File:  [Public] / 2007 / xml / sml / build / sml-if.html
Revision 1.60 1.61 : download - view: text , annotated - select for diffs
Mon Tue Dec 3 22:24:19 4 02:55:38 2007 UTC (16 years, 3 months ago) by vsmith
Branches: MAIN
CVS tags: HEAD
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4774

<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Service Modeling Language Interchange Format Version 1.1</title><style type="text/css">
code           { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }
ol.enumar      { list-style-type: decimal; }
ol.enumla      { list-style-type: lower-alpha; }
ol.enumlr      { list-style-type: lower-roman; }
ol.enumua      { list-style-type: upper-alpha; }
ol.enumur      { list-style-type: upper-roman; }
dt.label       { display: run-in; }
li, p           { margin-top: 0.3em;
                 margin-bottom: 0.8em; }
.diff-chg	{ background-color: yellow; }
.diff-del	{ background-color: red; text-decoration: line-through;}
.diff-add	{ background-color: lime; }
table          { empty-cells: show; }
table caption {
	font-weight: normal;
	font-style: italic;
	text-align: left;
	margin-bottom: .5em;
}
div.issue {
  color: red;
}
.rfc2119 {
  font-variant: small-caps;
}
.figure {
  text-align: center;
}
.center {
  text-align: center;
}
.left {
  text-align: left;
}
.red {
  color: red;
}
table.eg {
  color: #99ffff;
}
code.emph {
  font-style: italic;
}
div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
                    margin: 4px}
p.exampleHead { text-align: left;}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"></head><body><div class="head">
<h1><a name="title" id="title"></a>Service Modeling Language Interchange Format Version 1.1</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
            <a href="http://dev.w3.org/cvsweb/~checkout~/2007/xml/sml/build/sml-if.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2007/xml/sml/build/sml-if.html?content-type=text/html;%20charset=utf-8</a>
        </dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/sml-if/">http://www.w3.org/TR/sml-if/</a></dd><dt>Previous version:</dt><dd>
            <a href="http://www.w3.org/TR/2007/WD-sml-if-20070806/">http://www.w3.org/TR/2007/WD-sml-if-20070806/</a>
    </dd><dt>Editors:</dt><dd>James Lynn, HP</dd><dd>Bhalchandra Pandit, Microsoft Corporation</dd><dd>Valentina Popescu, IBM Corporation</dd><dd>Virginia Smith, HP</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>This specification defines the interchange format for
	  Service Modeling Language, Version 1.1 (SML) models. Markup is defined to identify the
	  model being interchanged, to distinguish between model
	  definition documents and model instance documents, and to bind
	  rule documents with other documents in the interchange set. </p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
        no official standing.</strong></p><p>Copyright holders will not be liable for any direct, indirect, special or consequential damages arising out of any use of the software or documentation.</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1. <a href="#Introduction">Introduction</a><br>
2. <a href="#Notations_and_Terminology">Notations and Terminology</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#Notational_Conventions">Notational Conventions</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#Terminology">Terminology</a><br>
3. <a href="#Dependencies">Dependencies on Other Specifications</a><br>
4. <a href="#Informal_Description">Informal Description</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#Packaging">Packaging</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#URI_References">URI References</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#Rule_Document_Bindings">Rule Document Bindings</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;4.4 <a href="#Schema_Document_Bindings">Schema Document Bindings</a><br>
5. <a href="#SML-IF_Normative_Definition">SML Interchange Format Definition (Normative)</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#ConformanceClause">Conformance Criteria</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#Concepts">SML-IF Documents</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#embedded_documents">Embedded Documents</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#document_references">Referenced Documents</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#URI_References2">URI References</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.1 <a href="#URI_equivalence">URI equivalence</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.2 <a href="#Document_aliases">Document aliases</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.3 <a href="#URI_Processing">URI Reference Processing</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#Rule_Document_Bindings1">Rule Document Bindings</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1 <a href="#URI_prefix_matching">URI prefix matching</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.2 <a href="#Bindings_defined">Bindings defined</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;5.5 <a href="#Schema_Document_Bindings1">Schema Document Bindings</a><br>
6. <a href="#References">References</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#Normative_References">Normative References</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#NonNormative_References">Non-Normative References</a><br>
</p>
<h3><a name="appendices" id="appendices"></a>Appendix</h3><p class="toc">A. <a href="#SML_IF_Schema">SML-IF Schema</a><br>
</p></div><hr><div class="body"><div class="div1">
<h2><a name="Introduction" id="Introduction"></a>1. Introduction</h2><p>As defined in the Service Modeling Language, Version 1.1 (SML) Specification [<cite><a href="#SML">SML 1.1</a></cite>]
an SML model is a collection of XML documents that may be used to
describe complex services and systems such as a set of IT resources, services and their
interrelations.</p><p>In every SML model there are two distinguished subsets of the model's documents,
 the definition documents and the instance documents. The model's definition documents 
 describe the abstract structure of the model, and
provide much of the information a model validator needs to decide
whether the model as a whole is valid. The model's instance documents describe or support the
description of the individual resources the model portrays.</p><p>The SML Specification identifies two categories of model definition
documents that participate in model validation: Schema documents and
rule documents. Schema documents in a model are XML documents that
conform to the [<cite><a href="#SML">SML 1.1</a></cite>] defined extensions to 
XML Schema [<cite><a href="#XSD1">XML Schema Structures</a></cite>, <cite><a href="#XSD2">XML Schema Datatypes</a></cite>].
Rule documents in a model include XML documents that conform to the 
[<cite><a href="#SML">SML 1.1</a></cite>] defined extensions of Schematron [<cite><a href="#Schematron">ISO/IEC 19757-3</a></cite>].</p><p>To ensure accurate and convenient interchange of the documents that
make up an SML model or a portion of an SML model, it is useful to
define an implementation-neutral interchange format that preserves the
content and interrelationships among the documents. This specification
defines a standard format called the SML Interchange Format (SML-IF)
for this purpose.</p><p>The specification consists of two parts. The first part is an
informal description of SML-IF to set the context. This is followed by SML-IF's normative definition.</p></div><div class="div1">
<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"></a>2. Notations and Terminology</h2><div class="div2">
<h3><a name="Notational_Conventions" id="Notational_Conventions"></a>2.1 Notational Conventions</h3><p>
	      The keywords "<span class="rfc2119">MUST</span>", "<span class="rfc2119">MUST
	      NOT</span>", "<span class="rfc2119">REQUIRED</span>",
	      "<span class="rfc2119">SHALL</span>", "<span class="rfc2119">SHALL
	      NOT</span>", "<span class="rfc2119">SHOULD</span>",
	      "<span class="rfc2119">SHOULD NOT</span>",
	      "<span class="rfc2119">RECOMMENDED</span>",
	      "<span class="rfc2119">MAY</span>", and
	      "<span class="rfc2119">OPTIONAL</span>" in this document are to be
	      interpreted as described in RFC 2119 [<cite><a href="#RFC2119">IETF RFC 2119</a></cite>].
	    </p></div><div class="div2">
