- From: Anish.Karmarkar via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 02 Mar 2005 22:50:21 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/media-types
In directory hutz:/tmp/cvs-serv4912
Modified Files:
xml-media-types.xml xml-media-types.html
Log Message:
include LC comments resolutions
Index: xml-media-types.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/media-types/xml-media-types.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -C2 -d -r1.26 -r1.27
*** xml-media-types.xml 28 Oct 2004 15:26:48 -0000 1.26
--- xml-media-types.xml 2 Mar 2005 22:50:19 -0000 1.27
***************
*** 15,19 ****
<spec w3c-doctype="wd" role="&document.role;">
<header>
! <title>Assigning Media Types to Binary Data in XML</title>
<w3c-designation/>
<w3c-doctype>&document.status;</w3c-doctype>
--- 15,19 ----
<spec w3c-doctype="wd" role="&document.role;">
<header>
! <title>Describing Media Content of Binary Data in XML</title>
<w3c-designation/>
<w3c-doctype>&document.status;</w3c-doctype>
***************
*** 40,48 ****
<author>
<name>Anish Karmarkar</name>
! <affiliation>Oracle Corporation</affiliation>
</author>
<author>
<name>&Umit;</name>
! <affiliation>Oracle Corporation</affiliation>
</author>
</authlist>
--- 40,48 ----
<author>
<name>Anish Karmarkar</name>
! <affiliation>Oracle</affiliation>
</author>
<author>
<name>&Umit;</name>
! <affiliation>SAP (formerly of Oracle)</affiliation>
</author>
</authlist>
***************
*** 52,59 ****
<abstract>
<p>
! This document addresses the need to indicate the media type associated with
binary element content in an XML document and the need to specify, in XML
! Schema, the expected media type(s) associated with binary element content.
! It is expected that the additional information about the media type will be
used for optimizing the handling of binary data that is part of a Web
services message.
--- 52,59 ----
<abstract>
<p>
! This document addresses the need to indicate the content-type associated with
binary element content in an XML document and the need to specify, in XML
! Schema, the expected content-type(s) associated with binary element content.
! It is expected that the additional information about the content-type will be
used for optimizing the handling of binary data that is part of a Web
services message.
***************
*** 75,82 ****
MIME media type defined by <bibref ref="rfc2046"/>, as the
type system. For example, "image/jpeg", "application/pdf".
! There is a need to indicate the media 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 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
--- 75,82 ----
MIME media type defined by <bibref ref="rfc2046"/>, as the
type system. For example, "image/jpeg", "application/pdf".
! There is a need to indicate the 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
! 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
***************
*** 88,92 ****
representation of the <emph>xs:base64Binary</emph> type) in an
optimized way using MIME packaging. There is a desire to
! specify the media type information of such binary element content in a
standard way in the <bibref ref="XMLInfoSet"/> and not just in the
optimized serialization of that Infoset.
--- 88,92 ----
representation of the <emph>xs:base64Binary</emph> type) in an
optimized way using MIME packaging. There is a desire to
! specify the content-type information of such binary element content in a
standard way in the <bibref ref="XMLInfoSet"/> and not just in the
optimized serialization of that Infoset.
***************
*** 99,108 ****
<item>
<p>
! An attribute (<emph>xmlmime:contentType</emph>) to indicate the media
! type of an XML element content whose type is
<emph>xs:base64Binary</emph> or <emph>xs:hexBinary</emph>. The value
! of the attribute is the name of a IANA media type token (e.g.,
! "text/xml; charset=utf-16"). This attribute specifies the media type
! of the content of an element on which it occurs.
</p>
</item>
--- 99,108 ----
<item>
<p>
! An attribute (<emph>xmlmime:contentType</emph>) to indicate the
! content-type of an XML element content whose type is
<emph>xs:base64Binary</emph> or <emph>xs:hexBinary</emph>. The value
! of the attribute is a valid content-type string (e.g.,
! "text/xml; charset=utf-16"). This attribute specifies the content-type
! of the element content on which it occurs.
</p>
</item>
***************
*** 110,115 ****
<p>
A XML Schema annotation attribute
! (<emph>xmlmime:expectedMediaType</emph>) to indicate, in XML Schema, the
! expected media type(s) for an element content whose type is
<emph>xs:base64Binary</emph> or <emph>xs:hexBinary</emph>.
</p>
--- 110,115 ----
<p>
A XML Schema annotation attribute
! (<emph>xmlmime:expectedContentType</emph>) to indicate, in XML Schema, the
! expected content-type(s) for an element content whose type is
<emph>xs:base64Binary</emph> or <emph>xs:hexBinary</emph>.
</p>
***************
*** 118,130 ****
<p>
! The XML Schema annotation, <emph>xmlmime:expectedMediaType</emph>,
specifies the expected range of values for the
! <emph>xmlmime:contentType</emph> attribute and the expected range of media
! types for the binary element content.
</p>
<p>
Note that the use of this mechanism, in particular the
! <emph>contentType</emph> attribute, does not require the implementation,
! in whole or in part, of XML Schema.
</p>
--- 118,132 ----
<p>
! The XML Schema annotation, <emph>xmlmime:expectedContentType</emph>,
specifies the expected range of values for the
! <emph>xmlmime:contentType</emph> attribute and the expected range of
! content-type for the binary element content.
</p>
<p>
Note that the use of this mechanism, in particular the
! <emph>xmlmime:contentType</emph> 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, <emph>xsi:type</emph>.
</p>
***************
*** 162,173 ****
</tr>
- <tr><td>wsdl</td>
- <td>&wsdlns;</td>
- <td>Defined by the WSDL 2.0 specification. A normative XML Schema <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>
- document for the &wsdlns; namespace
- can be found at &wsdlns;.
- </td>
- </tr>
-
<tr><td>xs</td>
<td>"http://www.w3.org/2001/XMLSchema"</td>
--- 164,167 ----
***************
*** 186,189 ****
--- 180,186 ----
</p>
+ <p>All parts of this specification are normative, with the exception of
+ examples and sections explicitly marked as "Non-Normative".
+ </p>
</div2>
<div2 id="requirements">
***************
*** 195,202 ****
<olist>
<item>
! <p> Define how to indicate the media type of an XML element
content whose type is <emph>xs:base64Binary</emph> or
<emph>xs:hexBinary</emph>. This is meta-data that may be, but not
! required to, used by tools to infer the specific media type of binary
data.
</p>
--- 192,199 ----
<olist>
<item>
! <p> Define how to indicate the content-type of an XML element
content whose type is <emph>xs:base64Binary</emph> or
<emph>xs:hexBinary</emph>. This is meta-data that may be, but not
! required to, used by tools to infer the specific content-type of binary
data.
</p>
***************
*** 204,211 ****
<item>
! <p> Define how to indicate the expected media type(s) of
XML element content whose type is <emph>xs:base64Binary</emph> or
<emph>xs:hexBinary</emph> in XML Schema. This information is needed to
! define the set of media types 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
--- 201,208 ----
<item>
! <p> Define how to indicate the expected content-type(s) of
XML element content whose type is <emph>xs:base64Binary</emph> or
<emph>xs:hexBinary</emph> in XML Schema. This information is needed to
! 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
***************
*** 215,223 ****
</item>
! <item><p>Define the acceptable format of media type values. </p>
</item>
<item><p>Define the relationship between the expected and the
! actual value of the media types declared for binary data in XML
documents.
</p>
--- 212,220 ----
</item>
! <item><p>Define the acceptable format of content-type values. </p>
</item>
<item><p>Define the relationship between the expected and the
! actual value of the content-type declared for binary data in XML
documents.
</p>
***************
*** 230,237 ****
<div1 id="declaration">
! <head>Attributes for Declaring Media Types</head>
<p>This section defines two global &AII;s for
! declaring the media type of binary data in XML Schema to address the
requirements (1) and (2) above. Their usage is addressed in Section <specref
ref="usage"/>.
--- 227,234 ----
<div1 id="declaration">
! <head>Attributes for Declaring Content-Type</head>
<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"/>.
***************
*** 239,246 ****
<div2 id="contentType">
! <head>contentType attribute </head>
<p>
! The <att>contentType</att> &AII; has the following Infoset properties:
</p>
--- 236,243 ----
<div2 id="contentType">
! <head>xmlmime:contentType attribute </head>
<p>
! The <att>xmlmime:contentType</att> &AII; has the following Infoset properties:
</p>
***************
*** 250,290 ****
</ulist>
! <p>The type of the <att>contentType</att> &AII; is
! <emph>xs:string</emph>.</p>
</div2>
! <div2 id="expectedMediaType">
! <head>expectedMediaType attribute </head>
! <p> The <att>expectedMediaType</att> &AII; has the following Infoset properties:
</p>
<ulist>
! <item><p>A [local name] of <el>expectedMediaType</el>.</p></item>
<item><p>A [namespace name] of <el>&xmlmimens;</el>.</p></item>
</ulist>
! <p>The type of the <att>expectedMediaType</att> &AII; is
<emph>xs:string</emph>.</p>
<p>The value and the meaning of the
! <att>expectedMediaType</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. The 'q'
! parameter defined by HTTP 1.1 specification, Section 3.9
! <bibref ref="rfc2616"/> is allowed, but other accept-extensions
! are not allowed.
</p>
! <ednote>
! <name></name>
! <edtext>
! The 'accept-extensions' of the HTTP 'Accept' header are not allowed in the 'expectedMediaType' attribute value. The WSD WG would like to solicit feedback on this.
! </edtext>
! </ednote>
!
! <p>The <att>expectedMediaType</att> attribute is intended to be used
as part of XML Schema annotation for a &BEII; declaration (see <specref
ref="usage"/>).
--- 247,291 ----
</ulist>
! <p>The type of the <att>xmlmime:contentType</att> &AII; is
! <emph>xs:string</emph> with a minimum length of three and all leading
! and trailing white space characters are ignored.</p>
</div2>
! <div2 id="expectedContentType">
! <head>xmlmime:expectedContentType attribute </head>
! <p> The <att>xmlmime:expectedContentType</att> &AII; has the following Infoset properties:
</p>
<ulist>
! <item><p>A [local name] of <el>expectedContentType</el>.</p></item>
<item><p>A [namespace name] of <el>&xmlmimens;</el>.</p></item>
</ulist>
! <p>The type of the <att>xmlmime:expectedContentType</att> &AII; is
<emph>xs:string</emph>.</p>
<p>The value and the meaning of the
! <att>xmlmime: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:
</p>
+ <olist>
+ <item>
+ <p>The prefix <emph>"Accept:"</emph> MUST NOT be used.</p>
+ </item>
+ <item>
+ <p>The rule <emph>qdtext</emph> is changed from:
+ <bnf>qdtext = <any TEXT except<">></bnf>
+ to:
+ <bnf>qdtext = <any CHAR except<">></bnf>
+ This change is made to disallow non-US-ASCII OCTETs.</p>
+ </item>
+ </olist>
! <p>The <att>xmlmime:expectedContentType</att> attribute is intended to be used
as part of XML Schema annotation for a &BEII; declaration (see <specref
ref="usage"/>).
***************
*** 294,300 ****
<div1 id="usage">
! <head>Declaring media types for binary data</head>
! <p>Documents that want to specify additional media type
information for binary data SHOULD denote this by using a &BEII;.
A &BEII; is an &EII; defined with the following additional constraints.
--- 295,301 ----
<div1 id="usage">
! <head>Declaring Content-Type for binary data</head>
! <p>Documents that want to specify additional content-type
information for binary data SHOULD denote this by using a &BEII;.
A &BEII; is an &EII; defined with the following additional constraints.
***************
*** 302,306 ****
<ulist>
! <item><p>An OPTIONAL <att>contentType</att> &AII; as described above in
<specref ref="contentType"/>. </p>
</item>
--- 303,307 ----
<ulist>
! <item><p>An OPTIONAL <att>xmlmime:contentType</att> &AII; as described above in
<specref ref="contentType"/>. </p>
</item>
***************
*** 311,330 ****
</ulist>
! <p>The [normalized value] of the <att>contentType</att> &AII; MUST be
! the name of a IANA media type token, e.g., "image/png", "text/xml;
! charset=utf-16" and indicates the media type of the [owner element].
</p>
! <p>The <att>contentType</att> &AII; allows Web services applications to
optimize the handling of the binary data defined by a &BEII; and should
! be considered as meta-data. The presence of the <att>contentType</att>
attribute does not changes the value of the element content.
</p>
<p>For authoring convenience, two types <att>xmlmime:base64Binary</att>
! and <att>xmlmime:hexBinary</att> are defined in <specref ref="appendix"/>
</p>
<example id="eg-ct-required">
! <head>Element with binary content and contentType attribute</head>
<eg xml:space="preserve">
<?xml version="1.0" ?>
--- 312,334 ----
</ulist>
! <p>The [normalized value] of the <att>xmlmime:contentType</att> &AII; MUST be
! a valid Content-Type string, e.g., "image/png", "text/xml;
! charset=utf-16" and indicates the content-type of the [owner element].
! 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>
! <p>The <att>xmlmime:contentType</att> &AII; allows Web services applications to
optimize the handling of the binary data defined by a &BEII; and should
! be considered as meta-data. The presence of the <att>xmlmime:contentType</att>
attribute does not changes the value of the element content.
</p>
<p>For authoring convenience, two types <att>xmlmime:base64Binary</att>
! and <att>xmlmime:hexBinary</att> are defined in <specref ref="schema"/>
</p>
<example id="eg-ct-required">
! <head>Element with binary content and xmlmime:contentType attribute</head>
<eg xml:space="preserve">
<?xml version="1.0" ?>
***************
*** 337,342 ****
schemaLocation="&xmlmimens;"/>
! <!-- This element has binary content and requires the contentType
! attribute that indicates the media type of the binary content -->
<xs:element name="MyBinaryData"/>
<xs:complexType>
--- 341,346 ----
schemaLocation="&xmlmimens;"/>
! <!-- This element has binary content and requires the xmlmime:contentType
! attribute that indicates the content-type of the binary content -->
<xs:element name="MyBinaryData"/>
<xs:complexType>
***************
*** 355,382 ****
<div2 id="role">
! <head>Role of expectedMediaType Schema annotation attribute</head>
! <p>The <att>expectedMediaType</att> attribute is used for annotating
! XML Schema to indicate the expected range of media types of the binary
element content and the expected range of values for
! <att>contentType</att> attribute.
</p>
! <p>The value of the <att>contentType</att> attribute, if present, SHOULD
! be within the range specified by the <att>expectedMediaType</att>
! annotation attribute, if specified in the schema. When the
! <att>expectedMediaType</att> annotation attribute has a wildcard
! ("*") or a list of acceptable media types, the schema SHOULD require
! the <att>contentType</att> attribute to be present.
</p>
! <p>Applications that need to specify expected media types SHOULD
use the schema annotation to declare the range of expected
values.
! <att>expectedMediaType</att> annotation attribute MAY be used in
conjunction with the declaration of &BEII;s or with complex type
definitions that are derived from <emph>xs:base64Binary</emph>
or <emph>xs:hexBinary</emph> in XML Schema. If the
! <att>expectedMediaType</att> annotation attribute is used in
both the &BEII; declaration as well as definition of the complex type
which the &BEII; belongs to, then the expected range of values defined
--- 359,389 ----
<div2 id="role">
! <head>Role of xmlmime:expectedContentType Schema annotation attribute</head>
! <p>The <att>xmlmime:expectedContentType</att> 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
! <att>xmlmime:contentType</att> attribute.
</p>
! <p>The value of the <att>xmlmime:contentType</att> attribute, if present, SHOULD
! be within the range specified by the <att>xmlmime: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>xmlmime:expectedContentType</att> annotation attribute contains a wildcard
! ("*") or a list of acceptable content-type separated by commas (","),
! the schema SHOULD require
! the <att>xmlmime:contentType</att> attribute to be present.
</p>
! <p>Applications that need to specify expected content-type SHOULD
use the schema annotation to declare the range of expected
values.
! <att>xmlmime:expectedContentType</att> annotation attribute MAY be used in
conjunction with the declaration of &BEII;s or with complex type
definitions that are derived from <emph>xs:base64Binary</emph>
or <emph>xs:hexBinary</emph> in XML Schema. If the
! <att>xmlmime:expectedContentType</att> annotation attribute is used in
both the &BEII; declaration as well as definition of the complex type
which the &BEII; belongs to, then the expected range of values defined
***************
*** 389,395 ****
and an element declaration, <el>Picture</el>. The
<att>xmlmime:contentType</att> attribute is required to be present
! and specifies the media type of
the binary content. The schema annotation attribute
! <att>xmlmime:expectedMediaType</att> specifies that the media type
of the binary content is 'image', but the
subtype name is unknown.
--- 396,402 ----
and an element declaration, <el>Picture</el>. The
<att>xmlmime:contentType</att> attribute is required to be present
! and specifies the content-type of
the binary content. The schema annotation attribute
! <att>xmlmime:expectedContentType</att> specifies that the media type
of the binary content is 'image', but the
subtype name is unknown.
***************
*** 419,423 ****
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmlmime:expectedMediaType="image/*"/>
</xs:element>
--- 426,430 ----
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmlmime:expectedContentType="image/*"/>
</xs:element>
***************
*** 434,438 ****
<example id="eg-wildcard-instance">
! <head>Document instance containing element with binary content type
"image/png"</head>
<eg xml:space="preserve">
--- 441,445 ----
<example id="eg-wildcard-instance">
! <head>Document instance containing element with binary content-type
"image/png"</head>
<eg xml:space="preserve">
***************
*** 478,482 ****
<xs:complexType name="JPEGPictureType"
type="xs:base64Binary"
! xmlmime:expectedMediaType="image/jpeg"/>
<xs:element name="JPEGPicture" type="tns:JpegPictureType"/>
--- 485,489 ----
<xs:complexType name="JPEGPictureType"
type="xs:base64Binary"
! xmlmime:expectedContentType="image/jpeg"/>
<xs:element name="JPEGPicture" type="tns:JpegPictureType"/>
***************
*** 519,523 ****
<xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
! xmlmime:expectedMediaType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
--- 526,530 ----
<xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
! xmlmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
***************
*** 526,529 ****
--- 533,537 ----
</example>
+ <!--
<ednote>
<name></name>
***************
*** 539,542 ****
--- 547,551 ----
</edtext>
</ednote>
+ -->
</div2>
***************
*** 546,551 ****
</div1>
! <div1 id="references">
! <head>References</head>
<blist>
--- 555,560 ----
</div1>
! <div1 id="normative-references">
! <head>Normative References</head>
<blist>
***************
*** 576,580 ****
<bibl key="IETF RFC 2046"
! id="rfc2046" href="http://www.faqs.org/rfcs/rfc2046.html"> <titleref>RFC 2046 - Multipurpose
Internet Mail Extensions (MIME) Part Two: Media
Types</titleref>, N. Freed, N. Borenstein, November
--- 585,589 ----
<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
***************
*** 601,619 ****
<bibl id="XMLInfoSet" key="XML Information Set"
href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024/">
! <titleref>XML Information Set</titleref>, J. Cowan and R.
! Tobin, Editors. World Wide Web Consortium, 24 October 2001.
</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="wsdl20part1"
--- 610,625 ----
<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>
! </blist>
! </div1>
!
! <div1 id="informative-references">
! <head>Informative References</head>
!
! <blist>
<bibl id="wsdl20part1"
***************
*** 629,643 ****
</bibl>
! <bibl id="XOP" key="XOP" href="http://www.w3.org/TR/2004/WD-xop10-20040209/">
! <titleref>XML-binary Optimized Packaging</titleref>, Noah
! Mendelsohn, Mark Nottingham, Herve Ruellan, W3C Working Draft 09 February 2004
</bibl>
! <bibl id="MTOM" key="MTOM" href="http://www.w3.org/TR/2004/WD-soap12-mtom-20040209/">
<titleref>SOAP Message Transmission Optimization
! Mechanism</titleref> Noah Mendelsohn, Mark Nottingham, Herve
! Ruellan, W3C Working Draft 09 February 2004
</bibl>
<!--
<bibl id="paswa" key="PASWA" href="http://www.gotdotnet.com/team/jeffsch/paswa/paswa61.html">
--- 635,662 ----
</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">
***************
*** 669,674 ****
</div1>
! <div1 id="appendix">
! <head>Appendix Schema</head>
<!--
--- 688,693 ----
</div1>
! <div1 id="schema">
! <head>Schema</head>
<!--
***************
*** 693,705 ****
</xs:attribute>
-->
! <xs:attribute name="contentType" type="xs:string" />
<!--
! <xs:element name="expectedMediaType" >
<xs:simpleType>
! <xs:list itemType="xmlmime:expectedMediaTypeItem" />
</xs:simpleType>
</xs:element>
! <xs:simpleType name="expectedMediaTypeItem" >
<xs:restriction base="xs:string" >
<xs:pattern value="(text|application|image|audio|video|model|x-[-.a-z0-9]+)/
--- 712,730 ----
</xs:attribute>
-->
! <xs:attribute name="contentType">
! <xs:simpleType>
! <xs:restriction base="xs:string" >
! <xs:minLength value="3" />
! </xs:restriction>
! </xs:simpleType>
! </xs:attribute>
<!--
! <xs:element name="expectedContentType" >
<xs:simpleType>
! <xs:list itemType="xmlmime:expectedContentType" />
</xs:simpleType>
</xs:element>
! <xs:simpleType name="expectedContentType" >
<xs:restriction base="xs:string" >
<xs:pattern value="(text|application|image|audio|video|model|x-[-.a-z0-9]+)/
***************
*** 708,712 ****
</xs:simpleType>
-->
! <xs:attribute name="expectedMediaType" type="xs:string" />
<xs:complexType name="base64Binary" >
--- 733,737 ----
</xs:simpleType>
-->
! <xs:attribute name="expectedContentType" type="xs:string" />
<xs:complexType name="base64Binary" >
***************
*** 730,733 ****
--- 755,873 ----
</eg>
</div1>
+
+ <inform-div1 id="changelog">
+ <head>Change Log</head>
+ <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
+ the sentence starting with "The 'q' parameter defined ..." and
+ the editorial note seeking feedback.</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>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</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>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. </td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Incorporated resolution for issue 261 specified in
+ http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0013.html
+ </td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Incorporated resolution for issue 262 specified in
+ http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0014.html</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>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 </td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>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.</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Removed the namespace prefix for wsdl in the table</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Resolved issue 254 by removing all ed notes</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Resolved issue 255 by updating the infoset ref to 2nd ed.</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Resolved issue 264 by accepting the proposal in the issue email
+ (used the prefix 'xmlmime' for all occurences of
+ expectedMediaType and contentType attribute)</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>Resolved issue 265 by updating the mtom and xop ref to REC</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050223</td>
+ <td>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</td>
+ </tr>
+ <tr>
+ <td>ASK</td>
+ <td>20050228</td>
+ <td>Resolved issue 270 by including language that clarifies that
+ [normalized value] does not mean normalization of ContentType
+ values</td>
+ </tr>
+ </tbody>
+ </table>
+ </inform-div1>
+
</back>
</spec>
Index: xml-media-types.html
===================================================================
RCS file: /sources/public/2002/ws/desc/media-types/xml-media-types.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** xml-media-types.html 25 Oct 2004 17:24:04 -0000 1.19
--- xml-media-types.html 2 Mar 2005 22:50:19 -0000 1.20
***************
*** 1,754 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
! <head>
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Assigning Media Types to Binary Data in XML</title>
!
! <style type="text/css">
! /*<![CDATA[*/
[...1224 lines suppressed...]
! http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0014.html</td></tr><tr><td>ASK</td><td>20050223</td><td>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 </td></tr><tr><td>ASK</td><td>20050223</td><td>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.</td></tr><tr><td>ASK</td><td>20050223</td><td>Removed the namespace prefix for wsdl in the table</td></tr><tr><td>ASK</td><td>20050223</td><td>Resolved issue 254 by removing all ed notes</td></tr><tr><td>ASK</td><td>20050223</td><td>Resolved issue 255 by updating the infoset ref to 2nd ed.</td></tr><tr><td>ASK</td><td>20050223</td><td>Resolved issue 264 by accepting the proposal in the issue email
! (used the prefix 'xmlmime' for all occurences of
! expectedMediaType and contentType attribute)</td></tr><tr><td>ASK</td><td>20050223</td><td>Resolved issue 265 by updating the mtom and xop ref to REC</td></tr><tr><td>ASK</td><td>20050223</td><td>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</td></tr><tr><td>ASK</td><td>20050228</td><td>Resolved issue 270 by including language that clarifies that
! [normalized value] does not mean normalization of ContentType
! values</td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 2 March 2005 22:50:21 UTC