Re: [ietf-types] Registration of ttml+xml

Philippe Le Hegaret <> Tue, 14 December 2010 18:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D84F03A6EBB for <>; Tue, 14 Dec 2010 10:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[AWL=-3.417, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, J_CHICKENPOX_37=0.6, J_CHICKENPOX_43=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wvJDG4eh0vU0 for <>; Tue, 14 Dec 2010 10:40:33 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 6DF8C3A6EBA for <>; Tue, 14 Dec 2010 10:40:32 -0800 (PST)
Received: from ( []) by (8.13.8/8.13.8) with ESMTP id oBEIfbMT006083 for <>; Tue, 14 Dec 2010 10:41:58 -0800
Received: from ([]) by with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <>) id 1PSZod-0005HQ-L4; Tue, 14 Dec 2010 13:41:35 -0500
From: Philippe Le Hegaret <>
To: Bjoern Hoehrmann <>
In-Reply-To: <>
References: <1282852932.5931.18.camel@chacal> <>
Content-Type: text/plain; charset="UTF-8"
Organization: World Wide Web Consortium
Date: Tue, 14 Dec 2010 13:41:30 -0500
Message-ID: <1292352090.2399.76.camel@chacal>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 7bit
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 ( []); Tue, 14 Dec 2010 10:41:58 -0800 (PST)
Cc:, public-tt <>
Subject: Re: [ietf-types] Registration of ttml+xml
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Dec 2010 18:40:34 -0000

On Sat, 2010-08-28 at 19:16 +0200, Bjoern Hoehrmann wrote:
> >[[
> >MIME media type name:
> This uses an outdated template, not the one from RFC 4288. Some of the
> field names have changed, and some fields have been split into separate
> fields.

I used the template at

> >Published specification:
> >        
> >        This media type registration is extracted from Appendix C Media
> >        Type Registration of the Timed Text Markup Language (TTML) 1.0
> >        specification.
> This should just reference the format specification.

I removed the reference to the subsection.

Here is the updated version:

Type name:
Subtype name:
Required parameters:
Optional parameters:
        Same as application/xml media type, as specified in [XML Media
        Types] or its successors.
        The document profile of a TTML document 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
Encoding considerations:
        Same for application/xml. See [XML Media], Section 3.2.
Security considerations:
        As with other XML types and as noted in [XML Media] 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.
        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, 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.
Interoperability considerations:
        The published specification describes processing semantics that
        dictate behavior that must be followed when dealing with, among
        other things, unrecognized elements and attributes, both in TTML
        namespaces and in other namespaces.
        Because TTML is extensible, conformant "application/ttml+xml"
        processors must expect that content received is well-formed XML,
        but it cannot be guaranteed that the content is valid to a
        particular DTD or Schema or that the processor will recognize
        all of the elements and attributes in the document.
Published specification:
        Timed Text Markup Language (TTML) 1.0.
Applications that use this media type:
        TTML is used in the television industry for the purpose of
        authoring, transcoding and exchanging timed text information and
        for delivering captions for television material repurposed for
        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:
Magic number(s):
File extension(s):
Macintosh file type code(s):
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 & email address to contact for further information:
        Timed Text Working Group (
Intended usage:
Restrictions on usage:
        The published specification is a work product of the World Wide
        Web Consortium's Timed Text (TT) Working Group.
Change controller:
        The W3C has change control over this specification.