Copyright © 2004 © 2005 W3C ® ( MIT , ERCIM , Keio ), All Rights Reserved. W3C liability , trademark and document use rules apply.
This document addresses the need to indicate the media type content-type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected media type(s) content-type(s) associated with binary element content. It is expected that the additional information about the media type content-type will be used for optimizing the handling of binary data that is part of a Web services message.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document is a <a href= "http://www.w3.org/2004/02/Process-20040205/tr.html#last-call"> W3C Working Group Note .This document includes the resolution of the comments received on the Last Call Working Draft previously published. The comments on this document and their resolution can be found in the Web Services Description Working Group's issues list and in the section C Change Log . A <a href="diff.html"> diff-marked version against the previous version of this document is available. deleted text: If the feedback is positive, the Working Groups plans to publish the final version of this specification as a W3C Working Group Note. Comments on this document are invited and are to be sent to the public <a href= "mailto:public-ws-media-types@w3.org"> public-ws-media-types@w3.org </a> mailing list ( <a href= "http://lists.w3.org/Archives/Public/public-ws-media-types/"> public archive </a> ). Comments can be sent until <b> 24 November 2004 </b>.
It has been produced jointly by the XML Protocol Working Group , and the Web Services Description Working Group , which are part of the Web Services Activity .
No further work on this topic is planned at this point. Errors in this document can be reported to the public public-ws-media-types@w3.org mailing list ( public archive ).
Publication as a Working Draft Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document has been produced under the 24 January 2002 Current Patent Practice as amended by the W3C Patent Policy Transition Procedure . Patent disclosures relevant to this specification may be found on the Web Services Description Working Group patent disclosure page and on the XML Protocol Working Group patent disclosure page . An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy .
1 Introduction
1.1 Notational
Conventions
1.2 Requirements
2 Attributes for Declaring Media Types Content-Type
2.1 <a
href="#contentType"> contentType attribute xmime:contentType
Attribute
2.2 <a href=
"#expectedMediaType"> expectedMediaType attribute
xmime:expectedContentTypes Attribute
3 Declaring media
types Content-Type for
binary data Binary Data
3.1 Role of expectedMediaType xmime:expectedContentTypes Schema annotation attribute Annotation Attribute
4 Examples
4.1 Binary data Data with
known media type Known Media Type
4.2 Binary
data Data with preferred media
type Preferred Media
Type
5 <a href="#references">
Normative
References
6 Informative
References
A Acknowledgements
B <a href="#appendix"> Appendix
Schema
C Change Log (Non-Normative)
Data sent and received over the Web typically uses the MIME media type defined by [IETF RFC 2046] , as the type system. For example, "image/jpeg", "application/pdf". There is a need to indicate the media type content-type of the XML element content, for example, in messages sent and received by Web services. There is also a need to express the media type content-type information using [XML Schema: Datatypes] and [XML Schema: Datatypes] , which is the type system used by [WSDL 2.0 Part 1] . This would allow XML-based applications, such as Web services, to utilize the widely deployed and supported MIME media type infrastructure.
[XOP] and [MTOM] enables one to serialize binary content (element content that is in a canonical lexical representation of the xs:base64Binary type) in an optimized way using MIME packaging. There is a desire to specify the media type content-type information of such binary element content in a standard way in the [XML Information Set] and not just in the optimized serialization of that Infoset.
This document specifies:
An attribute ( xmlmime:contentType xmime:contentType ) to indicate the media type content-type of an XML element content whose type is xs:base64Binary or xs:hexBinary . The value of the attribute is deleted text: the name of a IANA media type token valid content-type string (e.g., "text/xml; charset=utf-16"). This attribute specifies the media type content-type of the deleted text: content of an element content on which it occurs.
A XML Schema annotation attribute ( xmlmime:expectedMediaType xmime:expectedContentTypes ) to indicate, in XML Schema, the expected media type(s) content-type(s) for an element content whose type is xs:base64Binary or xs:hexBinary .
The XML Schema annotation, xmlmime:expectedMediaType xmime:expectedContentTypes , specifies the expected range of values for the xmlmime:contentType xmime:contentType attribute and the expected range of media types content-type for the binary element content.
Note that the use of this mechanism, in particular the contentType xmime:contentType attribute, does not require the implementation, in whole or in part, of XML Schema. In the absence of XML Schema the type information (xs:base64Binary or xs:hexBinary) may have to be provided via other mechanisms; for example, using xsi:type .
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [IETF RFC 2119] .
This specification uses properties from the XML Information Set, see Set (see [XML Information Set] </a>. ). Such properties are denoted by square brackets, e.g. [namespace name].
This specification uses namespace prefixes that are listed in Table 1. Note that the choice of any namespace prefix is arbitrary and not semantically significant (see [XML Information Set] ).
Prefix | Namespace | Definition |
---|---|---|
xmlmime xmime | http://www.w3.org/2004/11/xmlmime http://www.w3.org/2005/05/xmlmime | Defined by this specification |
wsdl xs | http://www.w3.org/2004/03/wsdl "http://www.w3.org/2001/XMLSchema" | Defined by in the WSDL 2.0 specification. A normative W3C XML Schema <a href="#XMLSchemaP1"> specifications [XML Schema: Structures] , [XML Schema: Datatypes] </a> document for the http://www.w3.org/2004/03/wsdl namespace can be found at http://www.w3.org/2004/03/wsdl. . |
xs xsi | "http://www.w3.org/2001/XMLSchema" "http://www.w3.org/2001/XMLSchema-instance" | Defined in the W3C XML Schema specification [XML Schema: Structures] deleted text: </a>, <a href= "#XMLSchemaP2"> [XML Schema: Datatypes] . |
Namespace names of the general form "http://example.org/..." and "http://example.com/..." represent application or context-dependent URIs <a href="#rfc2396"> (see [IETF RFC 2396] </a>. 3986] ).
All parts of this specification are normative, with the exception of examples and sections explicitly marked as "Non-Normative".
This section describes the set of requirements that this document addresses.
Define how to indicate the media type content-type of an XML element content whose type is xs:base64Binary or xs:hexBinary . This is meta-data that may be, but not required to, used by tools to infer the specific media type content-type of binary data.
Define how to indicate the expected media type(s) content-type(s) of XML element content whose type is xs:base64Binary or xs:hexBinary in XML Schema. This information is needed to define the set of media types content-type that a binary data may have. For example, a Web services application may be willing to indicate that the binary data represents an image, but leaves it to a document instance to further specify whether it is "jpeg", "gif", etc. or "gif". This meta-data is not required to be present.
Define the acceptable format of media type content-type values.
Define the relationship between the expected and the actual value of the media types content-type declared for binary data in XML documents.
This section defines two global attribute information item s for declaring the media type content-type of binary data and expected content-type(s) of binary data in XML Schema to address deleted text: the requirements (1) and (2) above. Their usage is addressed in Section 3 Declaring media types Content-Type for binary data Binary Data .
The contentType xmime:contentType
attribute
information item has the following Infoset properties:
A [local name] of contentType
.
A [namespace name] of "http://www.w3.org/2004/11/xmlmime". "http://www.w3.org/2005/05/xmlmime".
The type of the contentType
xmime:contentType
attribute information item is xs:string </em>. with a
minimum length of three and all leading and trailing white space
characters are ignored.
The [normalized value] of the
xmime:contentType
attribute information item
MUST be a valid Content-Type string, e.g.,
"image/png", "text/xml; charset=utf-16" as defined by
[IETF RFC
2045] and indicates the
content-type of the [owner element]. Note that [normalized value]
consists of normalized attribute value as defined by
[XML Information
Set] and does not mean that two
equivalent values of xmime:contentType
will necessarily be equal.
The xmime:contentType
attribute information item allows Web services applications to optimize the
handling of the binary data defined by a binary element information item and should be considered as meta-data. The presence of
the xmime:contentType
attribute does not changes the value of the element
content.
The expectedMediaType
xmime:expectedContentTypes
attribute information item has the following Infoset
properties:
A [local name] of expectedMediaType expectedContentTypes
.
A [namespace name] of http://www.w3.org/2004/11/xmlmime http://www.w3.org/2005/05/xmlmime
.
The type of the expectedMediaType xmime:expectedContentTypes
attribute
information item is xs:string .
The value and the meaning of the expectedMediaType xmime:expectedContentTypes
attribute is
similar to the value allowed for the 'Accept'
HTTP header defined by HTTP 1.1
specification, Section 14.1 <a href=
"#rfc2616"> (see [IETF RFC 2616] ) and
MUST follow the production rules defined in that section. The 'q' parameter defined by HTTP 1.1
specification, Section 3.9 <a href="#rfc2616"> [IETF RFC
2616] </a> is allowed, but other accept-extensions are not
allowed. section except for the
following:
The 'accept-extensions' of the HTTP 'Accept' header are not allowed in the 'expectedMediaType' attribute value. prefix "Accept:" MUST NOT be used.
The WSD WG would like rule qdtext is changed
from: qdtext = <any TEXT
except<">>
to:
qdtext = <any CHAR
except<">>
This
change is made to solicit feedback on
this. </td> </tr> </table> disallow non-US-ASCII OCTETs.
The expectedMediaType
xmime:expectedContentTypes
attribute information item
is intended to be used as part of XML Schema annotation for a
binary element information item declaration (see 3 Declaring media types
Content-Type for binary data Binary
Data ). This
attribute information item
is meant to allow XML Schema authors to
indicate the range of media types and/or associated parameters that
are acceptable for the binary data. It serves as a static constrain
on the xmime:contentType
.Users of this attribute information item are urged to avoid using wild cards (for example,
"image/*") as it may lead to interoperability problems. If the set
of expected media types is not known, the use of
xmime:expectedContentTypes
is NOT RECOMMENDED.
Documents that want to specify additional media type content-type information for binary data SHOULD denote this by using a binary element information item . A binary element information item is an element information item defined with the following additional constraints.
An OPTIONAL contentType
xmime:contentType
attribute information item as described above in
<a href="#contentType">
2.1 contentType
attribute xmime:contentType
Attribute .
The character information items comprising the [children] of the element information item MUST conform to the lexical constraints of xs:base64Binary or xs:hexBinary .
The [normalized value] of
If the media
type identified by the value of an contentType xmime:contentType
deleted text: <em> attribute information item
</em> MUST be the name of
is a IANA text based
media type token, e.g., "image/png",
"text/xml; charset=utf-16" and indicates then the media type
value of the deleted text: [owner
element]. </p> <p> The contentType xmime:contentType
deleted text: <em> attribute information item
</em> allows Web services applications
to optimize the handling of the binary data defined by
SHOULD include a deleted text: <em>
binary element information item </em> and should be
considered as meta-data. The presence of the
contentType charset
attribute
does not changes the value of the element content.
parameter.
For authoring convenience, two types xmlmime:base64Binary xmime:base64Binary
and xmlmime:hexBinary xmime:hexBinary
are defined in
<a href= "#appendix"> B deleted text:
Appendix Schema
<?xml version="1.0" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://example.com/ct-required" xmlns:xmlmime="http://www.w3.org/2004/11/xmlmime" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" targetNamespace="http://example.com/ct-required"> <xs:import namespace="http://www.w3.org/2004/11/xmlmime" schemaLocation="http://www.w3.org/2004/11/xmlmime"/> <xs:import namespace="http://www.w3.org/2005/05/xmlmime" schemaLocation="http://www.w3.org/2005/05/xmlmime"/> <!-- This element has binary content and requires the contentType attribute that indicates the media type of the binary content --> <xs:element name="MyBinaryData"/> <!-- This element has binary content and requires the xmime:contentType attribute that indicates the content-type of the binary element --> <xs:element name="MyBinaryData"> <xs:complexType> <xs:simpleContent> <xs:restriction base="xs:base64Binary" > <xs:attribute ref="xmlmime:contentType" use="required"/> </xs:restriction> <xs:extension base="xs:base64Binary" > <xs:attribute ref="xmime:contentType" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:schema> deleted text:
The expectedMediaType
xmime:expectedContentTypes
attribute is used for annotating XML Schema to indicate the
expected range of media types
content-type of the binary element
content and the expected range of values for contentType xmime:contentType
attribute.
The value of the contentType
xmime:contentType
attribute,
if present, SHOULD be within the range specified by the
expectedMediaType xmime:expectedContentTypes
annotation
attribute, if specified in the schema. See
Section 14.1 of [IETF RFC 2616] on how
to interpret content-type ranges that may be defined with respect
to actual content. When the expectedMediaType xmime:expectedContentTypes
annotation
attribute has contains a wildcard
wild card ("*") or a list of
acceptable media types, content-type separated by commas (","), the
schema SHOULD require the contentType xmime:contentType
attribute to be
present.
Applications that need to specify expected media types content-type SHOULD use the schema annotation to
declare the range of expected values. expectedMediaType xmime:expectedContentTypes
annotation
attribute MAY be used in conjunction with the declaration of
binary element information item s or with complex type
definitions that are derived from xs:base64Binary or
xs:hexBinary in XML Schema. If the expectedMediaType xmime:expectedContentTypes
annotation
attribute is used in both the binary element information
item declaration as well as definition of the complex type
which the binary element information item belongs to, then
the expected range of values defined for the binary element
information item MUST be a subset of the expected range of
values defined for the complex type.
The xmime:expectedContentTypes
annotation can be used in conjunction with either type
or element declarations. Certain data-binding frameworks which use
static type mappings can be more specific if the
xmime:expectedContentTypes
annotation is applied to the complexType declarations
instead of the element declarations using those types. For this
reason, the use of expectedContentTypes on element declarations
using named complex types is not recommended. An example is
provided in Example 6.
The example below consists of a
type definition, PictureType
, and an element
declaration, Picture
. The xmlmime:contentType xmime:contentType
attribute is required to
be present and specifies the media
type content-type of the
binary content. The schema annotation attribute xmlmime:expectedMediaType xmime:expectedContentTypes
specifies that
the media type of the binary content is 'image', but and the subtype
name is unknown. either 'jpeg' or 'png'.
<?xml version="1.0" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://example.com/wildcard" xmlns:xmlmime="http://www.w3.org/2004/11/xmlmime" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" targetNamespace="http://example.com/wildcard"> <xs:import namespace="http://www.w3.org/2004/11/xmlmime" schemaLocation="http://www.w3.org/2004/11/xmlmime"/> <xs:import namespace="http://www.w3.org/2005/05/xmlmime" schemaLocation="http://www.w3.org/2005/05/xmlmime"/> <xs:complexType name="PictureType"> <xs:simpleContent> <xs:restriction base="xmlmime:base64Binary" > <xs:attribute ref="xmlmime:contentType" use="required" /> <xs:restriction base="xmime:base64Binary" > <xs:attribute ref="xmime:contentType" use="required" /> </xs:restriction> </xs:simpleContent> </xs:complexType> <!-- This element designates the range of values that the element definition will accept --> <xs:element name="Picture" type="tns:PictureType" xmlmime:expectedMediaType="image/*"/> </xs:element> xmime:expectedContentTypes="image/jpeg, image/png"/> </xs:schema> deleted text:
The example document instance below conforms to the element
declaration of Picture
and specifies that the binary
content is of type "image/png".
<?xml version="1.0" ?> <Picture xmlns="http://example.com/wildcard" xmlns:xmlmime="http://www.w3.org/2004/11/xmlmime" xmlmime:contentType="image/png">/aWKKapGGyQ=</Picture> xmlns:xmime="http://www.w3.org/2005/05/xmlmime" xmime:contentType="image/png">/aWKKapGGyQ=</Picture>
The example below examples in this section consists of a binary element elements whose media type is known in advance to be "image/jpeg".
In this example, the application fixes
the Example 4, a
fixed media type is specified
by declaring it with an annotation in conjunction with the complex
type definition. The attribute
xmime:contentType
is not used as the media type of the binary
data is know in advance.
<?xml version="1.0" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://example.com/know-type" xmlns:xmlmime="http://www.w3.org/2004/11/xmlmime" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" targetNamespace="http://example.com/know-type"> <xs:import namespace="http://www.w3.org/2004/11/xmlmime" schemaLocation="http://www.w3.org/2004/11/xmlmime"/> <xs:import namespace="http://www.w3.org/2005/05/xmlmime" schemaLocation="http://www.w3.org/2005/05/xmlmime"/> <xs:complexType name="JPEGPictureType" type="xs:base64Binary" xmlmime:expectedMediaType="image/jpeg"/> <xs:simpleType name="JPEGPictureType" xmime:expectedContentTypes="image/jpeg"> <xs:restriction base="xs:base64Binary"/> </xs:simpleType> <xs:element name="JPEGPicture" type="tns:JpegPictureType"/> <xs:element name="JPEGPicture" type="tns:JPEGPictureType"/> </xs:schema>
In Example
5, a fixed media type is specified by
declaring it with an annotation in conjunction with the element
declaration. The attribute xmime:contentType
is optionally used in document instances to indicate the
media type of the binary data.
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/know-type"
xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
targetNamespace="http://example.com/know-type">
<xs:import namespace="http://www.w3.org/2005/05/xmlmime"
schemaLocation="http://www.w3.org/2005/05/xmlmime"/>
<xs:element name="JPEGPicture" type="xmime:base64Binary"
xmime:expectedContentTypes="image/jpeg" />
</xs:schema>
This example illustrates that binary data with media type 'image/jpeg' is preferred but binary data with media type of 'image/tiff' is also allowed (with a lower preference).
<?xml version="1.0" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://example.com/preferred-type" xmlns:xmlmime="http://www.w3.org/2004/11/xmlmime" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" targetNamespace="http://example.com/preferred-type"> <xs:import namespace="http://www.w3.org/2004/11/xmlmime" schemaLocation="http://www.w3.org/2004/11/xmlmime"/> <xs:import namespace="http://www.w3.org/2005/05/xmlmime" schemaLocation="http://www.w3.org/2005/05/xmlmime"/> <xs:complexType name="JPEGPreferredPictureType"> <xs:complexType name="JPEGPreferredPictureType" xmime:expectedContentTypes="image/jpeg;q=1.0, image/tiff;q=0.8"> <xs:simpleContent> <xs:restriction base="xmlmime:base64Binary" > <xs:attribute ref="xmlmime:contentType" use="required" /> <xs:restriction base="xmime:base64Binary" > <xs:attribute ref="xmime:contentType" use="required" /> </xs:restriction> </xs:simpleContent> </xs:complexType> <xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType" xmlmime:expectedMediaType="image/jpeg;q=1.0, image/tiff;q=0.8"/> <xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"/> </xs:schema> deleted text:
This document is developed by the participants of the joint media types task force formed by Web Services Description and XML Protocol Working Groups. Participants of the taskforce, specifically Martin Gudgin, and Mark Nottingham are gratefully acknowledged.
<?xml version="1.0" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xmlmime="http://www.w3.org/2004/11/xmlmime" targetNamespace="http://www.w3.org/2004/11/xmlmime" > xmlns:xmime="http://www.w3.org/2005/05/xmlmime" targetNamespace="http://www.w3.org/2005/05/xmlmime" > <xs:attribute name="contentType" type="xs:string" /> <xs:attribute name="contentType"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:minLength value="3" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="expectedMediaType" type="xs:string" /> <xs:attribute name="expectedContentTypes" type="xs:string" /> <xs:complexType name="base64Binary" > <xs:complexType name="base64Binary" > <xs:simpleContent> <xs:extension base="xs:base64Binary" > <xs:attribute ref="xmlmime:contentType" /> <xs:attribute ref="xmime:contentType" /> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:complexType> <xs:complexType name="hexBinary" > <xs:complexType name="hexBinary" > <xs:simpleContent> <xs:extension base="xs:hexBinary" > <xs:attribute ref="xmlmime:contentType" /> <xs:attribute ref="xmime:contentType" /> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:complexType> </xs:schema> deleted text:
Who | When | What |
---|---|---|
ASK | 20050223 | Incorporated resolution for issue 260. In section 2.2 removed the sentence starting with "The 'q' parameter defined ..." and the editorial note seeking feedback. |
ASK | 20050223 | Incorporated resolution for issue 259. Section 2.2 is modified to disallow the prefix "Accept:" and the rule qdtext is modified to disallow non-usascii octets |
ASK | 20050223 | Incorporated resolution for issue 266. At the end of the section the following is added: In the absence of XML schema the type information (xs:base64Binary or xs:hexBinary) may have to be provided via other mechanisms; for example, xsi:type. |
ASK | 20050223 | Incorporated resolution for issue 261 specified in http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0013.html |
ASK | 20050223 | Incorporated resolution for issue 262 specified in http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0014.html |
ASK | 20050223 | Incorporated resolution for issue 263. Changed schema to make contentLength be of minlength of 3 added the stmt: " ... with a minimum length of three and all leading and trailing white space characters are ignored." in section 2.1 |
ASK | 20050223 | Resolved issue 253. In section 1.1 added: All parts of this specification are normative, with the exception of examples and sections explicitly marked as "Non-Normative". Created two sections: normative ref and informative ref, moved wsdl 2.0, xop and mtom ref to informative ref section. |
ASK | 20050223 | Removed the namespace prefix for wsdl in the table |
ASK | 20050223 | Resolved issue 254 by removing all ed notes |
ASK | 20050223 | Resolved issue 255 by updating the infoset ref to 2nd ed. |
ASK | 20050223 | Resolved issue 264 by accepting the proposal in the issue email (used the prefix 'xmlmime' for all occurences of expectedMediaType and contentType attribute) |
ASK | 20050223 | Resolved issue 265 by updating the mtom and xop ref to REC |
ASK | 20050223 | Resolved issue 269 by implementing all the suggestions: 1) s/name of the IANA media type token/a valid content-type string 2) title change 3) s/expectedMediaType/expectedContentType 4) s/Declaring media types for binary data/Declaring Content-Type for binary data. Also replaced 'media type' with 'content-type' at bunch of places |
ASK | 20050228 | Resolved issue 270 by including language that clarifies that [normalized value] does not mean normalization of ContentType values |
ASK | 20050304 | Replaced the prefix 'xmlmime' with 'xmime' to address i18n comment |
ASK | 20050304 | Added a 'SHOULD' for 'charset' params for textual types to address i18n comment |
ASK | 20050308 | Added a recommendation to use list of media types over wild cards |
ASK | 20050309 | Misc. ed changes (indentation, capitalization etc), changes to References (updated schema refs to 2nd edition, updated 2396 to 3986), fixed examples so that image/* is not an expectedContentType |
ASK | 20050309 | Added another example in section 4.1 to address Kevin's concern. |
ASK | 20050309 | Moved 2nd and 3rd para from section 3 to section 2.1 |
ASK | 20050310 | Per WG decision, changed expectedContentType to expectedConentTypes |
ASK | 20050310 | fixed example 1 bug. s/restriction/extension |
ASK | 20050310 | Added ref to rfc 2045 |
ASK | 20050316 | fixed example 4 bug |
ASK | 20050422 | added the agreed upon note about issue with existing tools that bind to prog. languages when the annotation is on the element decl rather than on a named complex type |
ASK | 20050422 | modified example 6 to move the annotation from the element decl to the type definition |
ASK | 20050422 | Included suggestions at http://lists.w3.org/Archives/Public/public-ws-media-types/2005Mar/0021.html |