<h3><a name="Terminology" id="Terminology"></a>2.2 Terminology</h3><dl><dt class="label"><a name="interchange_set" id="interchange_set"></a>Interchange set</dt><dd><p>The SML-IF interchange set is the set of 
documents that constitute the SML model to be interchanged.</p></dd><dt class="label"><a name="SML_defined" id="SML_defined"></a>Definition document, instance document, rule document</dt><dd><p>These terms are defined in the [<cite><a href="#SML">SML 1.1</a></cite>] specification.</p></dd></dl></div></div><div class="div1">
<h2><a name="Dependencies" id="Dependencies"></a>3. Dependencies on Other Specifications</h2><p>Other specifications on which this one depends are listed in [<cite><a href="#Normative_References">Normative_References</a></cite>].
</p><p>
Conforming implementations of this specification MUST support SML 1.1 [<cite><a href="#SML">SML 1.1</a></cite>],
XML 1.0 [<cite><a href="#XML10">XML</a></cite>] and 
XML Schema 1.0 [<cite><a href="#XSD1">XML Schema Structures</a></cite>, <cite><a href="#XSD2">XML Schema Datatypes</a></cite>].
Conforming implementations MAY additionally support later
versions of the XML or XML Schema specifications.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This note is non-normative.
Although <a href="http://www.w3.org/TR/sml/#Dependencies">SML 1.1</a> and SML-IF
allow conforming implementations to support
newer versions of dependent specifications, 
there are interoperability implications to be considered
when documents based on those versions are interchanged 
using SML-IF. When an SML-IF document interchanges data built using newer versions 
of the SML and SML-IF dependent specifications, consumers of the SML-IF 
document not supporting these versions may be unable to interpret 
some of the data exchanged by this document.
</p></div></div><div class="div1">
<h2><a name="Informal_Description" id="Informal_Description"></a>4. Informal Description</h2><p>To represent an SML model in a standard way for interchange, three
topics need to be addressed.</p><p>
<b>Packaging:</b> The collection of XML documents that make up a
model (or model portion) to be interchanged need to be gathered
together. In doing so, the model definition and model instance
documents need to be distinguished from one another since they play
distinct roles in the model.</p><p>
<b>Explicit references:</b> The documents to be
interchanged may explicitly refer to one another and to documents that
are not packaged with the documents being interchanged. SML [<cite><a href="#SML">SML 1.1</a></cite>] references 
among SML model instance documents are an obvious example. Less
obvious are such references as certain <code>xsi:schemaLocation</code>
attributes in schema documents.</p><p>
<b>Binding of rule documents to the documents to which they
apply:</b> [<cite><a href="#SML">SML 1.1</a></cite>] permits models in which rule documents apply to all,
none, or subsets of the model's documents. SML-IF specifies how to
describe which rule documents apply to which of the model's
documents.</p><div class="div2">
<h3><a name="Packaging" id="Packaging"></a>4.1 Packaging</h3><p>An SML-IF document packages a collection of SML documents to be
interchanged as a single XML document. All SML-IF documents conform to
the XML Schema defined in the normative part of this
specification.</p><p>Informally, the structure of SML-IF documents, using the
pseudoschema notation from WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] is as
follows:</p><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;model xmlns="http://www.w3.org/@@@@/@@/sml-if"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt;
 
   
     xs:anyURI Namespace identifying the model
   
    ?
     xs:token 
   
   displayName smlerr:localizationid=
                        "xs:anyURI URI identifying the translation
                       resource for the display name" ? ?
     xs:string Descriptive name of model intended for display
   
   description smlerr:localizationid=
                        "xs:anyURI URI identifying the translation
                       resource for the description" ? ?
     xs:string Textual description of model for human consumption
   
 
  ?
   *
     ?
    
  
 
  ?
    *
      ?
        ?
          *
           xs:anyURI A URI by which this document may be referred to
         
       
     
    [
     
       xs:any 
     
    |
     
        ?
       xs:any 
     
    ]
   
 
  ?
    *
      ?
        ?
          +
           xs:anyURI A URI by which this document may be referred to
         
       
     
    [
     
       xs:any
     
    |
     
        ?
       xs:any 
     
    ]
   
 

	&lt;identity&gt;
	  &lt;name&gt;
	    xs:anyURI Namespace identifying the model
	  &lt;/name&gt;	  &lt;version&gt; ?
	    xs:token &lt;!—The version of this model. E.g., 1.2 or 0.3&gt;
	  &lt;/version&gt;	  &lt;displayName smlerr:localizationid=
	                       "xs:anyURI URI identifying the translation
	                      resource for the display name" ?&gt; ?
	    xs:string Descriptive name of model intended for display
	  &lt;displayName/&gt;	  &lt;description smlerr:localizationid=
	                       "xs:anyURI URI identifying the translation
	                      resource for the description" ?&gt; ?
	    xs:string Textual description of model for human consumption
	  &lt;description/&gt;	&lt;/identity&gt;	&lt;ruleBindings&gt; ?	 &lt;ruleBinding&gt; *	   &lt;documentAlias="xs:anyURI"/&gt; ?	   &lt;ruleAlias="xs:anyURI"/&gt;	 &lt;/ruleBinding&gt;	&lt;/ruleBindings&gt;	&lt;schemaBindings&gt; ?	  &lt;defaultSchema&gt; ?	    &lt;namespaceBinding/&gt; *  	  &lt;/defaultSchema&gt;	  &lt;schemaBinding&gt; *	    &lt;namespaceBinding/&gt; *  	    &lt;documentAlias/&gt; *     	  &lt;/schemaBinding&gt;	&lt;/schemaBindings&gt;	&lt;definitions schemaComplete="xs:boolean"&gt; ?	  &lt;document&gt; *	    &lt;docInfo&gt; ?	      &lt;aliases&gt; ?	        &lt;alias&gt; *
	          xs:anyURI A URI by which this document may be referred to
	        &lt;/alias&gt;	      &lt;/aliases&gt;	    &lt;/docInfo&gt;
	   [
	    &lt;data&gt;
	      xs:any &lt;!—At most one definition document goes here&gt;
	    &lt;/data&gt;
	   |
	    &lt;locator&gt;	      &lt;documentURI/&gt; ?
	      xs:any &lt;!—A reference to a definition document goes here&gt;
	    &lt;/locator&gt;
	   ]
	  &lt;/document&gt;	&lt;/definitions&gt;	&lt;instances&gt; ?	  &lt;document&gt; *	    &lt;docInfo&gt; ?	      &lt;aliases&gt; ?	        &lt;alias&gt; +
	          xs:anyURI A URI by which this document may be referred to
	        &lt;/alias&gt;	      &lt;/aliases&gt;	    &lt;/docInfo&gt;
	   [
	    &lt;data&gt;
	      xs:any&lt;!—At most one instance document goes here&gt;
	    &lt;/data&gt;
	   |
	    &lt;locator&gt;	      &lt;documentURI/&gt; ?
	      xs:any &lt;!—A reference to an instance document goes here&gt;
	    &lt;/locator&gt;
	   ]
	  &lt;/document&gt;	&lt;/instances&gt;
