- From: Anish.Karmarkar via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 04 Mar 2005 19:46:51 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/media-types
In directory hutz:/tmp/cvs-serv32456
Modified Files:
xml-media-types.xml xml-media-types.html
Log Message:
included the recommendations in 2a and 3 of i18n comments
Index: xml-media-types.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/media-types/xml-media-types.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -d -r1.27 -r1.28
*** xml-media-types.xml 2 Mar 2005 22:50:19 -0000 1.27
--- xml-media-types.xml 4 Mar 2005 19:46:48 -0000 1.28
***************
*** 99,103 ****
<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
--- 99,103 ----
<item>
<p>
! An attribute (<emph>xmime: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
***************
*** 110,114 ****
<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>.
--- 110,114 ----
<p>
A XML Schema annotation attribute
! (<emph>xmime: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>.
***************
*** 118,129 ****
<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
--- 118,129 ----
<p>
! The XML Schema annotation, <emph>xmime:expectedContentType</emph>,
specifies the expected range of values for the
! <emph>xmime: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>xmime: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
***************
*** 159,163 ****
<th>Definition</th>
</tr>
! <tr><td>xmlmime</td>
<td>&xmlmimens;</td>
<td>Defined by this specification</td>
--- 159,163 ----
<th>Definition</th>
</tr>
! <tr><td>xmime</td>
<td>&xmlmimens;</td>
<td>Defined by this specification</td>
***************
*** 236,243 ****
<div2 id="contentType">
! <head>xmlmime:contentType attribute </head>
<p>
! The <att>xmlmime:contentType</att> &AII; has the following Infoset properties:
</p>
--- 236,243 ----
<div2 id="contentType">
! <head>xmime:contentType attribute </head>
<p>
! The <att>xmime:contentType</att> &AII; has the following Infoset properties:
</p>
***************
*** 247,251 ****
</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>
--- 247,251 ----
</ulist>
! <p>The type of the <att>xmime: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>
***************
*** 254,260 ****
<div2 id="expectedContentType">
! <head>xmlmime:expectedContentType attribute </head>
! <p> The <att>xmlmime:expectedContentType</att> &AII; has the following Infoset properties:
</p>
--- 254,260 ----
<div2 id="expectedContentType">
! <head>xmime:expectedContentType attribute </head>
! <p> The <att>xmime:expectedContentType</att> &AII; has the following Infoset properties:
</p>
***************
*** 264,272 ****
</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
--- 264,272 ----
</ulist>
! <p>The type of the <att>xmime:expectedContentType</att> &AII; is
<emph>xs:string</emph>.</p>
<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
***************
*** 287,291 ****
</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"/>).
--- 287,291 ----
</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"/>).
***************
*** 303,307 ****
<ulist>
! <item><p>An OPTIONAL <att>xmlmime:contentType</att> &AII; as described above in
<specref ref="contentType"/>. </p>
</item>
--- 303,307 ----
<ulist>
! <item><p>An OPTIONAL <att>xmime:contentType</att> &AII; as described above in
<specref ref="contentType"/>. </p>
</item>
***************
*** 312,316 ****
</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].
--- 312,316 ----
</ulist>
! <p>The [normalized value] of the <att>xmime: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].
***************
*** 320,339 ****
</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" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/ct-required"
! xmlns:xmlmime="&xmlmimens;"
targetNamespace="http://example.com/ct-required">
--- 320,344 ----
</p>
! <p>The <att>xmime: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>xmime:contentType</att>
attribute does not changes the value of the element content.
</p>
! <p>If the media type identified by the value of an
! <att>xmime:contentType</att> attribute information item is a text
! based media type then the value of the <att>xmime:contentType</att>
! attribute information item SHOULD include a <att>charset</att> parameter.
! </p>
! <p>For authoring convenience, two types <att>xmime:base64Binary</att>
! and <att>xmime:hexBinary</att> are defined in <specref ref="schema"/>
</p>
<example id="eg-ct-required">
! <head>Element with binary content and xmime:contentType attribute</head>
<eg xml:space="preserve">
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/ct-required"
! xmlns:xmime="&xmlmimens;"
targetNamespace="http://example.com/ct-required">
***************
*** 341,345 ****
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"/>
--- 346,350 ----
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"/>
***************
*** 347,351 ****
<xs:simpleContent>
<xs:restriction base="xs:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" use="required"/>
</xs:restriction>
</xs:simpleContent>
--- 352,356 ----
<xs:simpleContent>
<xs:restriction base="xs:base64Binary" >
! <xs:attribute ref="xmime:contentType" use="required"/>
</xs:restriction>
</xs:simpleContent>
***************
*** 359,379 ****
<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>
--- 364,384 ----
<div2 id="role">
! <head>Role of xmime:expectedContentType Schema annotation attribute</head>
! <p>The <att>xmime: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>xmime:contentType</att> attribute.
</p>
! <p>The value of the <att>xmime:contentType</att> attribute, if present, SHOULD
! 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
! the <att>xmime:contentType</att> attribute to be present.
</p>
***************
*** 381,389 ****
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
--- 386,394 ----
use the schema annotation to declare the range of expected
values.
! <att>xmime: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>xmime: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
***************
*** 395,402 ****
The example below consists of a type definition, <el>PictureType</el>,
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.
--- 400,407 ----
The example below consists of a type definition, <el>PictureType</el>,
and an element declaration, <el>Picture</el>. The
! <att>xmime:contentType</att> attribute is required to be present
and specifies the content-type of
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.
***************
*** 408,412 ****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/wildcard"
! xmlns:xmlmime="&xmlmimens;"
targetNamespace="http://example.com/wildcard">
--- 413,417 ----
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/wildcard"
! xmlns:xmime="&xmlmimens;"
targetNamespace="http://example.com/wildcard">
***************
*** 417,422 ****
<xs:complexType name="PictureType">
<xs:simpleContent>
! <xs:restriction base="xmlmime:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
--- 422,427 ----
<xs:complexType name="PictureType">
<xs:simpleContent>
! <xs:restriction base="xmime:base64Binary" >
! <xs:attribute ref="xmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
***************
*** 426,430 ****
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmlmime:expectedContentType="image/*"/>
</xs:element>
--- 431,435 ----
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmime:expectedContentType="image/*"/>
</xs:element>
***************
*** 446,451 ****
<?xml version="1.0" ?>
<Picture xmlns="http://example.com/wildcard"
! xmlns:xmlmime="&xmlmimens;"
! xmlmime:contentType="image/png">/aWKKapGGyQ=</Picture>
</eg>
</example>
--- 451,456 ----
<?xml version="1.0" ?>
<Picture xmlns="http://example.com/wildcard"
! xmlns:xmime="&xmlmimens;"
! xmime:contentType="image/png">/aWKKapGGyQ=</Picture>
</eg>
</example>
***************
*** 476,480 ****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/know-type"
! xmlns:xmlmime="&xmlmimens;"
targetNamespace="http://example.com/know-type">
--- 481,485 ----
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/know-type"
! xmlns:xmime="&xmlmimens;"
targetNamespace="http://example.com/know-type">
***************
*** 485,489 ****
<xs:complexType name="JPEGPictureType"
type="xs:base64Binary"
! xmlmime:expectedContentType="image/jpeg"/>
<xs:element name="JPEGPicture" type="tns:JpegPictureType"/>
--- 490,494 ----
<xs:complexType name="JPEGPictureType"
type="xs:base64Binary"
! xmime:expectedContentType="image/jpeg"/>
<xs:element name="JPEGPicture" type="tns:JpegPictureType"/>
***************
*** 510,514 ****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/preferred-type"
! xmlns:xmlmime="&xmlmimens;"
targetNamespace="http://example.com/preferred-type">
--- 515,519 ----
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/preferred-type"
! xmlns:xmime="&xmlmimens;"
targetNamespace="http://example.com/preferred-type">
***************
*** 519,524 ****
<xs:complexType name="JPEGPreferredPictureType">
<xs:simpleContent>
! <xs:restriction base="xmlmime:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
--- 524,529 ----
<xs:complexType name="JPEGPreferredPictureType">
<xs:simpleContent>
! <xs:restriction base="xmime:base64Binary" >
! <xs:attribute ref="xmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
***************
*** 526,530 ****
<xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
! xmlmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
--- 531,535 ----
<xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
! xmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
***************
*** 699,703 ****
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns:xmlmime="&xmlmimens;"
targetNamespace="&xmlmimens;" >
--- 704,708 ----
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns:xmime="&xmlmimens;"
targetNamespace="&xmlmimens;" >
***************
*** 722,726 ****
<xs:element name="expectedContentType" >
<xs:simpleType>
! <xs:list itemType="xmlmime:expectedContentType" />
</xs:simpleType>
</xs:element>
--- 727,731 ----
<xs:element name="expectedContentType" >
<xs:simpleType>
! <xs:list itemType="xmime:expectedContentType" />
</xs:simpleType>
</xs:element>
***************
*** 738,742 ****
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" />
</xs:extension>
</xs:simpleContent>
--- 743,747 ----
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
! <xs:attribute ref="xmime:contentType" />
</xs:extension>
</xs:simpleContent>
***************
*** 746,750 ****
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
! <xs:attribute ref="xmlmime:contentType" />
</xs:extension>
</xs:simpleContent>
--- 751,755 ----
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
! <xs:attribute ref="xmime:contentType" />
</xs:extension>
</xs:simpleContent>
***************
*** 866,869 ****
--- 871,886 ----
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>
Index: xml-media-types.html
===================================================================
RCS file: /sources/public/2002/ws/desc/media-types/xml-media-types.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -d -r1.20 -r1.21
*** xml-media-types.html 2 Mar 2005 22:50:19 -0000 1.20
--- xml-media-types.html 4 Mar 2005 19:46:48 -0000 1.21
***************
*** 84,91 ****
1.2 <a href="#requirements">Requirements</a><br>
2 <a href="#declaration">Attributes for Declaring Content-Type</a><br>
! 2.1 <a href="#contentType">xmlmime:contentType attribute </a><br>
! 2.2 <a href="#expectedContentType">xmlmime:expectedContentType attribute </a><br>
3 <a href="#usage">Declaring Content-Type for binary data</a><br>
! 3.1 <a href="#role">Role of xmlmime: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>
--- 84,91 ----
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>
***************
*** 119,123 ****
This document specifies:
</p><ul><li><p>
! An attribute (<em>xmlmime:contentType</em>) to indicate the
content-type of an XML element content whose type is
<em>xs:base64Binary</em> or <em>xs:hexBinary</em>. The value
--- 119,123 ----
This document specifies:
</p><ul><li><p>
! An attribute (<em>xmime:contentType</em>) to indicate the
content-type of an XML element content whose type is
<em>xs:base64Binary</em> or <em>xs:hexBinary</em>. The value
***************
*** 127,141 ****
</p></li><li><p>
A XML Schema annotation attribute
! (<em>xmlmime:expectedContentType</em>) to indicate, in XML Schema, the
expected content-type(s) for an element content whose type is
<em>xs:base64Binary</em> or <em>xs:hexBinary</em>.
</p></li></ul><p>
! The XML Schema annotation, <em>xmlmime:expectedContentType</em>,
specifies the expected range of values for the
! <em>xmlmime:contentType</em> 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
! <em>xmlmime:contentType</em> 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
--- 127,141 ----
</p></li><li><p>
A XML Schema annotation attribute
! (<em>xmime:expectedContentType</em>) to indicate, in XML Schema, the
expected content-type(s) for an element content whose type is
<em>xs:base64Binary</em> or <em>xs:hexBinary</em>.
</p></li></ul><p>
! The XML Schema annotation, <em>xmime:expectedContentType</em>,
specifies the expected range of values for the
! <em>xmime:contentType</em> 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
! <em>xmime:contentType</em> 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
***************
*** 152,156 ****
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>xmlmime</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/..."
--- 152,156 ----
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/..."
***************
*** 182,194 ****
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 xmlmime:contentType attribute </h3><p>
! The <code>xmlmime: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>xmlmime: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 xmlmime:expectedContentType attribute </h3><p> The <code>xmlmime: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>xmlmime:expectedContentType</code> <em>attribute information item</em> is
<em>xs:string</em>.</p><p>The value and the meaning of the
! <code>xmlmime: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
--- 182,194 ----
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
***************
*** 199,203 ****
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>xmlmime: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">
--- 199,203 ----
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">
***************
*** 205,212 ****
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>xmlmime:contentType</code> <em>attribute information item</em> as described above in
! <a href="#contentType"><b>2.1 xmlmime: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>xmlmime:contentType</code> <em>attribute information item</em> 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].
--- 205,212 ----
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
a valid Content-Type string, e.g., "image/png", "text/xml;
charset=utf-16" and indicates the content-type of the [owner element].
***************
*** 214,229 ****
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>xmlmime: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
! be considered as meta-data. The presence of the <code>xmlmime:contentType</code>
attribute does not changes the value of the element content.
! </p><p>For authoring convenience, two types <code>xmlmime:base64Binary</code>
! and <code>xmlmime:hexBinary</code> are defined in <a href="#schema"><b>B Schema</b></a>
</p><div class="exampleOuter">
! <div class="exampleHeader"><a id="eg-ct-required" name="eg-ct-required"></a>Example 1: Element with binary content and xmlmime:contentType attribute</div><div class="exampleInner"><pre>
<?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/@@@@/@@/xmlmime"
targetNamespace="http://example.com/ct-required">
--- 214,233 ----
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
! be considered as meta-data. The presence of the <code>xmime:contentType</code>
attribute does not changes the value of the element content.
! </p><p>If the media type identified by the value of an
! <code>xmime:contentType</code> attribute information item is a text
! based media type then the value of the <code>xmime:contentType</code>
! attribute information item SHOULD include a <code>charset</code> parameter.
! </p><p>For authoring convenience, two types <code>xmime:base64Binary</code>
! and <code>xmime:hexBinary</code> are defined in <a href="#schema"><b>B Schema</b></a>
</p><div class="exampleOuter">
! <div class="exampleHeader"><a id="eg-ct-required" name="eg-ct-required"></a>Example 1: Element with binary content and xmime:contentType attribute</div><div class="exampleInner"><pre>
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/ct-required"
! xmlns:xmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/ct-required">
***************
*** 231,235 ****
schemaLocation="http://www.w3.org/@@@@/@@/xmlmime"/>
! <!-- This element has binary content and requires the xmlmime:contentType
attribute that indicates the content-type of the binary content -->
<xs:element name="MyBinaryData"/>
--- 235,239 ----
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"/>
***************
*** 237,241 ****
<xs:simpleContent>
<xs:restriction base="xs:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" use="required"/>
</xs:restriction>
</xs:simpleContent>
--- 241,245 ----
<xs:simpleContent>
<xs:restriction base="xs:base64Binary" >
! <xs:attribute ref="xmime:contentType" use="required"/>
</xs:restriction>
</xs:simpleContent>
***************
*** 246,270 ****
</pre></div></div><div class="div2">
! <h3><a id="role" name="role"></a>3.1 Role of xmlmime:expectedContentType Schema annotation attribute</h3><p>The <code>xmlmime: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
! <code>xmlmime:contentType</code> attribute.
! </p><p>The value of the <code>xmlmime:contentType</code> attribute, if present, SHOULD
! be within the range specified by the <code>xmlmime: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>xmlmime:expectedContentType</code> annotation attribute contains a wildcard
("*") or a list of acceptable content-type separated by commas (","),
the schema SHOULD require
! the <code>xmlmime:contentType</code> 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.
! <code>xmlmime:expectedContentType</code> annotation attribute MAY be used in
conjunction with the declaration of <em>binary element information item</em>s or with complex type
definitions that are derived from <em>xs:base64Binary</em>
or <em>xs:hexBinary</em> in XML Schema. If the
! <code>xmlmime:expectedContentType</code> annotation attribute is used in
both the <em>binary element information item</em> declaration as well as definition of the complex type
which the <em>binary element information item</em> belongs to, then the expected range of values defined
--- 250,274 ----
</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
! <code>xmime:contentType</code> attribute.
! </p><p>The value of the <code>xmime:contentType</code> attribute, if present, SHOULD
! 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
! the <code>xmime:contentType</code> 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.
! <code>xmime:expectedContentType</code> annotation attribute MAY be used in
conjunction with the declaration of <em>binary element information item</em>s or with complex type
definitions that are derived from <em>xs:base64Binary</em>
or <em>xs:hexBinary</em> in XML Schema. If the
! <code>xmime:expectedContentType</code> annotation attribute is used in
both the <em>binary element information item</em> declaration as well as definition of the complex type
which the <em>binary element information item</em> belongs to, then the expected range of values defined
***************
*** 274,281 ****
The example below consists of a type definition, <code>PictureType</code>,
and an element declaration, <code>Picture</code>. The
! <code>xmlmime:contentType</code> attribute is required to be present
and specifies the content-type of
the binary content. The schema annotation attribute
! <code>xmlmime:expectedContentType</code> specifies that the media type
of the binary content is 'image', but the
subtype name is unknown.
--- 278,285 ----
The example below consists of a type definition, <code>PictureType</code>,
and an element declaration, <code>Picture</code>. The
! <code>xmime:contentType</code> attribute is required to be present
and specifies the content-type of
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.
***************
*** 285,289 ****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/wildcard"
! xmlns:xmlmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/wildcard">
--- 289,293 ----
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/wildcard"
! xmlns:xmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/wildcard">
***************
*** 294,299 ****
<xs:complexType name="PictureType">
<xs:simpleContent>
! <xs:restriction base="xmlmime:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
--- 298,303 ----
<xs:complexType name="PictureType">
<xs:simpleContent>
! <xs:restriction base="xmime:base64Binary" >
! <xs:attribute ref="xmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
***************
*** 303,307 ****
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmlmime:expectedContentType="image/*"/>
</xs:element>
--- 307,311 ----
that the element definition will accept -->
<xs:element name="Picture" type="tns:PictureType"
! xmime:expectedContentType="image/*"/>
</xs:element>
***************
*** 317,322 ****
<?xml version="1.0" ?>
<Picture xmlns="http://example.com/wildcard"
! xmlns:xmlmime="http://www.w3.org/@@@@/@@/xmlmime"
! xmlmime:contentType="image/png">/aWKKapGGyQ=</Picture>
</pre></div></div></div></div><div class="div1">
<h2><a id="more-ex" name="more-ex"></a>4 Examples</h2><div class="div2">
--- 321,326 ----
<?xml version="1.0" ?>
<Picture xmlns="http://example.com/wildcard"
! xmlns:xmime="http://www.w3.org/@@@@/@@/xmlmime"
! xmime:contentType="image/png">/aWKKapGGyQ=</Picture>
</pre></div></div></div></div><div class="div1">
<h2><a id="more-ex" name="more-ex"></a>4 Examples</h2><div class="div2">
***************
*** 332,336 ****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/know-type"
! xmlns:xmlmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/know-type">
--- 336,340 ----
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/know-type"
! xmlns:xmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/know-type">
***************
*** 341,345 ****
<xs:complexType name="JPEGPictureType"
type="xs:base64Binary"
! xmlmime:expectedContentType="image/jpeg"/>
<xs:element name="JPEGPicture" type="tns:JpegPictureType"/>
--- 345,349 ----
<xs:complexType name="JPEGPictureType"
type="xs:base64Binary"
! xmime:expectedContentType="image/jpeg"/>
<xs:element name="JPEGPicture" type="tns:JpegPictureType"/>
***************
*** 356,360 ****
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/preferred-type"
! xmlns:xmlmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/preferred-type">
--- 360,364 ----
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/preferred-type"
! xmlns:xmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://example.com/preferred-type">
***************
*** 365,370 ****
<xs:complexType name="JPEGPreferredPictureType">
<xs:simpleContent>
! <xs:restriction base="xmlmime:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
--- 369,374 ----
<xs:complexType name="JPEGPreferredPictureType">
<xs:simpleContent>
! <xs:restriction base="xmime:base64Binary" >
! <xs:attribute ref="xmime:contentType" use="required" />
</xs:restriction>
</xs:simpleContent>
***************
*** 372,376 ****
<xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
! xmlmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
--- 376,380 ----
<xs:element name="JPEGPeferredPicture" type="tns:JPEGPreferredPictureType"
! xmime:expectedContentType="image/jpeg;q=1.0, image/tiff;q=0.8"/>
</xs:schema>
***************
*** 435,439 ****
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns:xmlmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://www.w3.org/@@@@/@@/xmlmime" >
--- 439,443 ----
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns:xmime="http://www.w3.org/@@@@/@@/xmlmime"
targetNamespace="http://www.w3.org/@@@@/@@/xmlmime" >
***************
*** 452,456 ****
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
! <xs:attribute ref="xmlmime:contentType" />
</xs:extension>
</xs:simpleContent>
--- 456,460 ----
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
! <xs:attribute ref="xmime:contentType" />
</xs:extension>
</xs:simpleContent>
***************
*** 460,464 ****
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
! <xs:attribute ref="xmlmime:contentType" />
</xs:extension>
</xs:simpleContent>
--- 464,468 ----
<xs:simpleContent>
<xs:extension base="xs:hexBinary" >
! <xs:attribute ref="xmime:contentType" />
</xs:extension>
</xs:simpleContent>
***************
*** 496,498 ****
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
--- 500,504 ----
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><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
Received on Friday, 4 March 2005 19:46:52 UTC