ISSUE-197: charset/encoding unconstrained
charset/encoding unconstrained
- State:
- PENDING REVIEW
- Product:
- TTML 1.0
- Raised by:
- Mike Dolan
- Opened on:
- 2012-11-29
- Description:
- TTML is silent on the document charset (xml encoding) permitted. Since the core XML specification permits virtually anything, then TTML is also unconstrained. Certain encodings, such as "binary" are generally non-interoperable. Further, since we permit other namespaces, constraints on those should also be required. For example, even if TTML is constrained to utf-8 and utf-16, then allowing other namespaces to use binary would make the document using such namespaces unparseable.
XML decoders are only required to support utf-8 and utf-16. Propose we so constrain TTML.
Related to Issue-196: https://www.w3.org/AudioVideo/TT/tracker/issues/196
Related to Action-131: https://www.w3.org/AudioVideo/TT/tracker/actions/131
Related to Action-129: https://www.w3.org/AudioVideo/TT/tracker/actions/129
- Related Actions Items:
- ACTION-136 on Glenn Adams to Integrate changes from Action-133 into the TTML 1.0 Second Edition - due 2013-01-14, pending review
- Related emails:
- TTWG Agenda March 7, 2013 (from momartin@microsoft.com on 2013-03-07)
- Re: TTML Agenda for 28/2/13 (from glenn@skynav.com on 2013-02-28)
- RE: TTML Agenda for 28/2/13 (from mdolan@newtbt.com on 2013-02-28)
- TTML Agenda for 28/2/13 (from momartin@microsoft.com on 2013-02-28)
- TTML Agenda for 21/02/13 (from Sean.Hayes@microsoft.com on 2013-02-21)
- TTML Agenda for 14/02/13 (from Sean.Hayes@microsoft.com on 2013-02-14)
- TTML Agenda for 07/02/13 (from Sean.Hayes@microsoft.com on 2013-02-07)
- TTML Agenda for 31/01/13 (from Sean.Hayes@microsoft.com on 2013-01-31)
- RE: TTML Agenda for 25/01/13 (from momartin@microsoft.com on 2013-01-24)
- TTML Agenda for 25/01/13 (from Sean.Hayes@microsoft.com on 2013-01-24)
- RE: TTML Agenda for 17/01/13 (from mdolan@newtbt.com on 2013-01-17)
- TTML Agenda for 17/01/13 (from Sean.Hayes@microsoft.com on 2013-01-17)
- TTWG Meeting Minutes Jan 10, 2013 (from momartin@microsoft.com on 2013-01-10)
- RE: TTML Agenda for 10/01/13 (from Sean.Hayes@microsoft.com on 2013-01-10)
- ISSUE-197: charset/encoding unconstrained [DFXP 1.0] (from sysbot+tracker@w3.org on 2012-11-29)
Related notes:
Opened to resolve for TTML 1.0 Second Edition.
Monica Martin, 7 Jan 2013, 16:09:09Related to: Actions 88, 133, 136 and Issue 175.
Monica Martin, 7 Jan 2013, 16:14:43see new Appendix M (informative)
Glenn Adams, 2 May 2013, 05:28:15Changelog:
Created issue 'charset/encoding unconstrained' nickname owned by Mike Dolan on product DFXP 1.0, description 'TTML is silent on the document charset (xml encoding) permitted. Since the core XML specification permits virtually anything, then TTML is also unconstrained. Certain encodings, such as "binary" are generally non-interoperable. Further, since we permit other namespaces, constraints on those should also be required. For example, even if TTML is constrained to utf-8 and utf-16, then allowing other namespaces to use binary would make the document using such namespaces unparseable.
XML decoders are only required to support utf-8 and utf-16. Propose we so constrain TTML.
Related to Issue-196: https://www.w3.org/AudioVideo/TT/tracker/issues/196
Related to Action-131: https://www.w3.org/AudioVideo/TT/tracker/actions/131
Related to Action-129: https://www.w3.org/AudioVideo/TT/tracker/actions/129
' non-public
Status changed to 'open'
Monica Martin, 7 Jan 2013, 16:09:23Status changed to 'pending review'
Glenn Adams, 2 May 2013, 05:28:15