&lt;/model&gt;
</pre></div><p>The <code>identity</code> element provides information applications
can use to identify and describe the set of SML documents being
interchanged.
</p><p>The optional <code>ruleBindings</code> element is used to contain
information that associates rule documents with the
documents they apply to. See <a href="#Rule_Document_Bindings"><b>4.3 Rule Document Bindings</b></a>
for further details.</p><p>The set of SML documents that are interchanged in an SML-IF
document is called the <em>interchange set</em>. Every document in the
interchange set appears as content of a <code>document</code> element
in either the <code>definitions</code> or the <code>instances</code>
element, depending on whether the document in question is a model
definition or a model instance document. There can be at most one 
embedded document contained by a <code>document/data</code> element. 
Both <code>definitions</code>
and <code>instances</code> are optional. So, for example, if there are
no model definition documents being packaged, the
<code>definitions</code> element must be omitted.</p><p>The first child of each <code>document</code> is typically a
<code>docInfo</code> element that (indirectly) contains a list of
<code>alias</code> elements whose content is a URI with no fragment
component (i.e., one with no "#" in it). Each of these URIs serves as
a name that other documents can use to refer to this
document. Examples of how aliases are used to handle certain URI-based
references are given in <a href="#URI_References"><b>4.2 URI References</b></a>.</p><p>A document in the interchange set can be represented in either of
two ways, by embedding its content, or by providing a reference to
it. Which is being used is indicated by the next child of the
<code>document</code> element. If the document is to be embedded, a
<code>data</code> element is used to contain the actual content of the
document. If the document is to be referred to, a <code>locator</code>
element is used to contain the reference. Syntactically, the content
of a <code>locator</code> can be a <code>documentURI</code> element
defined by SML-IF or anything else understood by the
consumer. Typically it is a URI, an XLink [<cite><a href="#XLink">XLink</a></cite>], or
a Web Services Addressing endpoint reference [<cite><a href="#WSADDR-CORE">WS-Addressing Core</a></cite>].</p><p>Although it is not fully shown in the pseudo-schema above, the
SML-IF schema has an "open content model." To provide extensibility,
essentially every element in it can contain additional content and/or
attributes from other XML namespaces.</p></div><div class="div2">
<h3><a name="URI_References" id="URI_References"></a>4.2 URI References</h3><p>
When processing the SML model packaged inside an SML-IF document,
certain URI references (as defined in RFC 3986 [<cite><a href="#RFC3986">IETF RFC 3986</a></cite>]) 
may need to be processed to find their corresponding target. 
For example, to assess SML validity of the interchanged model, 
SML references using the URI scheme need to be resolved; 
and to assemble a schema from multiple schema documents as part 
of SML model validity assessment, the schemaLocation attribute 
on an <code>xs:include</code> element needs to be processed 
to locate the schema document being included.
</p><p>To see how these URI references are handled, consider the
following SML-IF document:</p><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;model 
      xmlns="http://www.w3.org/@@@@/@@/sml-if" version="1.0"&gt;
 &lt;identity&gt;
   &lt;name&gt;http://www.university.example.org/sml/models/Sample/InterDocReferences&lt;/name&gt;
 &lt;/identity&gt;
 &lt;definitions&gt;
   &lt;document&gt;
     &lt;data&gt;
        &lt;xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt;
          &lt;xs:include schemaLocation="http://www.university.example.org/university/enrollmodel.xsd"/&gt;
        &lt;/xs:schema&gt;     
     &lt;/data&gt;      
   &lt;/document&gt;
 &lt;/definitions&gt;
 
 &lt;instances&gt;
   &lt;document&gt;
     &lt;data&gt;
       &lt;Student xmlns="http://www.university.example.org/ns"
       	xmlns:sml="http://www.w3.org/2007/09/sml"&gt;
         &lt;ID&gt;1000&lt;/ID&gt;
         &lt;Name&gt;John Doe&lt;/Name&gt;
         &lt;EnrolledCourses&gt;
           &lt;EnrolledCourse sml:ref="true"&gt;
&lt;!-- Reference to a course Inside the interchange set --&gt;                                     
             &lt;sml:uri&gt;
               http://www.university.example.org/Universities/MIT/Courses.xml#xmlns(u=http://www.university.example.org/ns)
               xpointer(/u:Courses/u:Course[u:Name='PHY101'])
             &lt;/sml:uri&gt;
           &lt;/EnrolledCourse&gt;
           &lt;EnrolledCourse sml:ref="true"&gt;
&lt;!-- Reference to a course OUTside the interchange set --&gt;                        
             &lt;sml:uri&gt;
               http://www.university.example.org/Universities/Capella/Courses.xml#xmlns(u=http://www.university.example.org/ns)
               xpointer(/u:Courses/u:Course[u:Name='LIT103'])
             &lt;/sml:uri&gt;
           &lt;/EnrolledCourse&gt;
         &lt;/EnrolledCourses&gt;
       &lt;/Student&gt;
      &lt;/data&gt;
   &lt;/document&gt;
   &lt;document&gt;
&lt;!-- One of the courses referenced above --&gt;
     &lt;docInfo&gt;
       &lt;aliases&gt;
         &lt;alias&gt;http://www.university.example.org/Universities/MIT/Courses.xml&lt;/alias&gt;
       &lt;/aliases&gt;
     &lt;/docInfo&gt;
     &lt;data&gt;
       &lt;Courses xmlns="http://www.university.example.org/ns"&gt;
         &lt;Course&gt;
           &lt;Name&gt;PHY101&lt;/Name&gt;
         &lt;/Course&gt;
         &lt;Course&gt;
           &lt;Name&gt;MAT200&lt;/Name&gt;
         &lt;/Course&gt;
       &lt;/Courses&gt;
     &lt;/data&gt;
   &lt;/document&gt;
 &lt;/instances&gt;
&lt;/model&gt;</pre></div><p>
Formal rules about how URI references are processed are defined
in section <a href="#URI_Processing"><b>5.3.3 URI Reference Processing</b></a>. When not packaged 
in an SML-IF document, certain URI references (e.g. values of <code>sml:uri</code> 
elements or certain <code>schemaLocation</code> attributes) are dereferenced to find 
their corresponding document. When these references are packaged in an SML-IF document, 
consumers of the SML-IF document need to first examine whether 
the target document or element is packaged in the same SML-IF document. 
To determine this, the fragment component, if any, is temporarily 
ignored to form a URI. This URI is then compared against 
<code>alias</code> URIs of packaged model documents.
</p><p>If the URI is equivalent to the URI in an
<code>alias</code> (see <a href="#URI_equivalence"><b>5.3.1 URI equivalence</b></a>), the consumer will not 
attempt to look for targets of this URI outside of the SML-IF document, 
although there may exist a document retrievable at this URI. If
the original reference has a fragment, the fragment is applied to the
referred-to document to establish the reference target(s) 
according to the corresponding reference scheme definition; 
otherwise the reference is to the root element of the referred-to
document.
</p><p>If the URI is not equivalent to the URI in any
<code>alias</code>, then the SML-IF document does not contain
the corresponding target of the original reference. The consumer 
may or may not attempt to look for targets outside of the SML-IF document,
depending on the nature of the reference.</p><p>Referring now to the example SML-IF document above. The
reference:</p><div class="exampleInner"><pre>http://www.university.example.org/Universities/MIT/Courses.xml#xmlns(u=http://www.university.example.org/ns)
xpointer(/u:Courses/u:Course[u:Name='PHY101'])</pre></div><p>, after removing the fragment, becomes</p><div class="exampleInner"><pre>http://www.university.example.org/Universities/MIT/Courses.xml</pre></div><p>, which is equivalent to the URI listed in the <code>alias</code>
accompanying the <code>Courses</code> document. So, by applying the
fragment in the reference to the <code>Courses</code> document, we
determine that the reference is to the <code>Course</code> element
whose <code>Name</code> element has "PHY101" as its content.</p><p>The fragment-free part of the reference:</p><div class="exampleInner"><pre>http://www.university.example.org/Universities/Capella/Courses.xml#xmlns(u=http://www.university.example.org/ns)
xpointer(/u:Courses/u:Course[u:Name='LIT103'])
</pre></div><p>is</p><div class="exampleInner"><pre>http://www.university.example.org/Universities/Capella/Courses.xml</pre></div><p>which is not equivalent to the URI in any <code>alias</code>. This means
that it is an unresolved SML reference.</p><p>The URI:</p><div class="exampleInner"><pre>http://www.university.example.org/university/enrollmodel.xsd 
</pre></div><p>(value of the <code>schemaLocation</code> attribute 
on the <code>include</code> element) is not equivalent to any <code>alias</code>.
The consumer may or may not attempt to locate a schema document using this URI reference.
</p></div><div class="div2">
<h3><a name="Rule_Document_Bindings" id="Rule_Document_Bindings"></a>4.3 Rule Document Bindings</h3><p>[<cite><a href="#SML">SML 1.1</a></cite>] uses Schematron patterns embedded in SML schemas and in
separate explicitly bound rule documents to express constraints that
cannot be expressed in XML Schemas. Schematron patterns embedded in
SML Schema documents all have well defined targets. [<cite><a href="#SML">SML 1.1</a></cite>] permits models
in which rule documents apply to all, none, or subsets of the model's
documents. SML-IF uses the list of <code>ruleBinding</code> elements
contained in the optional <code>ruleBindings</code> element to
associate rule documents with the documents in the interchange set to
which they apply. Each <code>ruleBinding</code> associates the
documents having an alias beginning with the URI prefix given in the
<code>documentAlias</code> with the rule documents having an alias
beginning with the prefix given in the <code>ruleAlias</code>. So, for
example, the <code>ruleBinding</code>:</p><div class="exampleInner"><pre>&lt;ruleBinding/&gt;
 &lt;documentAlias="http://www.university.example.org/sml/infrastructure/"/&gt;
 &lt;ruleAlias="http://www.university.example.org/sml/infrastructurerules/"/&gt;
