W3C home > Mailing lists > Public > xmlp-comments@w3.org > July 2004

Issue 470: identifying XOP packages (revised proposal)

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Wed, 28 Jul 2004 14:23:57 -0700
Message-Id: <6F57033D-E0DC-11D8-B7C2-000A95BD86C0@bea.com>
Cc: Graham Klyne <GK@ninebynine.org>, xmlp-comments@w3.org
To: XMLP Dist App <xml-dist-app@w3.org>


The Working Group today resolved to take a modified approach, outlined  
below, whereby the type parameter contains a content-type instead of a  
media type (i.e., it can contain parameters). This allows such  
parameters to "show through" both the root part's type parameter as  
well as the package's start-info parameter. It does mean that some  
escaping may be necessary, but that was thought an acceptable cost in  
exchange for the simplicity of the approach.

If there are any concerns about this, please communicate them to the WG  
list (xml-dist-app@w3.org) by the end of this week; unless this  
happens, the WG will consider the resolution accepted.

* Section 1.2 Example
In Example 2, change:
[[[Content-Type: Multipart/Related;boundary=MIME_boundary;
[[[Content-Type: multipart/related;boundry=MIME_boundary;

[[[Content-Type: application/soap_xop+xml; charset=UTF-8]]]
[[[Content-type: application/xop+xml; charset=UTF-8;  

* Section 3.1 Creating XOP Packages
In bullet 5, change "appropriate XOP-specific media type" to  
"application/xop+xml media type"

* Section 4.1 MIME Multipart/Related XOP Packages
Replace the second paragraph with:
"""The root MIME part is the root of the XOP Package, and MUST be a  
serialisation of the XOP Infoset using any W3C Recommendation-level  
version of XML (e.g., [XML 1.0], [XML 1.1]), and MUST be identified  
with a media type of "application/xop+xml" (as defined below). The  
"start-info" parameter of the package's media type MUST contain the  
content type associated with the content's XML serialisation (i.e., it  
will contain the same value as that of the root part's "type"  

* Section 5 Identifying XOP Packages
Replace the section with: """
XOP Documents, when used in MIME-like systems, are identified with the  
"application/xop+xml" media type, with the required "type" parameter  
conveying the original XML serialisation's associated content type.  
Note that when the type parameter contains reserved characters, it  
needs to be appropriately quoted and escaped.

For example, a XOP Package using MIME Multipart/Related packaging to  
serialise a SOAP 1.2 message [SOAP1.2] with an action parameter of  
"http://www.example.com/foo" would label the package itself with the  
"multipart/related" media type; the root part's media type is  
"application/xop+xml", with a "type" parameter containing  

5.1 Registration
MIME media type name:
MIME subtype name:
Required parameters:
	* "type"
	This parameter conveys the content type associated with the XML  
serialisation of the XOP Infoset, including parameters as appropriate.
Optional parameters:
	* "charset"
	 This parameter has identical semantics to the charset parameter of  
the application/xml media type as  specified in RFC 3023 [RFC 3023].
Encoding Considerations:
	 Identical to those of application/xml as described in RFC 3023 [RFC  
3023], section 3.2.
Security Consideration:
	In addition to application-specific considerations, XOP has the same  
security considerations described in RFC 3023  [RFC 3023], section 10.
Interoperability Considerations:
	There are no known interoperability issues.
Published Specification:
	This document.
Applications which use this media type:
	No known applications currently use this media type.
Additional Information:
	File extension:
	Fragment Identifiers:
		Identical to that of application/xml as described in RFC3023 [RFC3023]
	Base URI:
		As specified in RFC 3023 [RFC 3023], section 6.
	Macintosh File Type code:
Person and email address to contact for further information:
	Mark Nottingham <mnot@pobox.com>
Intended usage:
Author/Change controller:
	The XOP specification is a work product of the World Wide Web  
Consortium's XML Protocol Working Group. The W3C has change control  
over this specification.

Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Wednesday, 28 July 2004 17:24:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:14:17 UTC