July 2010 - Ietf-types - alvestrand.no

Registration of media type application/ttaf+xml
by Philippe Le Hegaret 26 Aug '10

26 Aug '10

The following media type registration will be submitted to the IESG for review, approval, and registration with IANA (as per [1]). At this point, we would appreciate comments on this registration information. If you see any problems, please let us know. Regards, Philippe [1] http://www.w3.org/2002/06/registering-mediatype [[ This appendix registers a new MIME media type, "application/ttaf+xml" in conformance with [1144]BCP 13 and [1145]W3CRegMedia. The information in this appendix is being submitted to the Internet Engineering Steering Group (IESG) for review, approval, and registration with the Internet Assigned Numbers Authority (IANA). [1144] http://www.ietf.org/rfc/rfc4288.txt [1145] http://www.w3.org/2002/06/registering-mediatype.html MIME media type name: application MIME subtype name: ttaf+xml Required parameters: None. Optional parameters: The encoding of a TT AF document must be determined by the XML encoding declaration. This has identical semantics to the application/xml media type in the case where the charset parameter is omitted, as specified in [1146][XML Media], Sections 8.9, 8.10 and 8.11. The document profile of a TT AF 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 [1147]6.2.8 ttp:profile of the published specification. Encoding considerations: Same for application/xml. See [1148][XML Media], Section 3.2. Restrictions on usage: None. Security considerations: As with other XML types and as noted in [1149][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 TT AF and of XML in general, it is possible that "application/ttaf+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 TT AF 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 TT AF namespaces and in other namespaces. Because TT AF is extensible, conformant "application/ttaf+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 [1150]D Media Type Registration of the [1151]Timed Text (TT) Authoring Format 1.0 - Distribution Format Exchange Profile (DFXP) specification. [1151] http://www.w3.org/TR/ttaf1-dfxp/ Additional information: None. Person & email address to contact for further information: Glenn Adams (public-tt(a)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. ]] http://www.w3.org/TR/ttaf1-dfxp/#media-type-registration

7 9

Re: Registration of media typeimage/svg+xml
by Chris Lilley 19 Jul '10

19 Jul '10

On Friday, June 18, 2010, 5:50:56 PM, Henry wrote: HST> Suggest you add HST> Fragment Identifiers HST> For documents labeled as application/svg+xml, the fragment identifier HST> notation is exactly that for application/xml, as specified in [RFC HST> 3023] or its successors. Henry, I have updated the registration template on the editors draft for SVG 1.1 second edition, incorporating a modified form of your suggestion (added a reference to the SVG-specific fragment syntax as well as the xml generic one). http://dev.w3.org/SVG/profiles/1.1F2/publish/mimereg.html Please have a look and tell me if its ok. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG

1 0

Vendor-specific MIME type for review
by Tapani Otala 15 Jul '10

15 Jul '10

Hello, We would like to submit a new vendor-specific MIME type for your review. The basic idea is simple, but it did not quite fit in the IANA registration form and the recommendation was to post it to this mailing list for review. MIME media type name: application MIME subtype name: vnd.adobe.composite-asset Required parameters: final_type, final_subtype Optional parameters: none Description: This media type denotes a generic composite asset container that contains multiple sub-assets, each of which has an existing IANA registered text, image and video media types. The final type is identified by the final_type and final_subtype parameters. Sample usage: application/vnd.adobe.composite-asset; final_type=text, final_subtype=html Encoding considerations: binary This media type may require encoding on transports not capable of handling binary. Security considerations: This media type contains content that could be considered 'active' or 'executable'. However, it does not expand upon the existing security considerations already applicable to those media types. Published specification: This media type references existing IANA registered MIME types, for which there are existing specifications. Applications which use this media: Adobe Photoshop.com Web Service (http://www.photoshop.com) and its client applications. Person to contact for further information: Tapani Otala (otala(a)adobe.com) Intended usage: Limited Use The use of this media type is limited to the Photoshop.com web service and its client applications. Sincerely, Tapani Otala Sr. Engineering Manager, Photoshop.com Platform Services Adobe Systems Incorporated

4 8

review of video media subtype for H264-SVC
by Roni Even 13 Jul '10

13 Jul '10

Hi, The AVT working group requests media type review for the video/H264-SVC media types defined in section 7.1 of http://tools.ietf.org/html/draft-ietf-avt-rtp-svc-21 . This draft went through AVT working group last call. We would be grateful if any comments could be made by 23 July 2010. Thanks, Roni Even (AVT co-chair)

1 0

review of video media subtype for H264-RCDO
by Roni Even 13 Jul '10

13 Jul '10

Hi, The AVT working group requests media type review for the video/H264-RCDO media types defined in section 6.1 of http://tools.ietf.org/html/draft-ietf-avt-rtp-h264-rcdo-06 . This draft went through AVT working group last call. We would be grateful if any comments could be made by 23 July 2010. Thanks, Roni Even (AVT co-chair)

1 0

Re: need advice on registration for YAML format
by Julian Reschke 10 Jul '10

10 Jul '10

On 09.07.2010 19:15, Ned Freed wrote: >> Hi, > >> currently there is no media type registered for YAML (see >> <http://yaml.org/spec/1.2/spec.html>). I'd like to change that. > >> Two questions though: > >> 1) YAML is a text format, but it has hardwired character sets, similar >> to application/json (detectable via the BOM). This means, it really >> needs to be registered under application/*, right? > > Given that UTF-16 is being used, there really isn't an option - it has > to go > under application. Agreed. But: how did text/xml end up where it is? Or text/html? > ... Best regards, Julian

4 3

need advice on registration for YAML format
by Julian Reschke 09 Jul '10

09 Jul '10

Hi, currently there is no media type registered for YAML (see <http://yaml.org/spec/1.2/spec.html>). I'd like to change that. Two questions though: 1) YAML is a text format, but it has hardwired character sets, similar to application/json (detectable via the BOM). This means, it really needs to be registered under application/*, right? 2) yaml.org isn't a standards body recognized by the IETF. So, to get into the standards tree, the canonical solution would be to move the spec into an RFC, right? An alternative would be the vendor tree (<http://tools.ietf.org/html/rfc4288#section-3.2>). So would application/vnd.yamlorg.yaml make sense? Best regards, Julian

3 2