&lt;/ruleBinding/&gt;</pre></div><p>Would associate documents that have the aliases such as:</p><div class="exampleInner"><pre>http://www.university.example.org/sml/infrastructure/server427.xml</pre></div><p>and</p><div class="exampleInner"><pre>http://www.university.example.org/sml/infrastructure/switch6E.xml</pre></div><p>with rule documents that have aliases such as:</p><div class="exampleInner"><pre>http://www.university.example.org/sml/infrastructurerules/assetistracked.sch</pre></div><p>and</p><div class="exampleInner"><pre>http://www.university.example.org/sml/infrastructurerules/managedbycorporate.sch</pre></div><p>SML-IF specifies rule bindings among documents in the interchange
set. It does not specify rule bindings that apply to documents not in
the interchange set. That said, it is often the case that the intent
of transferring an SML-IF document is to relate its contents with
other SML documents not in the interchange set. For example, the
intent might be to merge the interchange set with an existing SML
model. In such cases the context of use may choose to extend the
definition of <code>ruleBinding</code> to bind documents not in the
interchange set. For example, if the interchange set is merged into an
existing model, the merge process might choose to extend the
definition of <code>ruleBinding</code> elements to bind rule documents
in the interchange set to documents in the merged model that weren't
included in the interchange set.

included in the interchange set.</p></div><div class="div2">
<h3><a name="Schema_Document_Bindings" id="Schema_Document_Bindings"></a>4.4 Schema Document Bindings</h3><p>
Schema documents can be connected with other schema documents using composition 
features provided by XML Schema.  This includes <code>xs:include</code>, 
<code>xs:redefine</code>, and <code>xs:import</code>.  A schema document's 
validity may depend on other schema documents it includes/redefines/imports, or even 
other schema documents that include/redefine/import it.
In performing SML model validation over the SML model packaged in an SML-IF instance, 
associations between XML Schema definition documents and instance documents need to be 
drawn, both to completely validate XML Schema documents themselves and to establish the 
schema-validity of the instance documents.</p><p>The XML Schema 1.0 specification provides more flexibility in constructing the schema 
used for assessment than is appropriate for the semantics defined by SML and SML-IF 
validation.</p><ol class="enumar"><li><p>It allows processor latitude in terms of locating schema documents 
(resolving namespace and schema location attributes) and composing schema documents 
together to form a single schema.</p></li><li><p>Schema location attributes can be ignored in some cases
 (<code>xsi:schemaLocation</code> in instance documents and 
 <code>schemaLocation</code> attribute on <code>xs:import</code>) and 
 allowed to "fail to resolve" in others (<code>schemaLocation</code> 
 attribute on <code>xs:include</code> and <code>xs:import</code>). </p></li><li><p>Multiple imports of the same namespace allow all but the first 
one to be ignored.</p></li></ol><p>
So it is clear that SML-IF cannot guarantee general case interoperability 
based only on XML Schema given the constraints above and, therefore, needs to 
specify how to determine such associations. 
This proposal concerns only SML model validation and not SML-IF validation 
(against the IF schema). Unless otherwise indicated, "validation" or "validity" 
in the following sections refers to SML model validation. </p><p>
An SML-IF document can be:</p><ol class="enumar"><li><p>
                            <b>Schema-complete</b> - All schema documents are included in the 
SML-IF document, either as an
<a href="#embedded_documents"><b>5.2.1 Embedded Documents</b></a> or as <a href="#document_references"><b>5.2.2 Referenced Documents</b></a>.</p></li><li><p>                            <b>Schema-incomplete</b> - A required schema is not included in the SML-IF document, either as an embedded
document or a referenced document.</p></li></ol><p>It is necessary for an SML-IF producer to declaratively distinguish 
between these two cases and that is not always possible  
based on the content alone. SML-IF uses the <code>schemaComplete</code> 
attribute on the <code>definitions</code> element to indicate whether this 
SML-IF document includes all necessary schema definition documents. When 
this attribute is specified with a value of "true", then, for the 
instance to be valid, its schema definition documents and instance documents 
can only refer to either built-in components or components from definition 
documents included in the SML-IF instance.   Built-in components include:</p><ol class="enumar"><li><p>4 xsi: attributes (defined by XML Schema)</p></li><li><p>all schema built-in types (xs:anyType and simple types defined 
in XML Schema Part 2)</p></li><li><p>sml:ref attribute declaration</p></li><li><p>sml:uri element declaration</p></li></ol><p>An SML model represented by a schema-incomplete SML-IF document is not necessarily invalid.  However, SML-IF cannot guarantee interoperability for a schema-incomplete SML-IF document.</p><p>SML-IF uses a list of <code>schemaBinding</code> elements
contained in the optional <code>schemaBindings</code> element to
associate a namespace with a set of schema documents in the interchange set and 
the instance documents 
that should be validated against this set of schema documents.
 Each <code>namespaceBinding</code> child of a <code>schemaBinding</code> element 
 associates the
namespace specified in its <code>namespace</code> attribute 
with the schema documents whose alias specified in its <code>alias</code> attribute. 
In addition, 
the instance documents that are to be assessed against this set of schemas is specified 
in the <code>documentAlias</code>
child element of the same <code>schemaBinding</code> element.</p><p>
The following example illustrates schema bindings.</p><div class="exampleInner"><pre>    &lt;schemaBindings&gt;
      &lt;!-- Each "schemaBinding" element corresponds to a schema and model
           instance documents that are assessed against this schema --&gt;
      &lt;schemaBinding&gt;        &lt;!-- all "namespaceBinding" children together build the schema --&gt;        &lt;namespaceBinding namespace="ns1" aliases="xsd1-a xsd1-b"/&gt;        &lt;namespaceBinding namespace="ns2" aliases="xsd2-v1"/&gt;        &lt;!-- list all applicable instances; same as for rule bindings --&gt;        &lt;documentAlias&gt;doc1&lt;/documentAlias&gt;        &lt;documentAlias&gt;doc2-v1-a&lt;/documentAlias&gt;        &lt;documentAlias&gt;doc2-v1-b&lt;/documentAlias&gt;      &lt;/schemaBinding&gt;      &lt;schemaBinding&gt;        &lt;namespaceBinding namespace="ns1" aliases="xsd1-a xsd1-b"/&gt;        &lt;namespaceBinding namespace="ns2" aliases="xsd2-v2"/&gt;        &lt;documentAlias&gt;doc1&lt;/documentAlias&gt;        &lt;documentAlias&gt;doc2-v2&lt;/documentAlias&gt;      &lt;/schemaBinding&gt;    &lt;/schemaBindings&gt;    &lt;definitions schemaComplete="true"&gt;      &lt;!-- schema documents for xsd1-a, xsd1-b, xsd2-v1, xsd2-v2 --&gt;    &lt;/definitions&gt;</pre></div><p>
There are cases where many instance documents use the same schema. In this case, it is 
desirable to have a default schema binding rather than specifying a <code>schemaBinding</code> 
that lists all these instance documents.
The <code>defaultSchema</code> can be used cover instance documents that are not included in 
any other<code>schemaBinding</code> as in the following example.</p><div class="exampleInner"><pre>    &lt;schemaBindings&gt;
      &lt;!-- The "defaultSchema" element corresponds to a schema that governs
           all instance documents *not* included in any "schemaBinding". --&gt;
      &lt;defaultSchema&gt;        &lt;!-- all "namespaceBinding" children together build the schema --&gt;        &lt;namespaceBinding namespace="ns1" aliases="ns1.xsd"/&gt;        &lt;namespaceBinding namespace="ns2" aliases="ns2.xsd"/&gt;      &lt;/defaultSchema&gt;    &lt;/schemaBindings&gt;</pre></div></div></div><div class="div1">
