- From: Anish.Karmarkar via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 09 Mar 2005 20:22:39 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/media-types
In directory hutz:/tmp/cvs-serv971
Modified Files:
xml-media-types.xml xml-media-types.html
Log Message:
changes agreed to at the boston f2f + misc ed. changes
Index: xml-media-types.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/media-types/xml-media-types.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** xml-media-types.xml 4 Mar 2005 19:46:48 -0000 1.28
--- xml-media-types.xml 9 Mar 2005 20:22:36 -0000 1.29
***************
*** 78,82 ****
example, in messages sent and
received by Web services. There is also a need to express the
! content-type information using <bibref ref="XMLSchemaP2"/>, which
is the type system used by <bibref ref="wsdl20part1"/>.
This would allow XML-based applications, such as Web services, to utilize
--- 78,82 ----
example, in messages sent and
received by Web services. There is also a need to express the
! content-type information using <bibref ref="XMLSchemaP2"/> and <bibref ref="XMLSchemaP2"/>, which
is the type system used by <bibref ref="wsdl20part1"/>.
This would allow XML-based applications, such as Web services, to utilize
***************
*** 128,132 ****
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, <emph>xsi:type</emph>.
</p>
--- 128,132 ----
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 <emph>xsi:type</emph>.
</p>
***************
*** 141,145 ****
<p>This specification uses properties from the XML
! Information Set, see <bibref ref="XMLInfoSet"/>. Such properties are
denoted by square brackets, e.g. [namespace name].
</p>
--- 141,145 ----
<p>This specification uses properties from the XML
! Information Set (see <bibref ref="XMLInfoSet"/>). Such properties are
denoted by square brackets, e.g. [namespace name].
</p>
***************
*** 150,181 ****
</p>
! <table border="1"
! summary="Mapping of prefixes used in this document to their associated namespace name" id="tabnsprefixes">
! <caption>Table 1. Prefixes and Namespaces used in this specification</caption>
! <tbody>
! <tr>
! <th>Prefix</th>
! <th>Namespace</th>
! <th>Definition</th>
! </tr>
! <tr><td>xmime</td>
<td>&xmlmimens;</td>
! <td>Defined by this specification</td>
! </tr>
!
! <tr><td>xs</td>
<td>"http://www.w3.org/2001/XMLSchema"</td>
!
! <td>Defined in the W3C XML Schema
! specification <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.
! </td>
! </tr>
!
</tbody>
! </table>
<p>Namespace names of the general form "http://example.org/..."
and "http://example.com/..." represent application or
! context-dependent URIs <bibref ref="rfc2396"/>.
</p>
--- 150,188 ----
</p>
! <table border="1"
! summary="Mapping of prefixes used in this document to their associated
! namespace name" id="tabnsprefixes">
! <caption>Table 1. Prefixes and Namespaces used in this specification</caption>
! <tbody>
! <tr>
! <th>Prefix</th>
! <th>Namespace</th>
! <th>Definition</th>
! </tr>
! <tr>
! <td>xmime</td>
<td>&xmlmimens;</td>
! <td>Defined by this specification</td>
! </tr>
! <tr>
! <td>xs</td>
<td>"http://www.w3.org/2001/XMLSchema"</td>
! <td>Defined in the W3C XML Schema specifications
! <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.
! </td>
! </tr>
! <tr>
! <td>xsi</td>
! <td>"http://www.w3.org/2001/XMLSchema-instance"</td>
! <td>Defined in the W3C XML Schema specification
! <bibref ref="XMLSchemaP1"/>.
! </td>
! </tr>
</tbody>
! </table>
<p>Namespace names of the general form "http://example.org/..."
and "http://example.com/..." represent application or
! context-dependent URIs (see <bibref ref="rfc3986"/>).
</p>
***************
*** 206,211 ****
define the set of 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 to
! further specify whether it is "jpeg", "gif", etc. This meta-data is
not required to be present.
</p>
--- 213,218 ----
define the set of 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", or "gif". This meta-data is
not required to be present.
</p>
***************
*** 230,234 ****
<p>This section defines two global &AII;s for
! declaring the content-type of binary data in XML Schema to address the
requirements (1) and (2) above. Their usage is addressed in Section <specref
ref="usage"/>.
--- 237,242 ----
<p>This section defines two global &AII;s for
! declaring the content-type of binary data and expected content-type(s)
! of binary data in XML Schema to address
requirements (1) and (2) above. Their usage is addressed in Section <specref
ref="usage"/>.
***************
*** 236,240 ****
<div2 id="contentType">
! <head>xmime:contentType attribute </head>
<p>
--- 244,248 ----
<div2 id="contentType">
! <head>xmime:contentType Attribute </head>
<p>
***************
*** 254,258 ****
<div2 id="expectedContentType">
! <head>xmime:expectedContentType attribute </head>
<p> The <att>xmime:expectedContentType</att> &AII; has the following Infoset properties:
--- 262,266 ----
<div2 id="expectedContentType">
! <head>xmime:expectedContentType Attribute </head>
<p> The <att>xmime:expectedContentType</att> &AII; has the following Infoset properties:
***************
*** 269,274 ****
<p>The value and the meaning of the
<att>xmime:expectedContentType</att> attribute is similar to the value
! allowed for the 'Accept' header defined by HTTP 1.1
! specification, Section 14.1 <bibref ref="rfc2616"/> and MUST
follow the production rules defined in that section except for the
following:
--- 277,282 ----
<p>The value and the meaning of the
<att>xmime:expectedContentType</att> attribute is similar to the value
! allowed for the <att>'Accept'</att> HTTP header defined by HTTP 1.1
! specification, Section 14.1 (see <bibref ref="rfc2616"/>) and MUST
follow the production rules defined in that section except for the
following:
***************
*** 287,293 ****
</olist>
! <p>The <att>xmime:expectedContentType</att> attribute is intended to be used
! as part of XML Schema annotation for a &BEII; declaration (see <specref
! ref="usage"/>).
</p>
</div2>
--- 295,309 ----
</olist>
! <p>The <att>xmime:expectedContentType</att> &AII; is intended to be
! used as part of XML Schema annotation for a &BEII; declaration
! (see <specref ref="usage"/>). This &AII; 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
! <att>xmime:contentType</att>. Users of this &AII; are urged to
! use wild cards (for example, "image/*") with care as it may
! lead to interoperability problems. If the set of expected media types
! are known, a list of media types is RECOMMENDED instead of wild cards
! (for example, <att>"image/jpeg, image/png"</att>).
</p>
</div2>
***************
*** 295,299 ****
<div1 id="usage">
! <head>Declaring Content-Type for binary data</head>
<p>Documents that want to specify additional content-type
--- 311,315 ----
<div1 id="usage">
! <head>Declaring Content-Type for Binary Data</head>
<p>Documents that want to specify additional content-type
***************
*** 317,321 ****
Note that [normalized value] consists of normalized attribute value as
defined by <bibref ref="XMLInfoSet"/> and does not mean that two
! equivalent ContentType values will be equal.
</p>
--- 333,338 ----
Note that [normalized value] consists of normalized attribute value as
defined by <bibref ref="XMLInfoSet"/> and does not mean that two
! equivalent values of <att>xmime:contentType</att> will necessarily be
! equal.
</p>
***************
*** 344,352 ****
<xs:import namespace="&xmlmimens;"
! schemaLocation="&xmlmimens;"/>
<!-- This element has binary content and requires the xmime:contentType
! attribute that indicates the content-type of the binary content -->
! <xs:element name="MyBinaryData"/>
<xs:complexType>
<xs:simpleContent>
--- 361,369 ----
<xs:import namespace="&xmlmimens;"
! schemaLocation="&xmlmimens;"/>
<!-- 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>
***************
*** 359,368 ****
</xs:schema>
-
</eg>
</example>
<div2 id="role">
! <head>Role of xmime:expectedContentType Schema annotation attribute</head>
<p>The <att>xmime:expectedContentType</att> attribute is used for annotating
--- 376,384 ----
</xs:schema>
</eg>
</example>
<div2 id="role">
! <head>Role of xmime:expectedContentType Schema Annotation Attribute</head>
<p>The <att>xmime:expectedContentType</att> attribute is used for annotating
***************
*** 375,381 ****
be within the range specified by the <att>xmime:expectedContentType</att>
annotation attribute, if specified in the schema.
! Refer to 14.1 <bibref ref="rfc2616"/> on how to interpret content-type
ranges that may be defined with respect to actual content. When the
! <att>xmime:expectedContentType</att> annotation attribute contains a wildcard
("*") or a list of acceptable content-type separated by commas (","),
the schema SHOULD require
--- 391,397 ----
be within the range specified by the <att>xmime:expectedContentType</att>
annotation attribute, if specified in the schema.
! See Section 14.1 of <bibref ref="rfc2616"/> on how to interpret content-type
ranges that may be defined with respect to actual content. When the
! <att>xmime:expectedContentType</att> annotation attribute contains a wild card
("*") or a list of acceptable content-type separated by commas (","),
the schema SHOULD require
***************
*** 404,412 ****
the binary content. The schema annotation attribute
<att>xmime:expectedContentType</att> specifies that the media type
! of the binary content is 'image', but the
! subtype name is unknown.
</p>
<example id="eg-wildcard">
! <head>Schema declaring an element with binary content and expected media type of "image/*"</head>
<eg xml:space="preserve">
<?xml version="1.0" ?>
--- 420,429 ----
the binary content. The schema annotation attribute
<att>xmime:expectedContentType</att> specifies that the media type
! of the binary content is 'image', and the subtype name is either 'jpeg'
! or 'png'.
</p>
<example id="eg-wildcard">
! <head>Schema declaring an element with binary content and expected
! media type of "image/jpeg" or "image/png"</head>
<eg xml:space="preserve">
<?xml version="1.0" ?>
***************
*** 417,421 ****
<xs:import namespace="&xmlmimens;"
! schemaLocation="&xmlmimens;"/>
--- 434,438 ----
<xs:import namespace="&xmlmimens;"
! schemaLocation="&xmlmimens;"/>
***************
*** 431,439 ****
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmime:expectedContentType="image/*"/>
! </xs:element>
</xs:schema>
-
</eg>
</example>
--- 448,454 ----
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmime:expectedContentType="image/jpeg, image/png"/>
</xs:schema>
</eg>
</example>
***************
*** 463,467 ****
<head>Examples</head>
<div2 id="static">
! <head>Binary data with known media type</head>
<p>The example below consists of a binary element
--- 478,482 ----
<head>Examples</head>
<div2 id="static">
! <head>Binary Data with Known Media Type</head>
<p>The example below consists of a binary element
***************
*** 495,499 ****
</xs:schema>
-
</eg>
</example>
--- 510,513 ----
***************
*** 502,506 ****
<div2 id="example-with-q-param">
! <head>Binary data with preferred media type</head>
<p>This example illustrates that binary data with media type 'image/jpeg' is
--- 516,520 ----
<div2 id="example-with-q-param">
! <head>Binary Data with Preferred Media Type</head>
<p>This example illustrates that binary data with media type 'image/jpeg' is
***************
*** 519,523 ****
<xs:import namespace="&xmlmimens;"
! schemaLocation="&xmlmimens;"/>
--- 533,537 ----
<xs:import namespace="&xmlmimens;"
! schemaLocation="&xmlmimens;"/>
***************
*** 530,538 ****
</xs:complexType>
! <xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
xmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
-
</eg>
</example>
--- 544,552 ----
</xs:complexType>
! <xs:element name="JPEGPeferredPicture"
! type="tns:JPEGPreferredPictureType"
xmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
</eg>
</example>
***************
*** 566,596 ****
<bibl id="XMLSchemaP1" key="XML Schema: Structures"
! href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">
! <titleref>XML Schema Part 1: Structures</titleref>,
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! Editors. World Wide Web Consortium, 2 May 2001.
</bibl>
<bibl key="XML Schema: Datatypes"
id="XMLSchemaP2"
! href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">
!
! <titleref>XML Schema Part 2: Datatypes</titleref>, P. Byron and
! A. Malhotra, Editors. World Wide Web Consortium, 2 May
! 2001.
</bibl>
! <bibl key="IETF RFC 2396"
! id="rfc2396" href="http://www.ietf.org/rfc/rfc2396.txt">
<titleref>Uniform Resource Identifiers (URI): Generic
Syntax</titleref>, T. Berners-Lee, R. Fielding,
! L. Masinter, Authors. Internet Engineering Task Force,
! August 1998.
</bibl>
<bibl key="IETF RFC 2046"
! id="rfc2046" href="http://www.ietf.org/rfcs/rfc2046.html"> <titleref>RFC 2046 - Multipurpose
! Internet Mail Extensions (MIME) Part Two: Media
! Types</titleref>, N. Freed, N. Borenstein, November
1996.
</bibl>
--- 580,608 ----
<bibl id="XMLSchemaP1" key="XML Schema: Structures"
! href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
! <titleref>XML Schema Part 1: Structures Second Edition</titleref>,
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! Editors. World Wide Web Consortium Recommendation, 28 October 2004.
</bibl>
<bibl key="XML Schema: Datatypes"
id="XMLSchemaP2"
! href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
! <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>,
! P. Byron and A. Malhotra, Editors. World Wide Web Consortium
! Recommendation, 28 October 2004.
</bibl>
! <bibl key="IETF RFC 3986"
! id="rfc3986" href="http://www.ietf.org/rfc/rfc3986.txt">
<titleref>Uniform Resource Identifiers (URI): Generic
Syntax</titleref>, T. Berners-Lee, R. Fielding,
! L. Masinter, January 2005.
</bibl>
<bibl key="IETF RFC 2046"
! id="rfc2046" href="http://www.ietf.org/rfcs/rfc2046.html">
! <titleref>RFC 2046 - Multipurpose Internet Mail Extensions (MIME)
! Part Two: Media Types</titleref>, N. Freed, N. Borenstein, November
1996.
</bibl>
***************
*** 600,621 ****
href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">
<titleref>Hypertext Transfer Protocol--HTTP
! 1.1</titleref>, R. Fieldingm, J. Gettys, J. Mogul,
! H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, Authors,
! W3C/MIT, June 1999.
</bibl>
! <bibl id="rfc2119" key="IETF RFC 2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>Key words for use in RFCs to Indicate Requirement
Levels</titleref>, S. Bradner, Author. Internet Engineering
Task Force, June 1999.
! </bibl>
! <bibl id="XMLInfoSet" key="XML Information Set"
! href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024/">
! <titleref>XML Information Set (Second Edition)</titleref>,
J. Cowan and R.
! Tobin, Editors. World Wide Web Consortium, 4 February 2004.
</bibl>
--- 612,632 ----
href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">
<titleref>Hypertext Transfer Protocol--HTTP
! 1.1</titleref>, R. Fielding, J. Gettys, J. Mogul,
! H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, June 1999.
</bibl>
! <bibl id="rfc2119" key="IETF RFC 2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>Key words for use in RFCs to Indicate Requirement
Levels</titleref>, S. Bradner, Author. Internet Engineering
Task Force, June 1999.
! </bibl>
! <bibl id="XMLInfoSet" key="XML Information Set"
! href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024/">
! <titleref>XML Information Set (Second Edition)</titleref>,
J. Cowan and R.
! Tobin, World Wide Web Consortium Recommendation, 4 February 2004.
</bibl>
***************
*** 633,677 ****
<titleref>Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
! Language.
! </titleref>Roberto Chinnici, Martin Gudgin,
Jean-Jacques Moreau, Jeffrey Schlimmer, Sanjiva Weerawarana,
! World Wide Web Consortium,
! W3C Working Draft 26 March 2004
</bibl>
<bibl id="XOP" key="XOP" href="http://www.w3.org/TR/2005/REC-xop10-20050125/">
! <titleref>XML-binary Optimized Packaging</titleref>Martin Gudgin, Noah
! Mendelsohn, Mark Nottingham, Herve Ruellan, W3C Recommendation 25
! January 2005
</bibl>
<bibl id="MTOM" key="MTOM" href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/">
<titleref>SOAP Message Transmission Optimization
! Mechanism</titleref>Martin Gudgin, Noah Mendelsohn, Mark Nottingham, Herve
! Ruellan, W3C Recommendation 25 January 2005
</bibl>
- <!--
- <bibl id="wsdlSeptf2f" key="WSDL September 2003 Face to Face Meeting"
- href="http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0218.html">
- <loc
- href="http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0218.html">WSDL
- WG September Face2Face Meeting Minutes</loc>, is
- available at
- http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0218.html
- and contains other presentations.
- </bibl>
- -->
-
- <!--
- <bibl id="paswa" key="PASWA" href="http://www.gotdotnet.com/team/jeffsch/paswa/paswa61.html">
- <titleref>Proposed Infoset Addendum to SOAP Messages with
- Attachments</titleref> Adam Bosworth, Don Box, Martin
- Gudgin, Mark Jones, Franz-Josef Fritz, Amy Lewis,
- Jean-Jacques Moreau, Mark Nottingham, David Orchard, Herve
- Ruellan, Jeffrey Schlimmer, Volker Wiechers, Version 0.61
- draft.
- </bibl>
- -->
</blist>
</div1>
--- 644,664 ----
<titleref>Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
! Language</titleref>, Roberto Chinnici, Martin Gudgin,
Jean-Jacques Moreau, Jeffrey Schlimmer, Sanjiva Weerawarana,
! World Wide Web Consortium Working Draft 26 March 2004
</bibl>
<bibl id="XOP" key="XOP" href="http://www.w3.org/TR/2005/REC-xop10-20050125/">
! <titleref>XML-binary Optimized Packaging</titleref>, Martin Gudgin,
! Noah Mendelsohn, Mark Nottingham, Herve Ruellan, W3C
! Recommendation, 25 January 2005
</bibl>
<bibl id="MTOM" key="MTOM" href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/">
<titleref>SOAP Message Transmission Optimization
! Mechanism</titleref>, Martin Gudgin, Noah Mendelsohn, Mark Nottingham, Herve
! Ruellan, W3C Recommendation, 25 January 2005
</bibl>
</blist>
</div1>
***************
*** 696,704 ****
<head>Schema</head>
- <!--
- <note><p>The following definitions are taken from <bibref ref="paswa"/>.</p>
- </note>
- -->
-
<eg xml:space="preserve">
<?xml version="1.0" ?>
--- 683,686 ----
***************
*** 706,710 ****
xmlns:xmime="&xmlmimens;"
targetNamespace="&xmlmimens;" >
-
<!--
<xs:attribute name="contentType" >
--- 688,691 ----
***************
*** 717,721 ****
</xs:attribute>
-->
! <xs:attribute name="contentType">
<xs:simpleType>
<xs:restriction base="xs:string" >
--- 698,702 ----
</xs:attribute>
-->
! <xs:attribute name="contentType">
<xs:simpleType>
<xs:restriction base="xs:string" >
***************
*** 723,727 ****
</xs:restriction>
</xs:simpleType>
! </xs:attribute>
<!--
<xs:element name="expectedContentType" >
--- 704,708 ----
</xs:restriction>
</xs:simpleType>
! </xs:attribute>
<!--
<xs:element name="expectedContentType" >
***************
*** 738,744 ****
</xs:simpleType>
-->
! <xs:attribute name="expectedContentType" type="xs:string" />
! <xs:complexType name="base64Binary" >
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
--- 719,725 ----
</xs:simpleType>
-->
! <xs:attribute name="expectedContentType" type="xs:string" />
! <xs:complexType name="base64Binary" >
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
***************
*** 746,752 ****
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
! <xs:complexType name="hexBinary" >
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
--- 727,733 ----
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
! <xs:complexType name="hexBinary" >
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
***************
*** 754,761 ****
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
</xs:schema>
-
</eg>
</div1>
--- 735,741 ----
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
</xs:schema>
</eg>
</div1>
***************
*** 883,886 ****
--- 863,879 ----
address i18n comment</td>
</tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050308</td>
+ <td>Added a recommendation to use list of media types over wild cards
+ </td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050309</td>
+ <td>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</td>
+ </tr>
</tbody>
</table>
Index: xml-media-types.html
===================================================================
RCS file: /sources/public/2002/ws/desc/media-types/xml-media-types.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -C2 -d -r1.21 -r1.22
*** xml-media-types.html 4 Mar 2005 19:46:48 -0000 1.21
--- xml-media-types.html 9 Mar 2005 20:22:36 -0000 1.22
***************
*** 84,94 ****
1.2 <a href="#requirements">Requirements</a><br>
2 <a href="#declaration">Attributes for Declaring Content-Type</a><br>
! 2.1 <a href="#contentType">xmime:contentType attribute </a><br>
! 2.2 <a href="#expectedContentType">xmime:expectedContentType attribute </a><br>
! 3 <a href="#usage">Declaring Content-Type for binary data</a><br>
! 3.1 <a href="#role">Role of xmime:expectedContentType Schema annotation attribute</a><br>
4 <a href="#more-ex">Examples</a><br>
! 4.1 <a href="#static">Binary data with known media type</a><br>
! 4.2 <a href="#example-with-q-param">Binary data with preferred media type</a><br>
5 <a href="#normative-references">Normative References</a><br>
6 <a href="#informative-references">Informative References</a><br>
--- 84,94 ----
1.2 <a href="#requirements">Requirements</a><br>
2 <a href="#declaration">Attributes for Declaring Content-Type</a><br>
! 2.1 <a href="#contentType">xmime:contentType Attribute </a><br>
! 2.2 <a href="#expectedContentType">xmime:expectedContentType Attribute </a><br>
! 3 <a href="#usage">Declaring Content-Type for Binary Data</a><br>
! 3.1 <a href="#role">Role of xmime:expectedContentType Schema Annotation Attribute</a><br>
4 <a href="#more-ex">Examples</a><br>
! 4.1 <a href="#static">Binary Data with Known Media Type</a><br>
! 4.2 <a href="#example-with-q-param">Binary Data with Preferred Media Type</a><br>
5 <a href="#normative-references">Normative References</a><br>
6 <a href="#informative-references">Informative References</a><br>
***************
*** 105,109 ****
example, in messages sent and
received by Web services. There is also a need to express the
! content-type information using <a href="#XMLSchemaP2">[XML Schema: Datatypes]</a>, which
is the type system used by <a href="#wsdl20part1">[WSDL 2.0 Part 1]</a>.
This would allow XML-based applications, such as Web services, to utilize
--- 105,109 ----
example, in messages sent and
received by Web services. There is also a need to express the
! content-type information using <a href="#XMLSchemaP2">[XML Schema: Datatypes]</a> and <a href="#XMLSchemaP2">[XML Schema: Datatypes]</a>, which
is the type system used by <a href="#wsdl20part1">[WSDL 2.0 Part 1]</a>.
This would allow XML-based applications, such as Web services, to utilize
***************
*** 140,144 ****
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, <em>xsi:type</em>.
</p><div class="div2">
<h3><a id="notational" name="notational"></a>1.1 Notational Conventions</h3><p>The keywords "MUST",
--- 140,144 ----
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 <em>xsi:type</em>.
</p><div class="div2">
<h3><a id="notational" name="notational"></a>1.1 Notational Conventions</h3><p>The keywords "MUST",
***************
*** 147,160 ****
document are to be interpreted as described in <a href="#rfc2119">[IETF RFC 2119]</a>.
</p><p>This specification uses properties from the XML
! Information Set, see <a href="#XMLInfoSet">[XML Information Set]</a>. Such properties are
denoted by square brackets, e.g. [namespace name].
</p><p>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 <a href="#XMLInfoSet">[XML Information Set]</a>).
! </p><a id="tabnsprefixes" name="tabnsprefixes"></a><table border="1" summary="Mapping of prefixes used in this document to their associated namespace name"><caption>Table 1. Prefixes and Namespaces used in this specification</caption><tbody><tr><th>Prefix</th><th>Namespace</th><th>Definition</th></tr><tr><td>xmime</td><td>http://www.w3.org/@@@@/@@/xmlmime</td><td>Defined by this specification</td></tr><tr><td>xs</td><td>"http://www.w3.org/2001/XMLSchema"</td><td>Defined in the W3C XML Schema
! specification <a href="#XMLSchemaP1">[XML Schema: Structures]</a>, <a href="#XMLSchemaP2">[XML Schema: Datatypes]</a>.
! </td></tr></tbody></table><p>Namespace names of the general form "http://example.org/..."
and "http://example.com/..." represent application or
! context-dependent URIs <a href="#rfc2396">[IETF RFC 2396]</a>.
</p><p>All parts of this specification are normative, with the exception of
examples and sections explicitly marked as "Non-Normative".
--- 147,162 ----
document are to be interpreted as described in <a href="#rfc2119">[IETF RFC 2119]</a>.
</p><p>This specification uses properties from the XML
! Information Set (see <a href="#XMLInfoSet">[XML Information Set]</a>). Such properties are
denoted by square brackets, e.g. [namespace name].
</p><p>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 <a href="#XMLInfoSet">[XML Information Set]</a>).
! </p><a id="tabnsprefixes" name="tabnsprefixes"></a><table border="1" summary="Mapping of prefixes used in this document to their associated namespace name"><caption>Table 1. Prefixes and Namespaces used in this specification</caption><tbody><tr><th>Prefix</th><th>Namespace</th><th>Definition</th></tr><tr><td>xmime</td><td>http://www.w3.org/@@@@/@@/xmlmime</td><td>Defined by this specification</td></tr><tr><td>xs</td><td>"http://www.w3.org/2001/XMLSchema"</td><td>Defined in the W3C XML Schema specifications
! <a href="#XMLSchemaP1">[XML Schema: Structures]</a>, <a href="#XMLSchemaP2">[XML Schema: Datatypes]</a>.
! </td></tr><tr><td>xsi</td><td>"http://www.w3.org/2001/XMLSchema-instance"</td><td>Defined in the W3C XML Schema specification
! <a href="#XMLSchemaP1">[XML Schema: Structures]</a>.
! </td></tr></tbody></table><p>Namespace names of the general form "http://example.org/..."
and "http://example.com/..." represent application or
! context-dependent URIs (see <a href="#rfc3986">[IETF RFC 3986]</a>).
</p><p>All parts of this specification are normative, with the exception of
examples and sections explicitly marked as "Non-Normative".
***************
*** 171,176 ****
define the set of 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 to
! further specify whether it is "jpeg", "gif", etc. This meta-data is
not required to be present.
</p></li><li><p>Define the acceptable format of content-type values. </p></li><li><p>Define the relationship between the expected and the
--- 173,178 ----
define the set of 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", or "gif". This meta-data is
not required to be present.
</p></li><li><p>Define the acceptable format of content-type values. </p></li><li><p>Define the relationship between the expected and the
***************
*** 179,196 ****
</p></li></ol></div></div><div class="div1">
<h2><a id="declaration" name="declaration"></a>2 Attributes for Declaring Content-Type</h2><p>This section defines two global <em>attribute information item</em>s for
! declaring the content-type of binary data in XML Schema to address the
! requirements (1) and (2) above. Their usage is addressed in Section <a href="#usage"><b>3 Declaring Content-Type for binary data</b></a>.
</p><div class="div2">
! <h3><a id="contentType" name="contentType"></a>2.1 xmime:contentType attribute </h3><p>
The <code>xmime:contentType</code> <em>attribute information item</em> has the following Infoset properties:
</p><ul><li><p>A [local name] of <code>contentType</code>.</p></li><li><p>A [namespace name] of "http://www.w3.org/@@@@/@@/xmlmime".</p></li></ul><p>The type of the <code>xmime:contentType</code> <em>attribute information item</em> is
<em>xs:string</em> with a minimum length of three and all leading
and trailing white space characters are ignored.</p></div><div class="div2">
! <h3><a id="expectedContentType" name="expectedContentType"></a>2.2 xmime:expectedContentType attribute </h3><p> The <code>xmime:expectedContentType</code> <em>attribute information item</em> has the following Infoset properties:
</p><ul><li><p>A [local name] of <code>expectedContentType</code>.</p></li><li><p>A [namespace name] of <code>http://www.w3.org/@@@@/@@/xmlmime</code>.</p></li></ul><p>The type of the <code>xmime:expectedContentType</code> <em>attribute information item</em> is
<em>xs:string</em>.</p><p>The value and the meaning of the
<code>xmime:expectedContentType</code> attribute is similar to the value
! allowed for the 'Accept' header defined by HTTP 1.1
! specification, Section 14.1 <a href="#rfc2616">[IETF RFC 2616]</a> and MUST
follow the production rules defined in that section except for the
following:
--- 181,199 ----
</p></li></ol></div></div><div class="div1">
<h2><a id="declaration" name="declaration"></a>2 Attributes for Declaring Content-Type</h2><p>This section defines two global <em>attribute information item</em>s for
! declaring the content-type of binary data and expected content-type(s)
! of binary data in XML Schema to address
! requirements (1) and (2) above. Their usage is addressed in Section <a href="#usage"><b>3 Declaring Content-Type for Binary Data</b></a>.
</p><div class="div2">
! <h3><a id="contentType" name="contentType"></a>2.1 xmime:contentType Attribute </h3><p>
The <code>xmime:contentType</code> <em>attribute information item</em> has the following Infoset properties:
</p><ul><li><p>A [local name] of <code>contentType</code>.</p></li><li><p>A [namespace name] of "http://www.w3.org/@@@@/@@/xmlmime".</p></li></ul><p>The type of the <code>xmime:contentType</code> <em>attribute information item</em> is
<em>xs:string</em> with a minimum length of three and all leading
and trailing white space characters are ignored.</p></div><div class="div2">
! <h3><a id="expectedContentType" name="expectedContentType"></a>2.2 xmime:expectedContentType Attribute </h3><p> The <code>xmime:expectedContentType</code> <em>attribute information item</em> has the following Infoset properties:
</p><ul><li><p>A [local name] of <code>expectedContentType</code>.</p></li><li><p>A [namespace name] of <code>http://www.w3.org/@@@@/@@/xmlmime</code>.</p></li></ul><p>The type of the <code>xmime:expectedContentType</code> <em>attribute information item</em> is
<em>xs:string</em>.</p><p>The value and the meaning of the
<code>xmime:expectedContentType</code> attribute is similar to the value
! allowed for the <code>'Accept'</code> HTTP header defined by HTTP 1.1
! specification, Section 14.1 (see <a href="#rfc2616">[IETF RFC 2616]</a>) and MUST
follow the production rules defined in that section except for the
following:
***************
*** 199,210 ****
to:
<tbody><tr><td><pre>qdtext = <any CHAR except<">></pre></td></tr></tbody>
! This change is made to disallow non-US-ASCII OCTETs.</p></li></ol><p>The <code>xmime:expectedContentType</code> attribute is intended to be used
! as part of XML Schema annotation for a <em>binary element information item</em> declaration (see <a href="#usage"><b>3 Declaring Content-Type for binary data</b></a>).
</p></div></div><div class="div1">
! <h2><a id="usage" name="usage"></a>3 Declaring Content-Type for binary data</h2><p>Documents that want to specify additional content-type
information for binary data SHOULD denote this by using a <em>binary element information item</em>.
A <em>binary element information item</em> is an <em>element information item</em> defined with the following additional constraints.
</p><ul><li><p>An OPTIONAL <code>xmime:contentType</code> <em>attribute information item</em> as described above in
! <a href="#contentType"><b>2.1 xmime:contentType attribute </b></a>. </p></li><li><p>The <em>character information items</em> comprising the
[children] of the <em>element information item</em> MUST conform to the lexical constraints of
<em>xs:base64Binary</em> or <em>xs:hexBinary</em>.</p></li></ul><p>The [normalized value] of the <code>xmime:contentType</code> <em>attribute information item</em> MUST be
--- 202,222 ----
to:
<tbody><tr><td><pre>qdtext = <any CHAR except<">></pre></td></tr></tbody>
! This change is made to disallow non-US-ASCII OCTETs.</p></li></ol><p>The <code>xmime:expectedContentType</code> <em>attribute information item</em> is intended to be
! used as part of XML Schema annotation for a <em>binary element information item</em> declaration
! (see <a href="#usage"><b>3 Declaring Content-Type for Binary Data</b></a>). This <em>attribute information item</em> 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
! <code>xmime:contentType</code>. Users of this <em>attribute information item</em> are urged to
! use wild cards (for example, "image/*") with care as it may
! lead to interoperability problems. If the set of expected media types
! are known, a list of media types is RECOMMENDED instead of wild cards
! (for example, <code>"image/jpeg, image/png"</code>).
</p></div></div><div class="div1">
! <h2><a id="usage" name="usage"></a>3 Declaring Content-Type for Binary Data</h2><p>Documents that want to specify additional content-type
information for binary data SHOULD denote this by using a <em>binary element information item</em>.
A <em>binary element information item</em> is an <em>element information item</em> defined with the following additional constraints.
</p><ul><li><p>An OPTIONAL <code>xmime:contentType</code> <em>attribute information item</em> as described above in
! <a href="#contentType"><b>2.1 xmime:contentType Attribute </b></a>. </p></li><li><p>The <em>character information items</em> comprising the
[children] of the <em>element information item</em> MUST conform to the lexical constraints of
<em>xs:base64Binary</em> or <em>xs:hexBinary</em>.</p></li></ul><p>The [normalized value] of the <code>xmime:contentType</code> <em>attribute information item</em> MUST be
***************
*** 213,217 ****
Note that [normalized value] consists of normalized attribute value as
defined by <a href="#XMLInfoSet">[XML Information Set]</a> and does not mean that two
! equivalent ContentType values will be equal.
</p><p>The <code>xmime:contentType</code> <em>attribute information item</em> allows Web services applications to
optimize the handling of the binary data defined by a <em>binary element information item</em> and should
--- 225,230 ----
Note that [normalized value] consists of normalized attribute value as
defined by <a href="#XMLInfoSet">[XML Information Set]</a> and does not mean that two
! equivalent values of <code>xmime:contentType</code> will necessarily be
! equal.
</p><p>The <code>xmime:contentType</code> <em>attribute information item</em> allows Web services applications to
optimize the handling of the binary data defined by a <em>binary element information item</em> and should
***************
*** 233,241 ****
<xs:import namespace="http://www.w3.org/@@@@/@@/xmlmime"
! schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
<!-- This element has binary content and requires the xmime:contentType
! attribute that indicates the content-type of the binary content -->
! <xs:element name="MyBinaryData"/>
<xs:complexType>
<xs:simpleContent>
--- 246,254 ----
<xs:import namespace="http://www.w3.org/@@@@/@@/xmlmime"
! schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
<!-- 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>
***************
*** 248,254 ****
</xs:schema>
-
</pre></div></div><div class="div2">
! <h3><a id="role" name="role"></a>3.1 Role of xmime:expectedContentType Schema annotation attribute</h3><p>The <code>xmime:expectedContentType</code> attribute is used for annotating
XML Schema to indicate the expected range of content-type of the binary
element content and the expected range of values for
--- 261,266 ----
</xs:schema>
</pre></div></div><div class="div2">
! <h3><a id="role" name="role"></a>3.1 Role of xmime:expectedContentType Schema Annotation Attribute</h3><p>The <code>xmime:expectedContentType</code> attribute is used for annotating
XML Schema to indicate the expected range of content-type of the binary
element content and the expected range of values for
***************
*** 257,263 ****
be within the range specified by the <code>xmime:expectedContentType</code>
annotation attribute, if specified in the schema.
! Refer to 14.1 <a href="#rfc2616">[IETF RFC 2616]</a> on how to interpret content-type
ranges that may be defined with respect to actual content. When the
! <code>xmime:expectedContentType</code> annotation attribute contains a wildcard
("*") or a list of acceptable content-type separated by commas (","),
the schema SHOULD require
--- 269,275 ----
be within the range specified by the <code>xmime:expectedContentType</code>
annotation attribute, if specified in the schema.
! See Section 14.1 of <a href="#rfc2616">[IETF RFC 2616]</a> on how to interpret content-type
ranges that may be defined with respect to actual content. When the
! <code>xmime:expectedContentType</code> annotation attribute contains a wild card
("*") or a list of acceptable content-type separated by commas (","),
the schema SHOULD require
***************
*** 282,289 ****
the binary content. The schema annotation attribute
<code>xmime:expectedContentType</code> specifies that the media type
! of the binary content is 'image', but the
! subtype name is unknown.
</p><div class="exampleOuter">
! <div class="exampleHeader"><a id="eg-wildcard" name="eg-wildcard"></a>Example 2: Schema declaring an element with binary content and expected media type of "image/*"</div><div class="exampleInner"><pre>
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
--- 294,302 ----
the binary content. The schema annotation attribute
<code>xmime:expectedContentType</code> specifies that the media type
! of the binary content is 'image', and the subtype name is either 'jpeg'
! or 'png'.
</p><div class="exampleOuter">
! <div class="exampleHeader"><a id="eg-wildcard" name="eg-wildcard"></a>Example 2: Schema declaring an element with binary content and expected
! media type of "image/jpeg" or "image/png"</div><div class="exampleInner"><pre>
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
***************
*** 293,297 ****
<xs:import namespace="http://www.w3.org/@@@@/@@/xmlmime"
! schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
--- 306,310 ----
<xs:import namespace="http://www.w3.org/@@@@/@@/xmlmime"
! schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
***************
*** 307,315 ****
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmime:expectedContentType="image/*"/>
! </xs:element>
</xs:schema>
-
</pre></div></div><p>
The example document instance below conforms to the element
--- 320,326 ----
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmime:expectedContentType="image/jpeg, image/png"/>
</xs:schema>
</pre></div></div><p>
The example document instance below conforms to the element
***************
*** 325,329 ****
</pre></div></div></div></div><div class="div1">
<h2><a id="more-ex" name="more-ex"></a>4 Examples</h2><div class="div2">
! <h3><a id="static" name="static"></a>4.1 Binary data with known media type</h3><p>The example below consists of a binary element
whose media type is known in
advance to be "image/jpeg".
--- 336,340 ----
</pre></div></div></div></div><div class="div1">
<h2><a id="more-ex" name="more-ex"></a>4 Examples</h2><div class="div2">
! <h3><a id="static" name="static"></a>4.1 Binary Data with Known Media Type</h3><p>The example below consists of a binary element
whose media type is known in
advance to be "image/jpeg".
***************
*** 350,356 ****
</xs:schema>
-
</pre></div></div></div><div class="div2">
! <h3><a id="example-with-q-param" name="example-with-q-param"></a>4.2 Binary data with preferred media type</h3><p>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).
--- 361,366 ----
</xs:schema>
</pre></div></div></div><div class="div2">
! <h3><a id="example-with-q-param" name="example-with-q-param"></a>4.2 Binary Data with Preferred Media Type</h3><p>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).
***************
*** 364,368 ****
<xs:import namespace="http://www.w3.org/@@@@/@@/xmlmime"
! schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
--- 374,378 ----
<xs:import namespace="http://www.w3.org/@@@@/@@/xmlmime"
! schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
***************
*** 375,432 ****
</xs:complexType>
! <xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
xmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
-
</pre></div></div></div></div><div class="div1">
! <h2><a id="normative-references" name="normative-references"></a>5 Normative References</h2><dl><dt class="label"><a id="XMLSchemaP1" name="XMLSchemaP1"></a>XML Schema: Structures</dt><dd>
! <a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/"><cite>XML Schema Part 1: Structures</cite></a>,
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! Editors. World Wide Web Consortium, 2 May 2001.
! (See http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/.)</dd><dt class="label"><a id="XMLSchemaP2" name="XMLSchemaP2"></a>XML Schema: Datatypes</dt><dd>
!
! <a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/"><cite>XML Schema Part 2: Datatypes</cite></a>, P. Byron and
! A. Malhotra, Editors. World Wide Web Consortium, 2 May
! 2001.
! (See http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.)</dd><dt class="label"><a id="rfc2396" name="rfc2396"></a>IETF RFC 2396</dt><dd>
! <a href="http://www.ietf.org/rfc/rfc2396.txt"><cite>Uniform Resource Identifiers (URI): Generic
Syntax</cite></a>, T. Berners-Lee, R. Fielding,
! L. Masinter, Authors. Internet Engineering Task Force,
! August 1998.
! (See http://www.ietf.org/rfc/rfc2396.txt.)</dd><dt class="label"><a id="rfc2046" name="rfc2046"></a>IETF RFC 2046</dt><dd> <a href="http://www.ietf.org/rfcs/rfc2046.html"><cite>RFC 2046 - Multipurpose
! Internet Mail Extensions (MIME) Part Two: Media
! Types</cite></a>, N. Freed, N. Borenstein, November
1996.
(See http://www.ietf.org/rfcs/rfc2046.html.)</dd><dt class="label"><a id="rfc2616" name="rfc2616"></a>IETF RFC 2616</dt><dd>
<a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html"><cite>Hypertext Transfer Protocol--HTTP
! 1.1</cite></a>, R. Fieldingm, J. Gettys, J. Mogul,
! H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, Authors,
! W3C/MIT, June 1999.
(See http://www.w3.org/Protocols/rfc2616/rfc2616.html.)</dd><dt class="label"><a id="rfc2119" name="rfc2119"></a>IETF RFC 2119</dt><dd>
<a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement
Levels</cite></a>, S. Bradner, Author. Internet Engineering
Task Force, June 1999.
! (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a id="XMLInfoSet" name="XMLInfoSet"></a>XML Information Set</dt><dd>
! <a href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024/"><cite>XML Information Set (Second Edition)</cite></a>,
J. Cowan and R.
! Tobin, Editors. World Wide Web Consortium, 4 February 2004.
(See http://www.w3.org/TR/2001/REC-xml-infoset-20011024/.)</dd></dl></div><div class="div1">
<h2><a id="informative-references" name="informative-references"></a>6 Informative References</h2><dl><dt class="label"><a id="wsdl20part1" name="wsdl20part1"></a>WSDL 2.0 Part 1</dt><dd>
<a href="http://www.w3.org/TR/2004/WD-wsdl20-20040326/"><cite>Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
! Language.
! </cite></a>Roberto Chinnici, Martin Gudgin,
Jean-Jacques Moreau, Jeffrey Schlimmer, Sanjiva Weerawarana,
! World Wide Web Consortium,
! W3C Working Draft 26 March 2004
(See http://www.w3.org/TR/2004/WD-wsdl20-20040326/.)</dd><dt class="label"><a id="XOP" name="XOP"></a>XOP</dt><dd>
! <a href="http://www.w3.org/TR/2005/REC-xop10-20050125/"><cite>XML-binary Optimized Packaging</cite></a>Martin Gudgin, Noah
! Mendelsohn, Mark Nottingham, Herve Ruellan, W3C Recommendation 25
! January 2005
(See http://www.w3.org/TR/2005/REC-xop10-20050125/.)</dd><dt class="label"><a id="MTOM" name="MTOM"></a>MTOM</dt><dd>
<a href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/"><cite>SOAP Message Transmission Optimization
! Mechanism</cite></a>Martin Gudgin, Noah Mendelsohn, Mark Nottingham, Herve
! Ruellan, W3C Recommendation 25 January 2005
(See http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/.)</dd></dl></div></div><div class="back"><div class="div1">
<h2><a id="ack" name="ack"></a>A Acknowledgements</h2><p>This document is developed by the participants of the joint
--- 385,437 ----
</xs:complexType>
! <xs:element name="JPEGPeferredPicture"
! type="tns:JPEGPreferredPictureType"
xmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
</pre></div></div></div></div><div class="div1">
! <h2><a id="normative-references" name="normative-references"></a>5 Normative References</h2><dl><dt class="label"><a id="XMLSchemaP1" name="XMLSchemaP1"></a>XML Schema: Structures</dt><dd>
! <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>XML Schema Part 1: Structures Second Edition</cite></a>,
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
! Editors. World Wide Web Consortium Recommendation, 28 October 2004.
! (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a id="XMLSchemaP2" name="XMLSchemaP2"></a>XML Schema: Datatypes</dt><dd>
! <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML Schema Part 2: Datatypes Second Edition</cite></a>,
! P. Byron and A. Malhotra, Editors. World Wide Web Consortium
! Recommendation, 28 October 2004.
! (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a id="rfc3986" name="rfc3986"></a>IETF RFC 3986</dt><dd>
! <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifiers (URI): Generic
Syntax</cite></a>, T. Berners-Lee, R. Fielding,
! L. Masinter, January 2005.
! (See http://www.ietf.org/rfc/rfc3986.txt.)</dd><dt class="label"><a id="rfc2046" name="rfc2046"></a>IETF RFC 2046</dt><dd>
! <a href="http://www.ietf.org/rfcs/rfc2046.html"><cite>RFC 2046 - Multipurpose Internet Mail Extensions (MIME)
! Part Two: Media Types</cite></a>, N. Freed, N. Borenstein, November
1996.
(See http://www.ietf.org/rfcs/rfc2046.html.)</dd><dt class="label"><a id="rfc2616" name="rfc2616"></a>IETF RFC 2616</dt><dd>
<a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html"><cite>Hypertext Transfer Protocol--HTTP
! 1.1</cite></a>, R. Fielding, J. Gettys, J. Mogul,
! H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, June 1999.
(See http://www.w3.org/Protocols/rfc2616/rfc2616.html.)</dd><dt class="label"><a id="rfc2119" name="rfc2119"></a>IETF RFC 2119</dt><dd>
<a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement
Levels</cite></a>, S. Bradner, Author. Internet Engineering
Task Force, June 1999.
! (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a id="XMLInfoSet" name="XMLInfoSet"></a>XML Information Set</dt><dd>
! <a href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024/"><cite>XML Information Set (Second Edition)</cite></a>,
J. Cowan and R.
! Tobin, World Wide Web Consortium Recommendation, 4 February 2004.
(See http://www.w3.org/TR/2001/REC-xml-infoset-20011024/.)</dd></dl></div><div class="div1">
<h2><a id="informative-references" name="informative-references"></a>6 Informative References</h2><dl><dt class="label"><a id="wsdl20part1" name="wsdl20part1"></a>WSDL 2.0 Part 1</dt><dd>
<a href="http://www.w3.org/TR/2004/WD-wsdl20-20040326/"><cite>Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
! Language</cite></a>, Roberto Chinnici, Martin Gudgin,
Jean-Jacques Moreau, Jeffrey Schlimmer, Sanjiva Weerawarana,
! World Wide Web Consortium Working Draft 26 March 2004
(See http://www.w3.org/TR/2004/WD-wsdl20-20040326/.)</dd><dt class="label"><a id="XOP" name="XOP"></a>XOP</dt><dd>
! <a href="http://www.w3.org/TR/2005/REC-xop10-20050125/"><cite>XML-binary Optimized Packaging</cite></a>, Martin Gudgin,
! Noah Mendelsohn, Mark Nottingham, Herve Ruellan, W3C
! Recommendation, 25 January 2005
(See http://www.w3.org/TR/2005/REC-xop10-20050125/.)</dd><dt class="label"><a id="MTOM" name="MTOM"></a>MTOM</dt><dd>
<a href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/"><cite>SOAP Message Transmission Optimization
! Mechanism</cite></a>, Martin Gudgin, Noah Mendelsohn, Mark Nottingham, Herve
! Ruellan, W3C Recommendation, 25 January 2005
(See http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/.)</dd></dl></div></div><div class="back"><div class="div1">
<h2><a id="ack" name="ack"></a>A Acknowledgements</h2><p>This document is developed by the participants of the joint
***************
*** 442,447 ****
targetNamespace="http://www.w3.org/@@@@/@@/xmlmime" >
!
! <xs:attribute name="contentType">
<xs:simpleType>
<xs:restriction base="xs:string" >
--- 447,451 ----
targetNamespace="http://www.w3.org/@@@@/@@/xmlmime" >
! <xs:attribute name="contentType">
<xs:simpleType>
<xs:restriction base="xs:string" >
***************
*** 449,457 ****
</xs:restriction>
</xs:simpleType>
! </xs:attribute>
! <xs:attribute name="expectedContentType" type="xs:string" />
! <xs:complexType name="base64Binary" >
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
--- 453,461 ----
</xs:restriction>
</xs:simpleType>
! </xs:attribute>
! <xs:attribute name="expectedContentType" type="xs:string" />
! <xs:complexType name="base64Binary" >
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
***************
*** 459,465 ****
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
! <xs:complexType name="hexBinary" >
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
--- 463,469 ----
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
! <xs:complexType name="hexBinary" >
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
***************
*** 467,474 ****
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
</xs:schema>
-
</pre></div></div><div class="div1">
<h2><a id="changelog" name="changelog"></a>C Change Log (Non-Normative)</h2><table border="1"><caption>Changes since publication of Last Call WD.</caption><thead><tr><th>Who</th><th>When</th><th>What</th></tr></thead><tbody><tr><td>ASK</td><td>20050223</td><td>Incorporated resolution for issue 260. In section 2.2 removed
--- 471,477 ----
</xs:extension>
</xs:simpleContent>
! </xs:complexType>
</xs:schema>
</pre></div></div><div class="div1">
<h2><a id="changelog" name="changelog"></a>C Change Log (Non-Normative)</h2><table border="1"><caption>Changes since publication of Last Call WD.</caption><thead><tr><th>Who</th><th>When</th><th>What</th></tr></thead><tbody><tr><td>ASK</td><td>20050223</td><td>Incorporated resolution for issue 260. In section 2.2 removed
***************
*** 502,504 ****
values</td></tr><tr><td>ASK</td><td>20050304</td><td>Replaced the prefix 'xmlmime' with 'xmime' to address i18n
comment</td></tr><tr><td>ASK</td><td>20050304</td><td>Added a 'SHOULD' for 'charset' params for textual types to
! address i18n comment</td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
--- 505,510 ----
values</td></tr><tr><td>ASK</td><td>20050304</td><td>Replaced the prefix 'xmlmime' with 'xmime' to address i18n
comment</td></tr><tr><td>ASK</td><td>20050304</td><td>Added a 'SHOULD' for 'charset' params for textual types to
! address i18n comment</td></tr><tr><td>ASK</td><td>20050308</td><td>Added a recommendation to use list of media types over wild cards
! </td></tr><tr><td>ASK</td><td>20050309</td><td>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</td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 9 March 2005 20:22:39 UTC