Re: [ietf-types] Registration for application/ttml+xml

Philippe Le Hegaret <plh@w3.org> Thu, 06 September 2012 20:11 UTC

Return-Path: <plh@w3.org>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFC721F8778 for <ietf-types@ietfa.amsl.com>; Thu, 6 Sep 2012 13:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.169
X-Spam-Level:
X-Spam-Status: No, score=-8.169 tagged_above=-999 required=5 tests=[AWL=1.230, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-Few0Cokjpb for <ietf-types@ietfa.amsl.com>; Thu, 6 Sep 2012 13:11:03 -0700 (PDT)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id C27D521F876C for <ietf-types@ietf.org>; Thu, 6 Sep 2012 13:11:03 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id q86KAhNg025584 for <ietf-types@iana.org>; Thu, 6 Sep 2012 20:11:03 GMT
Received: from 30-5-196.wireless.csail.mit.edu ([128.30.5.196]) by jay.w3.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <plh@w3.org>) id 1T9iPR-0002Uh-HS; Thu, 06 Sep 2012 16:10:41 -0400
From: Philippe Le Hegaret <plh@w3.org>
To: ietf-types <ietf-types@iana.org>
In-Reply-To: <1346941169.2717.161.camel@chacal>
References: <1346941169.2717.161.camel@chacal>
Content-Type: text/plain; charset="UTF-8"
Organization: World Wide Web Consortium
Date: Thu, 06 Sep 2012 16:10:35 -0400
Message-ID: <1346962235.2717.178.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 (pechora4.lax.icann.org [192.0.33.74]); Thu, 06 Sep 2012 20:11:03 +0000 (UTC)
Cc: Sean Hayes <Sean.Hayes@microsoft.com>
Subject: Re: [ietf-types] Registration for application/ttml+xml
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2012 20:11:06 -0000

On Thu, 2012-09-06 at 10:19 -0400, Philippe Le Hegaret wrote:
> Hello,
> 
> This is Appendix C of TTML 1.0.
> 
> http://www.w3.org/TR/ttaf1-dfxp/#media-type-registration
> 
> Comments on this registration would be greatly appreciated.

Someone kindly pointed out that the version in the reference and below
don't match. So here is a report of the registration template:
MIME media type name:
        
        application
        
MIME subtype name:
        
        ttml+xml
        
Required parameters:
        
        None.
        
Optional parameters:
charset
        
        Same as application/xml media type, as specified in [XML Media
        Types] or its successors.
        
profile
        
        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
        specification.
        
Encoding considerations:
        
        Same for application/xml. See [XML Media], Section 3.2.
        
Restrictions on usage:
        
        None.
        
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:
        
        This media type registration is extracted from Appendix C Media
        Type Registration of the Timed Text Markup Language (TTML) 1.0
        specification.
        
Additional information:
Magic number(s):
File extension(s):
        
        .ttml
        
Macintosh file type code(s):
        
        "TTML"
        
Macintosh Universal Type Identifier code:
        
        org.w3c.ttml conforms to public.xml
        
Windows Clipboard Name:
        
        "Timed Text Document"
        
Person & email address to contact for further information:
        
        Timed Text Working Group (public-tt@w3.org)
        
Intended usage:
        
        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.