<h2><a name="SML-IF_Normative_Definition" id="SML-IF_Normative_Definition"></a>5. SML Interchange Format Definition (Normative)</h2><p>This section normatively defines the Service Modeling Language
Interchange Format (SML-IF). It is not intended as
motivational or introductory material. For such material, please see
the non-normative informal description, above. Instead, this section
is intended to concisely define the requirements that SML-IF documents must
adhere to and to define how URI references contained in
them are to be interpreted by consumers of SML-IF documents.</p><div class="div2">
<h3><a name="ConformanceClause" id="ConformanceClause"></a>5.1 Conformance Criteria</h3><p> 
SML-IF defines two levels of conformance for SML-IF Documents: 
<ol class="enumar"><li><p>A <em>level 2 conforming SML-IF Document</em> <span class="rfc2119">MUST</span> adhere to all requirements
 in this specification as described in the normative sections. 
 In particular, all non-null SML references in the document <span class="rfc2119">MUST</span> contain
  a URI scheme representation  [<cite><a href="#SML">SML 1.1</a></cite>].
</p></li><li><p>A <em>level 1 conforming SML-IF Document</em> <span class="rfc2119">MUST</span> adhere to all requirements 
in this specification as described in the normative sections with the exception
 that a URI scheme representation [<cite><a href="#SML">SML 1.1</a></cite>] is not required for SML references. An SML-IF Document that 
 contains at least one non-null SML reference which has no URI scheme representation
 but satisfies all other SML-IF requirements is a level 1 conforming SML-IF Document.
</p></li></ol>
</p><p>A  <em>conforming SML-IF Producer</em> 
<span class="rfc2119">MUST</span> be able to generate a level 2 conforming SML-IF Document from an SML model.</p><p>A <em>conforming SML-IF Consumer</em> 
<span class="rfc2119">MUST</span> process a conforming SML-IF Document using, in whole or part, 
semantics defined by this specification. It is <span class="rfc2119">OPTIONAL</span> that a conforming SML-IF Consumer
 process all elements defined in this specification, but
any element that is processed <span class="rfc2119">MUST</span> be processed 
in a manner that is consistent with the semantics defined here. </p></div><div class="div2">
<h3><a name="Concepts" id="Concepts"></a>5.2 SML-IF Documents</h3><p>The purpose of SML-IF is to package the set of documents
that constitute an SML model into a standard format so that it can be exchanged 
in a standard way. 
</p><p>An SML-IF document <span class="rfc2119">MUST</span> conform to XML [<cite><a href="#XML10">XML</a></cite>] specification.</p><p>An SML-IF document <span class="rfc2119">MUST</span> be valid under the XML Schema given in Appendix A.</p><p>
An SML-IF document <span class="rfc2119">MAY</span> form a valid SML model 
but it is not required to do so. Various uses of SML-IF may define
requirements with respect to model validity and the interchange set,
but this specification does not. </p><p>Each document in the interchange set <span class="rfc2119">MUST</span> be represented in the SML-IF document by 
a separate <code>document</code> element as follows: </p><ol class="enumar"><li><p>Each definition document  
in the interchange set <span class="rfc2119">MUST</span> appear as a descendant
of a <code>model/definitions/document</code> element.
The order of the <code>document</code> children is not significant.</p></li><li><p>Each instance document in the interchange set
<span class="rfc2119">MUST</span> appear as a descendant of a <code>model/instances/document</code> 
element. The order of
the <code>document</code> children is not significant.</p></li></ol><p>Each document in the interchange set <span class="rfc2119">MUST</span> be included 
in the SML-IF document either as an embedded document (where the document to be
included is embedded in the SML-IF
document) or by including a reference to the document.</p><div class="div3">
<h4><a name="embedded_documents" id="embedded_documents"></a>5.2.1 Embedded Documents</h4><p>Documents that are to be embedded in the SML-IF document <span class="rfc2119">MUST</span> be 
embedded as follows:</p><ol class="enumar"><li><p>
Definition documents <span class="rfc2119">MUST</span> be embedded as the content of <code>model/definitions/document/data</code> 
element. There can be at most one definition document embedded in each 
<code>model/definitions/document/data</code> element.</p></li><li><p>Instance documents that do not contain a DTD <span class="rfc2119">MUST</span> be embedded 
as the content of a <code>model/instances/document/data</code> element. 
There can be at most one instance document embedded in each 
<code>model/instances/document/data</code> element.
</p></li><li><p>Instance documents that contain a DTD <span class="rfc2119">MUST</span> be embedded 
as follows:</p><ol class="enumla"><li><p>The document <span class="rfc2119">MUST</span> be encoded in base64 format.</p></li><li><p>The resultant data stream <span class="rfc2119">MUST</span> be embedded as the 
content of a <code>model/instances/document/base64Data</code> element. There can be at most one 
instance document embedded in each <code>model/instances/document/base64Data</code> element.</p></li></ol></li></ol><p>When extracting an embedded document that is contained in a <code>base64Data</code> element, 
an SML-IF consumer <span class="rfc2119">MUST</span> decode the content of the <code>base64Data</code> element
 first and then process the resulting document as a embedded instance document. 
