W3C home > Mailing lists > Public > public-tt@w3.org > October 2017

[ttml2] [ttml2] TTML2 wide review comment: styling

From: tmichel07 via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Oct 2017 06:51:59 +0000
To: public-tt@w3.org
Message-ID: <issues.opened-262322266-1507013504-sysbot+gh@w3.org>
tmichel07 has just created a new issue for https://github.com/w3c/ttml2:

== [ttml2] TTML2 wide review comment: styling ==
TTML is based in XML, but experience over the years has shown that the ‘X’ (extensible) is deeply problematic.  

When a specification is revised, either all the new features are in a new namespace, which makes documents messy and hard to read, or they have to fit into places where ‘any’ element or ‘any’ attribute is allowed in the prior grammar. Unfortunately, the latter leaves the new elements/attributes very much in a second-class-citizen state. If instead, a new namespace and grammar is minted,  then the documents are no longer recognizable to and processable by a reader written to recognize the old namespace ID, even if the extensions and new elements can be ignored and fallback behavior is acceptable.
Comment sent by David Singer <singer@apple.com> on  01/10/2017 à 02:47, a écrit :
https://lists.w3.org/Archives/Public/public-tt/2017Oct/0000.html
------------
When the incorporation of elements designed by other bodies is included, the result can be a bewildering mess. This has sometimes led to attempts to ‘make native’ these elements, and effectively copy their specification from the external definition into the revision; but this raises questions of attribution and backwards compatibility.

I recommend the group consider a re-design using a more flexible and less problematic base syntax.


David Singer
Manager, Software Standards, Apple Inc.


Please view or discuss this issue at https://github.com/w3c/ttml2/issues/446 using your GitHub account
Received on Tuesday, 3 October 2017 06:51:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:44:20 UTC