
*This message was transferred with a trial version of CommuniGate(tm) Pro* This is a request for comments on the registration of the application/ccxml+xml mime type. The request is published as part of the CCXML 1.0 specification and is copied below. The url of the request is: http://www.w3.org/TR/ccxml/#ccxml-mime-definition Please send any comments on this request to rj@voxeo.com Thanks, RJ Appendix I - CCXML Media Type This appendix registers a new MIME media type, "application/ccxml+xml". I.1 Registration of MIME media type application/ccxml+xml MIME media type name: application MIME subtype name: ccxml+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 CCXML content being XML, it has the same considerations when sent as "application/ccxml+xml" as does XML. See RFC 3023, section 3.2. Security considerations: Several CCXML instructions may cause arbitrary URIs to be referenced. In this case, the security issues of RFC1738, section 6, should be considered. In addition, because of the extensibility features for CCXML, it is possible that "application/ccxml+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 CCXML is extensible, conferment "application/ccxml+xml" processors can expect that content received is well-formed XML, but it cannot be guaranteed that the content is valid CCXML or that the processor will recognize all of the elements and attributes in the document. Published specification: This media type registration is for CCXML documents as described by this specification. Additional information: Magic number(s): There is no single initial octet sequence that is always present in CCXML documents. File extension(s): CCXML documents are most often identified with the extensions ".ccxml". Macintosh File Type Code(s): TEXT Person & email address to contact for further information: RJ Auburn, <rj@voxeo.com>. Intended usage: COMMON Author/Change controller: The CCXML specification is a work product of the World Wide Web Consortium's Voice Browser Working Group. The W3C has change control over these specifications.