All  embedded instance documents not encoded in base64 <span class="rfc2119">MUST</span> be processed as if they contained 
the same DTD as the one specified on the model element (if present). </p></div><div class="div3">
<h4><a name="document_references" id="document_references"></a>5.2.2 Referenced Documents</h4><p>Documents that are to be referenced rather than embedded <span class="rfc2119">MUST</span> be included as follows:</p><ol class="enumar"><li><p>If the document is a definition document, 
the location of the document <span class="rfc2119">MUST</span> be included as the content of a 
<code>model/definitions/document/locator</code> element.</p></li><li><p>
If the document is an instance document, 
the location of the document <span class="rfc2119">MUST</span> be included as the content of a 
<code>model/instances/document/locator</code> element.
</p></li></ol><p>SML-IF specifies one way
that <span class="rfc2119">MAY</span> be used to provide the location of the 
referenced document, the <code>documentURI</code> element.</p><p>An SML-IF 
consumer <span class="rfc2119">MAY</span> choose to locate a referenced document.
If an SML-IF consumer chooses not to locate a referenced document or if it attempts to
locate the referenced document and this attempt fails, then the SML-IF consumer 
<span class="rfc2119">MUST</span> treat the referenced document as if it is not part of the 
<a title="" href="#interchange_set">interchange set</a>.
If either of these conditions occurs, the SML-IF consumer
<span class="rfc2119">SHOULD</span> make its invoker aware of this condition. </p></div></div><div class="div2">
<h3><a name="URI_References2" id="URI_References2"></a>5.3 URI References</h3><div class="div3">
<h4><a name="URI_equivalence" id="URI_equivalence"></a>5.3.1 URI equivalence</h4><p>SML-IF uses URI equivalence extensively to handle references among
documents in the interchange set. To determine whether two URIs are
equivalent, consumers <span class="rfc2119">MUST</span> perform case sensitive 
codepoint-by-codepoint comparison of the corresponding 
characters in the URI references.
</p></div><div class="div3">
<h4><a name="Document_aliases" id="Document_aliases"></a>5.3.2 Document aliases</h4><p>In addition to containing or referring to one of the documents in
the interchange set, each <code>document</code> element may
(indirectly) contain a list of <code>alias</code> elements. Each
<code>alias</code> contains a URI. The set of alias URIs for a given
document constitutes the set of identifiers by which documents in the
interchange set may have references to the document in question.</p><p>A <code>document</code> element containing no <code>alias</code>
elements signals that the document in question has no aliases.</p><p>Each member of the set of all alias URIs in an SML-IF document 
<span class="rfc2119">MUST</span> be unique. That is, no two alias URIs in a given 
SML-IF document may be equivalent.</p><p>
Alias URIs <span class="rfc2119">MUST</span> comply with the “absolute-URI” production as 
defined in RFC 3986 ([<cite><a href="#RFC3986">IETF RFC 3986</a></cite>]). This implies that they 
do not contain fragment components.
</p><p>
All <code>alias</code> URIs in an SML-IF document <span class="rfc2119">MUST</span> be unique.
</p></div><div class="div3">
<h4><a name="URI_Processing" id="URI_Processing"></a>5.3.3 URI Reference Processing</h4><p>
When processing an SML-IF document, there are 3 categories
of URI references that may need to be resolved:
</p><ol class="enumar"><li><p>
<code>schemaLocation</code> attributes on <code>xs:include</code>
and <code>xs:redefine</code> in schema documents, when they are model definition documents.
</p></li><li><p>Certain URI references used in SML reference schemes. 
For a URI reference to be in this category, its non-fragment 
URI components have all the information to uniquely identify 
at most one model document that potentially contains the 
target(s) of the URI reference.
</p></li><li><p>URI references used in SML reference schemes which are not in category #2. </p></li></ol><p>
It is clear which references fall into category #1. 
An example of category #2 is URI references used in SML references 
that use the SML URI reference scheme. An example of category #3 
is URI references used in SML references that use the SML EPR reference scheme.
This is a consequence of how the respective schemes are defined. 
Similarly, when new references schemes that use URI references are defined,
whether they fall into category #2 or #3 will be clear from the reference
scheme definitions. Resolution of URI references in category #3 is defined
in their respective scheme definitions. It is also possible to have 
reference schemes that do not use URI references. Again, their resolution 
is governed by their scheme definitions and is not covered by this section.
</p><p>
To process a URI reference <b>UR</b> that is within categories
#1 or #2 above, the following steps are performed:
</p><ol class="enumar"><li><p>Determine the document <b>D</b> that possibly contains the target:</p><ol class="enumla"><li><p>If <b>UR</b> contains only a fragment component, 
        then <b>D</b> is the model document that contains <b>UR</b>. </p></li><li><p>Otherwise</p><ol class="enumlr"><li><p>If <b>UR</b> has a fragment component,
	      then let <b>UR'</b> be the URI referenced formed 
	      by removing the fragment component; otherwise let <b>UR'</b> be <b>UR</b>.</p></li><li><p>If <b>UR'</b> is a relative reference, 
	      then let <b>B</b> be the [base URI] ([<cite><a href="#XMLInfoset">XML Information Set</a></cite>]) property of the element
	       information item containing <b>UR</b>, and transform 
	       <b>UR'</b> to form an (absolute) URI <b>U</b>, 
	       using <b>B</b> as the base URI, as defined in section
	        “5 Reference Resolution” of RFC 3986 ([<cite><a href="#RFC3986">IETF RFC 3986</a></cite>]); 
	        otherwise let <b>U</b> be <b>UR'</b>. 
	      </p></li><li><p>If there exists a model document with an alias URI that
	       is equivalent to <b>U</b> (<a href="#URI_equivalence"><b>5.3.1 URI equivalence</b></a>), then 
	       <b>D</b> is that document; otherwise <b>D</b> has no value. 
	      </p></li></ol></li></ol></li><li><p>If <b>D</b> has no value, then</p><ol class="enumla"><li><p>If <b>UR</b> is within category #1 (<code>schemaLocation</code>), 
      then the SML-IF document does not contain the target schema document. 
      (Whether the consumer continues to dereference <b>UR</b> or <b>U</b>
      is governed by other sections of this specification.) </p></li><li><p>Otherwise (<b>R</b> is within category #2, used in an SML reference)
      <b>UR</b> has no target.</p></li></ol></li><li><p>If <b>D</b> is a schema document that is also
a model definition document in the interchange set, then </p><ol class="enumla"><li><p>If <b>UR</b> is within category #1 (<code>schemaLocation</code>), 
      and it does not contain a fragment component, 
      then <b>UR</b> targets the root element of <b>D</b>. </p></li><li><p>Otherwise (<b>UR</b> contains a fragment component or 
      is within category #2) <b>UR</b> has no target. </p></li></ol></li><li><p>If <b>D</b> is a model instance document in the interchange set, then</p><ol class="enumla"><li><p>If <b>UR</b> is within category #1 (<code>schemaLocation</code>), then it has no target.</p></li><li><p>If <b>UR</b> does not contain a fragment component, 
      then it targets the root element of <b>D</b>.</p></li><li><p>Otherwise (<b>UR</b> is within category #2 
      and contains a fragment component) the fragment component of 
      <b>UR</b> is applied to the root element of <b>D</b>,
      which may result in 0, 1, or many target elements.</p></li></ol></li><li><p>Otherwise (<b>D</b> is another kind of document
in the interchange set) <b>UR</b> has no target.</p></li></ol></div></div><div class="div2">
<h3><a name="Rule_Document_Bindings1" id="Rule_Document_Bindings1"></a>5.4 Rule Document Bindings</h3><div class="div3">
<h4><a name="URI_prefix_matching" id="URI_prefix_matching"></a>5.4.1 URI prefix matching</h4><p>To associate SML rule documents with the subset of documents in the
model to which they apply, SML-IF uses a combination of the alias
mechanism described above [<a href="#Document_aliases"><b>5.3.2 Document aliases</b></a>] 
and URI prefix matching.</p><p>Two URIs, one called the <em>prefix</em>, and one called the
<em>target</em> participate in URI prefix matching. The target is
said to match the prefix if and only if the target, truncated to the length of
the prefix, is equivalent to the prefix as defined in section <a href="#URI_equivalence"><b>5.3.1 URI equivalence</b></a>.</p></div><div class="div3">
 is an association of a set of one or more

<h4><a name="Bindings_defined" id="Bindings_defined"></a>5.4.2 Bindings defined</h4><p>A <em>rule binding</em> is an association of a set of one or more
rule documents with a set of zero or more model documents. The
documents associated with a given rule document are said to be "bound"
to it. For a model to be valid, every document in the model must
conform to the constraints defined by every rule document it is bound
to. It is permissible for a rule document to have no bindings
associated with it, and for a model document to be bound to zero rule
documents.</p><p>The <code>ruleBinding</code> element is used in SML-IF to express
bindings. In any given binding the set of rule documents is that

rule bindings. In any given binding the set of rule documents is that

subset of rule documents in the interchange set with an alias that
matches the URI prefix given by the content of the
<code>ruleAlias</code> element. The set of model documents in the
binding is that subset of the documents in the interchange set with an
alias that matches the URI prefix given by the content of the
<code>documentAlias</code> element. If the <code>documentAlias</code>
element is omitted in a <code>ruleBinding</code>, the set of model
documents in the binding is all documents in the interchange set.</p><p>Although SML-IF itself does not do so, various uses of SML-IF <span class="rfc2119">MAY</span>
 choose to extend the sets of documents involved in bindings to
include documents not contained in the interchange set. For example,
if an SML-IF document is used to represent a model fragment that is
intended to be merged with some other model, it is entirely possible
that some or all of the bindings may involve not just the documents in
the interchange set, but documents in the other model.

the interchange set, but documents in the other model.</p></div></div><div class="div2">
<h3><a name="Schema_Document_Bindings1" id="Schema_Document_Bindings1"></a>5.5 Schema Document Bindings</h3><p>For every schema binding <b>SB</b> in the model, i.e. every <code>/model/schemaBindings/schemaBinding</code> 
element, SML-IF consumers <span class="rfc2119">MUST</span> perform the following steps 
for instance document validation.</p><ol class="enumar"><li><p>Compose a schema using all documents specified under all 
<b>SB</b>'s <code>namespaceBinding</code> children.</p></li><li><p>Whenever an <code>import</code> for a namespace <b>N</b> is encountered, perform the following steps.<ol class="enumla"><li><p>If there is a <code>namespaceBinding</code> child of <b>SB</b> whose <code>namespace</code> attribute matches <b>N</b>, then components from schema documents listed in the 
corresponding <code>aliases</code> attribute are used.  As with rule bindings, 
URI prefixing [<a href="#URI_prefix_matching"><b>5.4.1 URI prefix matching</b></a>]
is used for matching schema document aliases.
At most one <code>namespaceBinding</code> is allowed per namespace <b>N</b> within 
a given <b>SB</b>.  If more than one namespace binding exists for the namespace as part of 
a single schema binding, the SML-IF document is in error.
If the set of aliases for namespace <b>N</b> is empty, the namespace has no schema 
documents defining it in the schema binding.</p></li><li><p>Otherwise, if there are schema documents in the SML-IF document whose targetNamespace 
is <b>N</b>, then components from all those schema documents are used.</p></li><li><p>Otherwise, if this is a schema-complete SML-IF document 
(<code>/model/definitions/@schemaComplete</code> = "true"), then no component from <b>N</b> (other than built-ins) is included in 
the schema being composed.</p></li><li><p>Otherwise, it is implementation-defined whether an SML-IF consumer 
tries to retrieve components for <b>N</b> from outside the SML-IF document.</p></li></ol>
                        </p></li><li><p>Whenever an <code>include</code> or <code>redefine</code> is encountered, 
the <code>schemaLocation</code> is used to match aliases of schema documents, as with base SML-IF.
<ol class="enumla"><li><p>If there is a schema document in the SML-IF document matching that alias, then 
that document is used.</p></li><li><p>Otherwise, if this is a schema-complete SML-IF document, then the <code>include</code> or 
<code>redefine</code> is unresolved (which is allowed by XML Schema 
validity assessment rules).</p></li><li><p>Otherwise, it is implementation-defined whether an SML-IF consumer tries to resolve 
<code>include</code> or <code>redefine</code> to schema documents outside the SML-IF document.</p></li></ol>                        </p></li><li><p>The instance documents that are referenced in the <code>documentAlias</code> 
element of <b>SB</b>
                            <span class="rfc2119">MUST</span> be validated 
against the schema constructed in steps 1 through 3. <code>sml:target*</code> and SML identity constraints can now be checked. 
Similar to <code>documentAlias</code> under <code>ruleBinding</code> elements [<a href="#Rule_Document_Bindings1"><b>5.4 Rule Document Bindings</b></a>], each 
<code>documentAlias</code> can refer to multiple documents via URI prefixing.</p></li></ol><p>If <code>defaultSchema</code> is present, then an SML-IF consumer <span class="rfc2119">MUST</span>
 compose a default schema from this element  
following rules 1 to 3 above. Otherwise, an SML-IF consumers <span class="rfc2119">MUST</span>
 compose a default schema using *all* schema documents 
included in the SML-IF document. An SML-IF consumer <span class="rfc2119">MUST</span> 
use this default schema to validate those SML instance documents that are not 
included in any <code>schemaBinding</code>.</p><p>The common use case where match-all namespace matching is desired 
can be achieved by omitting <code>schemaBindings</code>, i.e. without introducing any additional 
complexity into the SML-IF document.</p></div></div><div class="div1">

<h2><a name="References" id="References"></a>6. References</h2><div class="div2">
<h3><a name="Normative_References" id="Normative_References"></a>6.1 Normative References</h3><dl><dt class="label"><a name="SML"></a>[SML 1.1] </dt><dd>
  <cite><a href="http://www.w3.org/TR/@@@@/WD-sml-@@@@@@@@/">Service Modeling Language, Version 1.1</a></cite>,James Lynn,Bhalchandra Pandit,
Valentina Popescu, Virginia Smith, Editors.  World Wide Web Consortium, @@ @@@@ @@@@. This
   version of the Service Modeling Language specification is available
   at http://www.w3.org/TR/@@@@/WD-sml-@@@@@@@@/. The
   <a href="http://www.w3.org/TR/sml">latest version of Service Modeling Language, Version 1.1</a> is available at
   http://www.w3.org/TR/sml
</dd><dt class="label"><a name="XSD1"></a>[XML Schema Structures] </dt><dd>
   <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures Second
   Edition</a></cite>, H. Thompson, D. Beech, M. Maloney, and
   N. Mendelsohn, Editors. World Wide Web Consortium, 2 May
   2001, revised 28 October 2004. This version of the XML
   Schema Part 1 Recommendation is
   http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The
   <a href="http://www.w3.org/TR/xmlschema-1/">latest
   version of XML Schema Part 1</a> is available at
   http://www.w3.org/TR/xmlschema-1.
 </dd><dt class="label"><a name="XSD2"></a>[XML Schema Datatypes] </dt><dd>
   <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes Second
   Edition</a></cite>, P. Byron and A. Malhotra,
   Editors. World Wide Web Consortium, 2 May 2001, revised 28
   October 2004. This version of the XML Schema Part 2
   Recommendation is
   http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The
   <a href="http://www.w3.org/TR/xmlschema-2/">latest
   version of XML Schema Part 2</a> is available at
   http://www.w3.org/TR/xmlschema-2.
 </dd><dt class="label"><a name="XML10"></a>[XML] </dt><dd>
   <cite><a href="http://www.w3.org/TR/2006/REC-xml-20060816">Extensible Markup Language (XML) 1.0 (Fourth
   Edition)</a></cite>, T.  Bray, J. Paoli,
   C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide
   Web Consortium, 10 February 1998, revised 16 August 2006. This version of the XML
   1.0 Recommendation is
   http://www.w3.org/TR/2006/REC-xml-20060816. The <a href="http://www.w3.org/TR/REC-xml/">latest version of XML
   1.0</a> is available at http://www.w3.org/TR/REC-xml.
 </dd><dt class="label"><a name="XMLInfoset"></a>[XML Information Set] </dt><dd>
   <cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">XML Information Set</a></cite>, John Cowan and Richard Tobin, Editors.
   World Wide Web Consortium, 4 February 2004.
   This version of the XML Infoset
   Recommendation is http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.
   The <a href="http://www.w3.org/TR/xml-infoset/">
   latest version of the XML Infoset</a> is available at http://www.w3.org/TR/xml-infoset/.
 </dd><dt class="label"><a name="RFC3986"></a>[IETF RFC 3986] </dt><dd>
  <cite><a href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a></cite>, 
  T. Berners-Lee, R. Fielding, L. Masinter Authors. Internet
  Engineering Task Force, January 2005. Available at
  http://www.ietf.org/rfc/3986.txt.
</dd><dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
  <cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate
  Requirement Levels</a></cite>, S. Bradner, Author. Internet
  Engineering Task Force, June 1999. Available at
  http://www.ietf.org/rfc/rfc2119.txt.
</dd></dl></div><div class="div2">
<h3><a name="NonNormative_References" id="NonNormative_References"></a>6.2 Non-Normative References</h3><dl><dt class="label"><a name="Schematron"></a>[ISO/IEC 19757-3] </dt><dd>
  <cite><a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/c040833_ISO_IEC_19757-3_2006(E).zip">Information technology ― Document Schema
  Definition Languages (DSDL) ― Part 3: Rule-based
  validation ― Schematron</a></cite>. International
  Organization for Standardization and International
  Electrotechnical Commission, 1 January 2006. Available at
  http://standards.iso.org/ittf/PubliclyAvailableStandards/c040833_ISO_IEC_19757-3_2006(E).zip
</dd><dt class="label"><a name="Canonical"></a>[Canonical XML] </dt><dd>
   <cite><a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">Canonical XML</a></cite>, J. Boyer, Author. World Wide
   Web Consortium, 15 March 2001. This version of the Canonical XML
   Recommendation is
   http://www.w3.org/TR/2001/REC-xml-c14n-20010315. The <a href="http://www.w3.org/TR/xml-c14n">latest version of Canonical
   XML</a> is available at http://www.w3.org/TR/xml-c14n.
</dd><dt class="label"><a name="XML-Signature"></a>[XML-Signature] </dt><dd>
  <cite><a href="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/">XML-Signature Syntax and Processing</a></cite>,
  D. Eastlake, J. Reagle, and D. Solo, Editors. Internet
  Engineering Task Force &amp; World Wide Web Consortium, 12
  February 2002. This version of the XML-Signature Syntax
  and Processing Recommendation is
  http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/. The
  <a href="http://www.w3.org/TR/xmldsig-core/">latest
  version of XML-Signature Syntax and Processing</a> is
  available at http://www.w3.org/TR/xmldsig-core/.
</dd><dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
  <cite><a href="http://www.w3.org/TR/2006/REC-ws-addr-core-20060509">Web Services Addressing 1.0 - Core</a></cite>,
  M. Gudgin, M. Hadley, and T. Rogers, Editors. World Wide
  Web Consortium, 9 May 2006. This version of the
  WS-Addressing Core Recommendation is
  http://www.w3.org/TR/2006/REC-ws-addr-core-20060509. The
  <a href="http://www.w3.org/TR/ws-addr-core">latest
  version of WS-Addressing Core</a> is available at
  http://www.w3.org/TR/ws-addr-core.
</dd><dt class="label"><a name="WSDL20"></a>[WSDL 2.0 Core Language] </dt><dd>
  <cite><a href="http://www.w3.org/TR/2007/PR-wsdl20-20070523">Web Services Description Language (WSDL) Version
  2.0 Part 1: Core Language</a></cite>, R. Chinnici,
  M. Gudgin, J-J. Moreau, S. Weerawarana, Editors. World
  Wide Web Consortium, 23 May 2007. This version of the "Web
  Services Description Language (WSDL) Version 2.0 Part 1:
  Core Language" Specification is available is available at
  http://www.w3.org/TR/2007/PR-wsdl20-20070523. The <a href="http://www.w3.org/TR/wsdl20">latest version of "Web
  Services Description Language (WSDL) Version 2.0 Part 1:
  Core Language"</a> is available at
  http://www.w3.org/TR/wsdl20.
</dd><dt class="label"><a name="XLink"></a>[XLink] </dt><dd>
   <cite><a href="http://www.w3.org/TR/2001/REC-xlink-20010627/">XML Linking Language (XLink) Version 1.0</a></cite>, Steve DeRose, Eve Maler,
   David Orchard, Editors. World Wide Web
   Consortium, 27 June 2001.  This version of the XLink
   Recommendation is
   http://www.w3.org/TR/2001/REC-xlink-20010627/ The
   <a href="http://www.w3.org/TR/xlink/">latest
   version of XLink</a> is available at
   http://www.w3.org/TR/xlink/.
</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="SML_IF_Schema" id="SML_IF_Schema"></a>A. SML-IF Schema</h2><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;!--
/*
 * Copyright © @@@@ World Wide Web Consortium,
 *
 * (Massachusetts Institute of Technology, European Research Consortium for
 * Informatics and Mathematics, Keio University). All Rights Reserved. This
 * work is distributed under the W3C® Document License [1] in the hope that
 * it will be useful, but WITHOUT ANY WARRANTY; without even the implied
 * warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 *
 * [1] http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231
 */
--&gt;
&lt;xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:smlif="http://www.w3.org/@@@@/@@/sml-if" xmlns:ns1="http://www.w3.org/@@@@/@@/sml-if" targetNamespace="http://www.w3.org/@@@@/@@/sml-if" elementFormDefault="qualified" blockDefault="#all" version="1.0" xml:lang="EN" finalDefault="" attributeFormDefault="unqualified"&gt;
  &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/&gt;
  &lt;xs:element name="model" type="smlif:modelType"/&gt;
  &lt;xs:complexType name="modelType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element name="identity" type="smlif:identityType"/&gt;
      &lt;xs:element ref="smlif:ruleBindings" minOccurs="0"/&gt;
      &lt;xs:element ref="smlif:schemaBindings" minOccurs="0"/&gt;
      &lt;xs:element name="definitions" type="smlif:documentCollectionType" minOccurs="0"/&gt;
      &lt;xs:element name="instances" type="smlif:documentCollectionType" minOccurs="0"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  
   &lt;!-- If there is a need for localized string values, e.g. in displayName
       or description, the smlerr:localizationid global attribute can be
       used --&gt;
   
  &lt;xs:complexType name="identityType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element name="name" type="smlif:uriType"/&gt;
      &lt;xs:element name="version" type="smlif:tokenType" minOccurs="0"/&gt;
      &lt;xs:element name="displayName" type="smlif:displayType" minOccurs="0"/&gt;
      &lt;xs:element name="description" type="smlif:displayType" minOccurs="0"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:complexType name="displayType" mixed="false"&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base="xs:string"&gt;
        &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:complexType name="tokenType" mixed="false"&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base="xs:token"&gt;
        &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:complexType name="uriType" mixed="false"&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base="xs:anyURI"&gt;
        &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="ruleBindings" type="smlif:ruleBindingCollectionType"/&gt;
  &lt;xs:complexType name="ruleBindingCollectionType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="smlif:ruleBinding" maxOccurs="unbounded"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="ruleBinding" type="smlif:ruleBindingType"/&gt;
  &lt;xs:complexType name="ruleBindingType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element name="documentAlias" type="smlif:uriType" minOccurs="0"/&gt;
      &lt;xs:element name="ruleAlias" type="smlif:uriType"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="schemaBindings"/&gt;
  &lt;xs:complexType name="schemaBindingCollectionType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="smlif:defaultSchema" minOccurs="0"/&gt;
      &lt;xs:element ref="smlif:schemaBinding" minOccurs="0" maxOccurs="unbounded"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="schemaBinding" type="smlif:schemaBindingType"/&gt;
  &lt;xs:complexType name="schemaBindingType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="ns1:namespaceBinding"/&gt;
      &lt;xs:element name="documentAlias" type="smlif:uriType" maxOccurs="unbounded"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="namespaceBinding" type="ns1:namespaceBindingType"/&gt;
  &lt;xs:complexType name="namespaceBindingType" mixed="false"&gt;
    &lt;xs:attribute name="namespace" type="xs:NCName" use="required"/&gt;
    &lt;xs:attribute name="alias" use="required"&gt;
      &lt;xs:simpleType&gt;
        &lt;xs:list itemType="xs:anyURI"/&gt;
      &lt;/xs:simpleType&gt;
    &lt;/xs:attribute&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="defaultSchema"/&gt;
  &lt;xs:complexType name="defaultSchemaType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="smlif:namespaceBinding"/&gt;
    &lt;/xs:sequence&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:complexType name="documentCollectionType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="smlif:document" maxOccurs="unbounded"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:attribute name="schemaComplete" type="xs:boolean"/&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="document" type="smlif:documentType"/&gt;
  &lt;xs:complexType name="documentType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="smlif:docinfo" minOccurs="0"/&gt;
      &lt;xs:choice&gt;
        &lt;xs:element name="data" type="smlif:dataType"/&gt;
        &lt;xs:element name="locator" type="smlif:locatorType"/&gt;
      &lt;/xs:choice&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="docinfo" type="smlif:docinfoType"/&gt;
  &lt;xs:complexType name="docinfoType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element ref="smlif:aliases" minOccurs="0"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:element name="aliases" type="smlif:aliasCollectionType"/&gt;
  &lt;xs:complexType name="aliasCollectionType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element name="alias" type="smlif:uriType" maxOccurs="unbounded"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:complexType name="dataType" mixed="false"&gt;
    &lt;xs:annotation&gt;
      &lt;xs:documentation&gt;
The wildcard with processContents "skip" matches the root element of the  
model document being packaged. The value of processContents is set to "skip" so
that the contained element is not processed for schema validation. As a result,
validity of the packaged document will not affect validity of the IF document
itself.
      &lt;/xs:documentation&gt;
        

    &lt;/xs:annotation&gt;
    &lt;xs:sequence&gt;
      &lt;xs:any processContents="skip" minOccurs="0" namespace="##any" maxOccurs="1"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
  &lt;xs:complexType name="locatorType" mixed="false"&gt;
    &lt;xs:sequence&gt;
      &lt;xs:element name="documentURI" type="smlif:uriType" minOccurs="0"/&gt;
      &lt;xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:anyAttribute namespace="##other" processContents="lax"/&gt;
  &lt;/xs:complexType&gt;
&lt;/xs:schema&gt;


</pre>




</div>




</div>




</div>




</body>




</html>



Webmaster