401
edits
Accessibility/Video a11y requirements: Difference between revisions
Jump to navigation
Jump to search
Accessibility/Video a11y requirements (view source)
Revision as of 12:08, 24 November 2008
, 24 November 2008added RELAX NG
(removed hreflang need, since it's not used much in html either) |
(added RELAX NG) |
||
| Line 390: | Line 390: | ||
* If a subset of HTML is selected as a choice for the markup language, parsing and rendering engines of Web browsers can be re-used. | * If a subset of HTML is selected as a choice for the markup language, parsing and rendering engines of Web browsers can be re-used. | ||
* XML based markup of text codecs however often renders the text specification unreadable. Examples: [http://wiki.xiph.org/index.php/OggKate#Overview_of_the_Kate_bitstream_format Kate] chose a C-like tree that was easy to parse with lex & yacc; [http://www.w3.org/DesignIssues/Notation3 RDF has a N3 notation as a RDF-XML alternative | * XML based markup of text codecs however often renders the text specification unreadable. Examples: [http://wiki.xiph.org/index.php/OggKate#Overview_of_the_Kate_bitstream_format Kate] chose a C-like tree that was easy to parse with lex & yacc; [http://www.w3.org/DesignIssues/Notation3 RDF has a N3 notation] [http://www.w3.org/TR/rdf-syntax-grammar/#section-RELAXNG-Schema or a RELAX NG notation] as a RDF-XML alternative; [http://en.wikipedia.org/wiki/Subrip srt] and other simple subtitle/caption formats avoid XML | ||
* When encapsulating text codecs into a binary audio/video file such as Ogg, where compression is everything that counts, a "talkative" XML codec may not be the best choice. | * When encapsulating text codecs into a binary audio/video file such as Ogg, where compression is everything that counts, a "talkative" XML codec may not be the best choice. | ||