- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 29 Jan 2008 03:38:22 +0900
- To: ietf-types@iana.org
- CC: ietf-xml-mime@imc.org, www-multimodal@w3.org
Dear list, W3C published a Last Call Working Draft for "Ink Markup Language (InkML)" at: http://www.w3.org/TR/2006/WD-InkML-20061023/ I am sending this request to ask the Ietf-types list for comments on the Media Type section of the InkML specification following the procedure defined at: http://www.w3.org/2002/06/registering-mediatype --- The Media Type section of the InkML specification is available at: http://www.w3.org/TR/2006/WD-InkML-20061023/#mime-definition and a plaintext copy is also available below. MIME media type name: ---------------------- application MIME subtype name: ------------------- inkml+xml Required parameters: --------------------- None. Optional parameters: --------------------- charset This parameter has identical semantics to the charset parameter of the application/xml media type as specified in [RFC3023]. Encoding considerations: ------------------------- By virtue of InkML content being XML, it has the same considerations when sent as "application/inkml+xml" as does XML. See RFC 3023, section 3.2. Security considerations: ------------------------- Several InkML instructions may cause arbitrary URIs to be dereferenced. In this case, the security issues of RFC1738, section 6, should be considered. In addition, because of the extensibility features for InkML, it is possible that "application/inkml+xml" may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of this specification, this content will 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: --------------------------------- This specification describes processing semantics that dictate behavior that must be followed when dealing with, among other things, unrecognized elements. Because InkML is extensible, conformant "application/inkml+xml" processors can expect that content received is well-formed XML, but it cannot be guaranteed that the content is valid InkML or that the processor will recognize all of the elements and attributes in the document. Published specification: ------------------------- This media type registration is for InkML documents as described by this specification. Additional information: ------------------------- Magic number(s): There is no single initial octet sequence that is always present in InkML documents. File extension(s): InkML documents are most often identified with the extensions ".ink" or ".inkml". Macintosh File Type Code(s): TEXT Intended usage: ---------------- COMMON Author/Change controller: -------------------------- The InkML specification is a work product of the World Wide Web Consortium's Multimodal Interaction Working Group. The W3C has change control over these specifications. Normative References: ---------------------- [RFC3023] XML Media Types. IETF RFC 3023. http://www.ietf.org/rfc/rfc3023.txt . Sincerely, Kazuyuki -- Kazuyuki Ashimura / W3C Multimodal & Voice Activity Lead mailto: ashimura@w3.org voice: +81.466.49.1170 / fax: +81.466.49.1171
Received on Monday, 28 January 2008 18:37:15 UTC