[Fwd: [IANA #695904] Request for MIME media type Application/Standards Tree - ttml+xml]

Here are the comments from the IESG regarding our request to register
the TTML media type. We should address them before moving TTML 1.0 2nd
to REC.

Philippe

> The IESG-designated expert has reviewed your application and returned 
> the inline comments below. Please reply to this email within 30 days 
> (i.e. by 15 September) with a revised application. 
> 
> If you have any questions, please don't hesitate to contact us.
> 
> Best regards,
> 
> Amanda Baber
> IANA Request Specialist
> ICANN
> 
> 
> > Name : Philippe Le Hegaret
> 
> > Email : plh@w3.org
> 
> > MIME media type name : Application
> 
> > MIME subtype name : Standards Tree -ttml+xml
> 
> > Required parameters : None
> 
> > Optional parameters :
> > charset
> 
> > If specified, the charset parameter must match the XML encoding declaration,
> > or if absent, the actual encoding.
> 
> 
> Isn't the effectively constrained to utf-8 or utf-16, as noted in the
> specification? If so, why not say so?
> 
> 
> > profile
> 
> > The document profile of a TTMLDocument Instance may be specified using an
> > optional profile parameter, which, if specified, the value of which must adhere
> > to the syntax and semantics of ttp:profile parameter defined by Section 6.2.8
> > ttp:profile of the published specification.
> 
> 
> > Encoding considerations : 8bit
> 
> 
> This isn't consistent with what's in the specification, which says:
> 
>   Same for application/xml, except constrained to either UTF-8 or 
>   UTF-16. See  [XML Media Types], Section 3.2.
> 
> If the specification is correct, the encoding here has to be binary in order to accommodate utf-16. And theres' no reason not to include this text in the actual registration.
> 
> 
> > Security considerations :
> 
> > As with other XML types and as noted in [XML Media Types] Section 10,
> > repeated expansion of maliciously constructed XML entities can be used to
> > consume large amounts of memory, which may cause XML processors in constrained
> > environments to fail.
> 
> 
> Either the definition of [XML Media Types] needs to be included or else it needs to be expanded to RFC 3023 inline.
> 
> 
> > In addition, because of the extensibility features for TTML and of XML in
> > general, it is possible that "application/ttml+xml" may describe content that
> > has security implications beyond those described here. However, TTML does not
> > provide for any sort of active or executable content, and if the processor
> > follows only the normative semantics of the published specification, this
> > content will be outside TTML namespaces and may be ignored. Only in the case
> > where the processor recognizes and processes the additional content, or where
> > further processing of that content is dispatched to other processors, would
> > security issues potentially arise. And in that case, they would fall outside
> > the domain of this registration document.
> 
> > Although not prohibited, there are no expectations that XML signatures or
> > encryption would normally be employed.
> 
> 
> > Interoperability considerations :
> 
> 
> > Published specification :
> > This media type registration is extracted from Appendix C Media Type
> > Registration of the Timed Text Markup Language (TTML) 1.0 specification:
> > http://www.w3.org/TR/ttaf1-dfxp/
> > Timed Text Markup Language (TTML) 1.0.
> 
> 
> > Applications which use this media :
> 
> > TTML is used in the television industry for the purpose of authoring,
> > transcoding and exchanging timed text information and for delivering captions,
> > subtitles, and other metadata for television material repurposed for the Web
> > or, more generally, the Internet.
> 
> > There is partial and full support of TTML in components used by several Web
> > browsers plugins, and in a number of caption authoring tools.
> 
> > Additional information :
> 
> > 1. Magic number(s) : none
> > 2. File extension(s) : .ttml
> > 3. Macintosh file type code : "TTML"
> > 4. Object Identifiers: none
> 
> > Fragment identifiers:
> > For documents labeled as application/ttml+xml, the fragment identifier notation is intended to be used with xml:id attributes, as described in section 7.2.1 of the Timed Text Markup Language (TTML) 1.0 specification.
> 
> 
> > Person to contact for further information :
> 
> > 1. Name : Timed Text Working Group
> > 2. Email : public-tt@w3.org
> 
> > Intended usage : Common
> > COMMON
> 
> 
> > Author/Change controller : The published specification is a work product of
> > the World Wide Web Consortium's Timed Text (TT) Working Group.
> 
> > The W3C has change control over this specification.
> 
> 
>

Received on Wednesday, 21 August 2013 12:33:45 UTC