- From: Jonathan Marsh via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 22 Dec 2006 19:13:17 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv21006/wsdl20
Modified Files:
wsdl20-primer.html
Log Message:
Added spiff and references to the Guide to Versioning XML Languages using XML Schema 1.1.
Removed F&P from the infoset diagram.
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.170
retrieving revision 1.171
diff -C 2 -d -r1.170 -r1.171
*** wsdl20-primer.html 21 Dec 2006 15:22:23 -0000 1.170
--- wsdl20-primer.html 22 Dec 2006 19:13:14 -0000 1.171
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title><style type="text/css">
code { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title><style type="text/css">
code { font-family: monospace; }
***************
*** 93,97 ****
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br> 1.1 <a href="#Prerequisites">Prerequisites</a><br> 1.2 <a href="#PrimerStructure">Structure of this Primer</a><br> 1.3 <a href="#UseIRI">Use of URIs and IRIs</a><br> 1.4 <a href="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br> 2.1 <a href="#basic-example">Getting Started: The GreatH Hotel Example</a><br> 2.1.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br> 2.1.2 <a href="#basics-getting-started">Defining a WSDL 2.0 Target Namespace</a><br> 2.1.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br> &nbp; 2.1.3 <a href="#basics-types">Defining Message Types</a><br> 2.1.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br> 2.1.4 <a href="#basics-interface">Defining an Interface</a><br> 2.1.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br> 2.1.5 <a href="#basics-binding">Defining a Binding</a><br> 2.1.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br> 2.1.6 <a href="#basics-service">Defining a Service</a><br> 2.1.6.1 <a href="#example-initial-service-explanation">Explanatin of Example</a><br> 2.1.7 <a href="#basics-documentation">Documenting the Service</a><br> 2.1.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br> 2.2 <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br> 2.2.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br> 2.2.2 <a href="#wsdl-schema">WSDL 2.0 Schema</a><br> 2.2.2.1 <a href="#element-order">WSDL 2.0 Element Ordering</a><br> 2.2.3 <a href="#component-model">WSDL 2.0 Component Model</a><br> 2.2.3.1 <a href="#import-component">WSDL 2.0 Import and Include</a><br>&nbp; 2.3 <a href="#more-types">More on Message Types</a><br> 2.3.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br> 2.3.2 <a href="#more-types-schema-import">Importing XML Schema</a><br> 2.3.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br> 2.4 <a href="#more-interfaces">More on Interfaces</a><br> 2.4.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br> 2.4.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br> 2.4.3 <a href="#more-interfaces-faults">Interface Faults</a><br> 2.4.4 <a href="#more-interfaces-operations">Interface Operations</a><br> &bsp; 2.4.4.1 <a href="#more-interfaces-op-attr">Operation Attributes</a><br> 2.4.4.2 <a href="#N109C9">Operation Message References</a><br> 2.4.4.2.1 <a href="#N109E6">The messageLabel Attribute</a><br> 2.4.4.2.2 <a href="#N109FE">The element Attribute</a><br> 2.4.4.2.3 <a href="#N10A4F">Multiple infault or outfault Elements</a><br> 2.4.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br> 2.5 <a href="#more-bindings">More on Bindings</a><br> nbsp; 2.5.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br> 2.5.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br> 2.5.3 <a href="#more-bindings-faults">Binding Faults</a><br> 2.5.4 <a href="#bindingOperations">Binding Operations</a><br> 2.5.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br> 2.5.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br> 2.5.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br> 2.5.6.1 <a href="#N10C17">Explanation of
Example</a><br> 2.5.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br> 3.1 <a href="#adv-import-and-authoring">Importing WSDL</a><br> 3.2 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br> 3.2.1 <a href="#N10D67">Schemas in Imported Documents</a><br> 3.2.2 <a href="#N10DF2">Multiple Inline Schemas in One Document</a><br> 3.2.3 <a href="#adv-schema-location">The schemaLocation Attribute</a><br> 3.2.3.1 <a href="#N10E52">Using the id Attribute to Identify Inline
! Schemas</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br> 4.1 <a href="#adv-extensibility">Extensibility</a><br> 4.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br> 4.2 <a href="#adv-MEP">Defining New MEPs</a><br> 4.2.1 <a href="#challenge-confirm">Confirmed Challenge</a><br> 4.3 <a href="#adv-RPCstyle">RPC Style</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br> 5.1 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br> 5.2 <a href="#adv-versioning">Web Service Versioning</a><br> 5.2.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br> .2.2 <a href="#adv-versioning-big-bang">Big Bang</a><br> 5.2.3 <a href="#ad-versioing-migration">Evolving a Service</a><br> 5.2.4 <a href="#adv-versioning-combined">Combined Approaches</a><br> 5.2.5 <a href="#adv-versioning-examples">Examples of Versioning and Extending a Service</a><br> 5.2.5.1 <a href="#N110DF">Additional Optional Elements Added in Content</a><br> 5.2.5.2 <a href="#N110F6">Additional Optional Elements Added to a Header</a><br> 5.2.5.3 <a href="#N1110D">Additional Mandatory Elements in Content</a><br> 5.2.5.4 <a href="#N11124">Additional Optional Operation Added to Interfae</a><br> 5.2.5.5 <a href="#N11130">Additional Mandatory Operation Added to Interface</a><br> 5.2.5.6 <a href="#N1114A">Indicating Incompatibility by Changing the Endpoint URI</a><br> 5.2.5.7 <a href="#N11153">Indicating Incompatibility by Changing the SOAP Action</a><br> 5.2.5.8 <a href="#N1116A">Indicating Incompatibility by Changing the Element Content</a><br> 5.3 <a href="#adv-service-references">
Describing Web Service Messages That Refer to Other Web
Services
--- 93,97 ----
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#Introduction">Introduction</a><br> 1.1 <a href="#Prerequisites">Prerequisites</a><br> 1.2 <a href="#PrimerStructure">Structure of this Primer</a><br> 1.3 <a href="#UseIRI">Use of URIs and IRIs</a><br> 1.4 <a href="#notation">Notational Conventions</a><br>2. <a href="#basics">WSDL 2.0 Basics</a><br> 2.1 <a href="#basic-example">Getting Started: The GreatH Hotel Example</a><br> 2.1.1 <a href="#basics-greath-scenario">Example Scenario: The GreatH Hotel Reservation Service</a><br> 2.1.2 <a href="#basics-getting-started">Defining a WSDL 2.0 Target Namespace</a><br> 2.1.2.1 <a href="#example-empty-shell-explanation">Explanation of Example</a><br> &nbp; 2.1.3 <a href="#basics-types">Defining Message Types</a><br> 2.1.3.1 <a href="#example-initial-types-explanation">Explanation of Example</a><br> 2.1.4 <a href="#basics-interface">Defining an Interface</a><br> 2.1.4.1 <a href="#example-initial-interface-explanation">Explanation of Example</a><br> 2.1.5 <a href="#basics-binding">Defining a Binding</a><br> 2.1.5.1 <a href="#example-initial-binding-explanation">Explanation of Example</a><br> 2.1.6 <a href="#basics-service">Defining a Service</a><br> 2.1.6.1 <a href="#example-initial-service-explanation">Explanatin of Example</a><br> 2.1.7 <a href="#basics-documentation">Documenting the Service</a><br> 2.1.7.1 <a href="#example-initial-documentation-explanation">Explanation of Example</a><br> 2.2 <a href="#wsdl-xml-representation">WSDL 2.0 Infoset, Schema and Component Model</a><br> 2.2.1 <a href="#wsdl-infoset-diagram">WSDL 2.0 Infoset</a><br> 2.2.2 <a href="#wsdl-schema">WSDL 2.0 Schema</a><br> 2.2.2.1 <a href="#element-order">WSDL 2.0 Element Ordering</a><br> 2.2.3 <a href="#component-model">WSDL 2.0 Component Model</a><br> 2.2.3.1 <a href="#import-component">WSDL 2.0 Import and Include</a><br>&nbp; 2.3 <a href="#more-types">More on Message Types</a><br> 2.3.1 <a href="#more-types-schema-inline">Inlining XML Schema</a><br> 2.3.2 <a href="#more-types-schema-import">Importing XML Schema</a><br> 2.3.3 <a href="#more-types-import-include-summary">Summary of Import and Include Mechanisms</a><br> 2.4 <a href="#more-interfaces">More on Interfaces</a><br> 2.4.1 <a href="#more-interfaces-interfaces">Interface Syntax </a><br> 2.4.2 <a href="#more-interfaces-inheritance">Interface Inheritance</a><br> 2.4.3 <a href="#more-interfaces-faults">Interface Faults</a><br> 2.4.4 <a href="#more-interfaces-operations">Interface Operations</a><br> &bsp; 2.4.4.1 <a href="#more-interfaces-op-attr">Operation Attributes</a><br> 2.4.4.2 <a href="#N109C9">Operation Message References</a><br> 2.4.4.2.1 <a href="#N109E6">The messageLabel Attribute</a><br> 2.4.4.2.2 <a href="#N109FE">The element Attribute</a><br> 2.4.4.2.3 <a href="#N10A4F">Multiple infault or outfault Elements</a><br> 2.4.4.3 <a href="#more-interfaces-meps">Understanding Message Exchange Patterns (MEPs)</a><br> 2.5 <a href="#more-bindings">More on Bindings</a><br> nbsp; 2.5.1 <a href="#more-bindings-wsdl">Syntax Summary for Bindings</a><br> 2.5.2 <a href="#more-bindings-reusable">Reusable Bindings</a><br> 2.5.3 <a href="#more-bindings-faults">Binding Faults</a><br> 2.5.4 <a href="#bindingOperations">Binding Operations</a><br> 2.5.5 <a href="#more-bindings-soap">The SOAP Binding Extension</a><br> 2.5.5.1 <a href="#more-bindings-soap-example-explanation">Explanation of Example</a><br> 2.5.6 <a href="#more-bindings-http">The HTTP Binding Extension</a><br> 2.5.6.1 <a href="#N10C17">Explanation of
Example</a><br> 2.5.7 <a href="#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br>3. <a href="#advanced-topic_ii">Advanced Topics I: Importing Mechanisms</a><br> 3.1 <a href="#adv-import-and-authoring">Importing WSDL</a><br> 3.2 <a href="#adv-multiple-inline-schemas">Importing Schemas</a><br> 3.2.1 <a href="#N10D67">Schemas in Imported Documents</a><br> 3.2.2 <a href="#N10DF2">Multiple Inline Schemas in One Document</a><br> 3.2.3 <a href="#adv-schema-location">The schemaLocation Attribute</a><br> 3.2.3.1 <a href="#N10E52">Using the id Attribute to Identify Inline
! Schemas</a><br>4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility and Predefined Extensions</a><br> 4.1 <a href="#adv-extensibility">Extensibility</a><br> 4.1.1 <a href="#adv-optional-versus-required">Optional Versus Required Extensions</a><br> 4.2 <a href="#adv-MEP">Defining New MEPs</a><br> 4.2.1 <a href="#challenge-confirm">Confirmed Challenge</a><br> 4.3 <a href="#adv-RPCstyle">RPC Style</a><br>5. <a href="#advanced-topic_iv">Advanced Topics III: Miscellaneous</a><br> 5.1 <a href="#adv-message-dispatch">Enabling Easy Message Dispatch</a><br> 5.2 <a href="#adv-versioning">Web Service Versioning</a><br> 5.2.1 <a href="#adv-versioning-compatible-evolution">Compatible Evolution</a><br> .2.2 <a href="#adv-versioning-big-bang">Big Bang</a><br> 5.2.3 <a href="#ad-versioing-migration">Evolving a Service</a><br> 5.2.4 <a href="#adv-versioning-combined">Combined Approaches</a><br> 5.2.5 <a href="#adv-versioning-examples">Examples of Versioning and Extending a Service</a><br> 5.2.5.1 <a href="#N110EB">Additional Optional Elements Added in Content</a><br> 5.2.5.2 <a href="#N11102">Additional Optional Elements Added to a Header</a><br> 5.2.5.3 <a href="#N11119">Additional Mandatory Elements in Content</a><br> 5.2.5.4 <a href="#N11130">Additional Optional Operation Added to Interfae</a><br> 5.2.5.5 <a href="#N1113C">Additional Mandatory Operation Added to Interface</a><br> 5.2.5.6 <a href="#N11156">Indicating Incompatibility by Changing the Endpoint URI</a><br> 5.2.5.7 <a href="#N1115F">Indicating Incompatibility by Changing the SOAP Action</a><br> 5.2.5.8 <a href="#N11176">Indicating Incompatibility by Changing the Element Content</a><br> 5.3 <a href="#adv-service-references">
Describing Web Service Messages That Refer to Other Web
Services
***************
*** 2545,2550 ****
<ul><li><p>The <a href="http://www.w3.org/2001/tag/">Technical Architecture Group (TAG)</a> has published guidance on the extensibility and versioning of data formats in its Web Architecture document [<cite><a href="#webarch">Web Architecture</a></cite>]. There is also a more wide ranging draft finding on Versioning
and Extensibility [<cite><a href="#TAG-versioning">W3C TAG Finding: Versioning</a></cite>]. Both of these works build
! upon the technical note on Web Architecture: Extensible Languages [<cite><a href="#web-extensible">WebArch: Extensible Languages</a></cite>].</p></li><li><p>The <a href="http://www.w3.org/XML/Schema">XML Schema Working Group</a> is collecting a series of use cases
! for schema versioning as a part of the Schema 1.1 activity. See XML Schema Versioning Use Cases [<cite><a href="#xsd-versioning">XML Schema: Versioning Use-Cases</a></cite>].</p></li><li><p>The <a href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web Best Practices and Deployments Working Group</a> is
examining how vocabularies may evolve. See [<cite><a href="#sw-vocabulary">SW VocabManagementNote</a></cite>]</p></li></ul>
--- 2545,2553 ----
<ul><li><p>The <a href="http://www.w3.org/2001/tag/">Technical Architecture Group (TAG)</a> has published guidance on the extensibility and versioning of data formats in its Web Architecture document [<cite><a href="#webarch">Web Architecture</a></cite>]. There is also a more wide ranging draft finding on Versioning
and Extensibility [<cite><a href="#TAG-versioning">W3C TAG Finding: Versioning</a></cite>]. Both of these works build
! upon the technical note on Web Architecture: Extensible Languages [<cite><a href="#web-extensible">WebArch: Extensible Languages</a></cite>].</p></li>
! <li><p>The <a href="http://www.w3.org/XML/Schema">XML Schema Working Group</a> is collecting a series of use cases
! for schema versioning as a part of the Schema 1.1 activity. See XML Schema Versioning Use Cases [<cite><a href="#xsd-versioning">XML Schema: Versioning Use-Cases</a></cite>].</p></li>
! <li><p>The Guide to Versioning XML Languages using XML Schema 1.1 [<cite><a href="#xsd-versioning-guide">Guide to Versioning XML Languages using XML Schema 1.1</a></cite>] illustrates some techniques for versioning XML languages enabled by features of XML Schema 1.1 [<cite><a href="#xsd11">XML Schema 1.1</a></cite>].</p></li>
! <li><p>The <a href="http://www.w3.org/2001/sw/BestPractices/">Semantic Web Best Practices and Deployments Working Group</a> is
examining how vocabularies may evolve. See [<cite><a href="#sw-vocabulary">SW VocabManagementNote</a></cite>]</p></li></ul>
***************
*** 2643,2647 ****
<div class="div4">
! <h5><a name="N110DF"></a>5.2.5.1 Additional Optional Elements Added in Content</h5>
<p> The following example demonstrates how content may be extended with
additional content. The reservation service is changed to a newer version that can accept an optional
--- 2646,2650 ----
<div class="div4">
! <h5><a name="N110EB"></a>5.2.5.1 Additional Optional Elements Added in Content</h5>
<p> The following example demonstrates how content may be extended with
additional content. The reservation service is changed to a newer version that can accept an optional
***************
*** 2672,2676 ****
<div class="div4">
! <h5><a name="N110F6"></a>5.2.5.2 Additional Optional Elements Added to a Header</h5>
<p> Another option is to add the extension as a header block. This is
accomplished by defining an element for the extension and adding a
--- 2675,2679 ----
<div class="div4">
! <h5><a name="N11102"></a>5.2.5.2 Additional Optional Elements Added to a Header</h5>
<p> Another option is to add the extension as a header block. This is
accomplished by defining an element for the extension and adding a
***************
*** 2707,2711 ****
<div class="div4">
! <h5><a name="N1110D"></a>5.2.5.3 Additional Mandatory Elements in Content</h5>
<p> This following example demonstrates an extension with additional
content. The reservation service requires a number of guests parameter.
--- 2710,2714 ----
<div class="div4">
! <h5><a name="N11119"></a>5.2.5.3 Additional Mandatory Elements in Content</h5>
<p> This following example demonstrates an extension with additional
content. The reservation service requires a number of guests parameter.
***************
*** 2735,2739 ****
<div class="div4">
! <h5><a name="N11124"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5>
<p> Section <a href="#more-interfaces-inheritance"><b>2.4.2 Interface Inheritance</b></a> shows another type
of versioning or extension, where the reservationInterface extends the
--- 2738,2742 ----
<div class="div4">
! <h5><a name="N11130"></a>5.2.5.4 Additional Optional Operation Added to Interface</h5>
<p> Section <a href="#more-interfaces-inheritance"><b>2.4.2 Interface Inheritance</b></a> shows another type
of versioning or extension, where the reservationInterface extends the
***************
*** 2744,2748 ****
<div class="div4">
! <h5><a name="N11130"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5>
<p> Often mandatory operations are added to an interface. The Hotel service
decides to add an operation to the reservation service which is a
--- 2747,2751 ----
<div class="div4">
! <h5><a name="N1113C"></a>5.2.5.5 Additional Mandatory Operation Added to Interface</h5>
<p> Often mandatory operations are added to an interface. The Hotel service
decides to add an operation to the reservation service which is a
***************
*** 2787,2791 ****
<div class="div4">
! <h5><a name="N1114A"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5>
<p> To indicate incompatibility, the URI of the Hotel Endpoint can be
changed and messages send to the old Endpoint return a Fault.</p>
--- 2790,2794 ----
<div class="div4">
! <h5><a name="N11156"></a>5.2.5.6 Indicating Incompatibility by Changing the Endpoint URI</h5>
<p> To indicate incompatibility, the URI of the Hotel Endpoint can be
changed and messages send to the old Endpoint return a Fault.</p>
***************
*** 2793,2797 ****
<div class="div4">
! <h5><a name="N11153"></a>5.2.5.7 Indicating Incompatibility by Changing the SOAP Action</h5>
<p> The SOAP Action can be set for the makeReservation request, and making
it different than the earlier version should indicate incompatibility.</p>
--- 2796,2800 ----
<div class="div4">
! <h5><a name="N1115F"></a>5.2.5.7 Indicating Incompatibility by Changing the SOAP Action</h5>
<p> The SOAP Action can be set for the makeReservation request, and making
it different than the earlier version should indicate incompatibility.</p>
***************
*** 2814,2818 ****
<div class="div4">
! <h5><a name="N1116A"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5>
<p> The namespace or name of the makeReservation element can be changed, and
then the interface and bindings changed. To indicate incompatibility,
--- 2817,2821 ----
<div class="div4">
! <h5><a name="N11176"></a>5.2.5.8 Indicating Incompatibility by Changing the Element Content</h5>
<p> The namespace or name of the makeReservation element can be changed, and
then the interface and bindings changed. To indicate incompatibility,
***************
*** 3740,3744 ****
http://www.w3.org/TR/xmlschema-2.
</dd>
!
<dt class="label"><a name="RFC3023"></a>[RFC 3023]</dt><dd>IETF
"RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July
--- 3743,3747 ----
http://www.w3.org/TR/xmlschema-2.
</dd>
!
<dt class="label"><a name="RFC3023"></a>[RFC 3023]</dt><dd>IETF
"RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July
***************
*** 3953,3957 ****
--- 3956,3973 ----
<cite><a href="http://www.w3.org/XML/2005/xsd-versioning-use-cases/">XML Schema Versioning Use Cases</a></cite> , Hoylen Sue. W3C XML Schema Working Group Draft, 15 April 2005. Available at http://www.w3.org/XML/2005/xsd-versioning-use-cases/
</dd>
+ <dt class="label"><a name="xsd-versioning-guide"></a>[Guide to Versioning XML Languages using XML Schema 1.1]</dt><dd>
+ <cite><a href="http://www.w3.org/TR/xmlschema-guide2versioning">Guide to Versioning XML Languages using XML Schema 1.1</a></cite>, David Orchard. W3C XML Schema Working Group Draft, 28 September 2006. Available at http://www.w3.org/TR/xmlschema-guide2versioning
+ </dd>
+ <dt class="label"><a name="xsd11"></a>[XML Schema 1.1]</dt><dd>
+ <cite><a href="http://www.w3.org/TR/2006/WD-xmlschema11-1-20060831/">XML Schema 1.1 Part 1: Structures</a></cite>,
+ H. Thompson, C. M. Sperberg-McQueen, Shudi (Sandy) Gao, N. Mendelsohn,
+ David Beech, Murray Maloney, Editors. World Wide Web Consortium, 31 August 2006.
+ This Working Draft of XML Schema 1.1 Part 1 is
+ http://www.w3.org/TR/2006/WD-xmlschema11-1-20060831/. The <a href="http://www.w3.org/TR/xmlschema11-1/">latest version of
+ XML Schema 1.1 Part 1</a> is available at
+ http://www.w3.org/TR/xmlschema11-1/.
+ </dd>
+
<dt class="label"><a name="sw-vocabulary"></a>[SW VocabManagementNote]</dt><dd>
<cite><a href="http://esw.w3.org/topic/VocabManagementNote">Vocabulary Management</a></cite> , Thomas Baker, et al. Semantic Web Best Practices and Deployment Working Group Note, 8 Feb 2005. Available at
Received on Friday, 22 December 2006 19:13:34 UTC