Accessibility/Video Text Format: Difference between revisions

Accessibility/Video Text Format (view source)

Revision as of 13:07, 7 July 2010

273 bytes added , 7 July 2010

improve intro text

Silviapfeiffer

401

edits

@@ Line 9: / Line 9: @@
 The new elements are not an extension to HTML5 and are not planned to be. There are hooks into HTML through the [http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#timed-tracks TimedTracks] API in HTML5 by which the WMML elements are exposed to the Web page that bears the media resource and the link to the WMML document. Some of these HTML5 APIs are only objects in HTML5, but are actual elements in WMML.
-The aim behind this way of defining WMML is to create a format that existing HTML5 parser implementations can parse with only a small number of extensions, rather than having to invent a completely new parsing model. The extensions are designed to map into existing HTML5 APIs so should not create an unacceptable overhead. Also, the reuse of CSS will allow reuse of existing implementations for styling and positioning. This should vastly help Web browsers to implement support for WMML, even and particularly including the richer features.
+The aim behind this way of defining WMML is to create a format that can reuse existing HTML5 snippet parsing, rather than having to invent a completely new parsing model. A WMML parser will only consist of a small amount of new parsing code and rely on an existing HTML5 snippet parser to provide for the bulk of its parsing needs. Also, the reuse of CSS will allow reuse of existing implementations for styling and positioning. This should vastly help Web browsers to implement support for WMML, even and particularly including the richer features.
-Note: A WMML document is a non-HTML document that contains HTML elements but is not an XML-with-namespaces document. This is on purpose so as to allow reuse of HTML parsers.
+Note: A WMML document is a non-HTML document that contains HTML elements but is not an XML-with-namespaces document. This is on purpose so as to allow reuse of HTML snippet parsing.
+Also note that as it stands WMML is not XML conformant, since it has some relaxed parsing rules (e.g. <cue> doesn't have to be explicitly closed - it will be implicitly closed by the next <cue> element). Stricter parsing rules could however be introduced.