DFXP's mime type is formally based on RFC 3023 [XML Media Types], which specifies ".xml" as file name extension (see Section 3.2 of that RFC, under Additional Information);<div><br></div><div><div class="gmail_quote">
On Tue, Oct 6, 2009 at 9:03 AM, Silvia Pfeiffer <span dir="ltr"><<a href="mailto:silviapfeiffer1@gmail.com">silviapfeiffer1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I am concerned about the lack of a additional information typically<br>
used in mime type registration RFCS, see e.g.<br>
<a href="http://www.rfc-editor.org/rfc/rfc3839.txt" target="_blank">http://www.rfc-editor.org/rfc/rfc3839.txt</a> (for 3gpp) or<br>
<a href="http://tools.ietf.org/html/rfc4337" target="_blank">http://tools.ietf.org/html/rfc4337</a> (mpeg4) or<br>
<a href="http://www.ietf.org/rfc/rfc5334.txt" target="_blank">http://www.ietf.org/rfc/rfc5334.txt</a> (ogg):<br>
<br>
Magic number(s): (probably not relevant)<br>
File extension(s):<br>
Macintosh File Type Code(s):<br>
<br>
I think it is important that we specify a common file extension and a<br>
mac file type code so as not to create confusion in the market with<br>
some people creating .dfxp , some creating .xml and some creating<br>
whatever they think is appropriate. This will make it very difficult<br>
for example for Web servers to serve the correct mime types, since<br>
they tend to do so based on file extensions.<br>
<br>
My suggestion is:<br>
<br>
File extension: .dfxp (I think four letters is reasonable nowadays,<br>
even for windows?)<br>
<br>
Mac file type code: DFXP<br>
<br>
<br>
Best Regards,<br>
<font color="#888888">Silvia.<br>
</font><div><div></div><div class="h5"><br>
<br>
On Thu, Oct 1, 2009 at 6:46 AM, Philippe Le Hegaret <<a href="mailto:plh@w3.org">plh@w3.org</a>> wrote:<br>
> The following media type registration will be submitted to<br>
> the IESG for review, approval, and registration with IANA (as per [1]).<br>
><br>
> At this point, we would appreciate comments on this registration<br>
> information. If you see any problems, please let us know.<br>
><br>
><br>
> Regards,<br>
><br>
> Philippe<br>
><br>
> [1] <a href="http://www.w3.org/2002/06/registering-mediatype" target="_blank">http://www.w3.org/2002/06/registering-mediatype</a><br>
><br>
> [[<br>
><br>
> This appendix registers a new MIME media type, "application/ttaf+xml"<br>
> in conformance with [1144]BCP 13 and [1145]W3CRegMedia. The information<br>
> in this appendix is being submitted to the Internet Engineering<br>
> Steering Group (IESG) for review, approval, and registration with the<br>
> Internet Assigned Numbers Authority (IANA).<br>
><br>
> [1144] <a href="http://www.ietf.org/rfc/rfc4288.txt" target="_blank">http://www.ietf.org/rfc/rfc4288.txt</a><br>
> [1145] <a href="http://www.w3.org/2002/06/registering-mediatype.html" target="_blank">http://www.w3.org/2002/06/registering-mediatype.html</a><br>
><br>
> MIME media type name:<br>
> application<br>
><br>
> MIME subtype name:<br>
> ttaf+xml<br>
><br>
> Required parameters:<br>
> None.<br>
><br>
> Optional parameters:<br>
> The encoding of a TT AF document must be determined by the<br>
> XML encoding declaration. This has identical semantics to the<br>
> application/xml media type in the case where the charset<br>
> parameter is omitted, as specified in [1146][XML Media],<br>
> Sections 8.9, 8.10 and 8.11.<br>
><br>
> The document profile of a TT AF document may be specified<br>
> using an optional profile parameter, which, if specified, the<br>
> value of which must adhere to the syntax and semantics of<br>
> ttp:profile parameter defined by Section [1147]6.2.8<br>
> ttp:profile of the published specification.<br>
><br>
> Encoding considerations:<br>
> Same for application/xml. See [1148][XML Media], Section 3.2.<br>
><br>
> Restrictions on usage:<br>
> None.<br>
><br>
> Security considerations:<br>
> As with other XML types and as noted in [1149][XML Media]<br>
> Section 10, repeated expansion of maliciously constructed XML<br>
> entities can be used to consume large amounts of memory,<br>
> which may cause XML processors in constrained environments to<br>
> fail.<br>
><br>
> In addition, because of the extensibility features for TT AF<br>
> and of XML in general, it is possible that<br>
> "application/ttaf+xml" may describe content that has security<br>
> implications beyond those described here. However, if the<br>
> processor follows only the normative semantics of the<br>
> published specification, this content will be outside TT AF<br>
> namespaces and may be ignored. Only in the case where the<br>
> processor recognizes and processes the additional content, or<br>
> where further processing of that content is dispatched to<br>
> other processors, would security issues potentially arise.<br>
> And in that case, they would fall outside the domain of this<br>
> registration document.<br>
><br>
> Interoperability considerations:<br>
> The published specification describes processing semantics<br>
> that dictate behavior that must be followed when dealing<br>
> with, among other things, unrecognized elements and<br>
> attributes, both in TT AF namespaces and in other namespaces.<br>
><br>
> Because TT AF is extensible, conformant<br>
> "application/ttaf+xml" processors must expect that content<br>
> received is well-formed XML, but it cannot be guaranteed that<br>
> the content is valid to a particular DTD or Schema or that<br>
> the processor will recognize all of the elements and<br>
> attributes in the document.<br>
><br>
> Published specification:<br>
> This media type registration is extracted from Appendix<br>
> [1150]D Media Type Registration of the [1151]Timed Text (TT)<br>
> Authoring Format 1.0 - Distribution Format Exchange Profile<br>
> (DFXP) specification.<br>
><br>
> [1151] <a href="http://www.w3.org/TR/ttaf1-dfxp/" target="_blank">http://www.w3.org/TR/ttaf1-dfxp/</a><br>
><br>
> Additional information:<br>
> None.<br>
><br>
> Person & email address to contact for further information:<br>
> Glenn Adams (<a href="mailto:public-tt@w3.org">public-tt@w3.org</a>)<br>
><br>
> Intended usage:<br>
> COMMON<br>
><br>
> Author/Change controller:<br>
> The published specification is a work product of the World<br>
> Wide Web Consortium's Timed Text (TT) Working Group. The W3C<br>
> has change control over this specification.<br>
><br>
> ]]<br>
> <a href="http://www.w3.org/TR/ttaf1-dfxp/#media-type-registration" target="_blank">http://www.w3.org/TR/ttaf1-dfxp/#media-type-registration</a><br>
><br>
><br>
><br>
><br>
><br>
</div></div></blockquote></div><br></div>