The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
The schema for OASIS ebXML Registry Information Model
<div xmlns="http://www.w3.org/1999/xhtml">
<h1>About the XML namespace</h1>
<div class="bodytext">
<p>
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
</p>
<p>
See <a href="http://www.w3.org/XML/1998/namespace.html">
http://www.w3.org/XML/1998/namespace.html</a> and
<a href="http://www.w3.org/TR/REC-xml">
http://www.w3.org/TR/REC-xml</a> for information
about this namespace.
</p>
<p>
Note that local names in this namespace are intended to be
defined only by the World Wide Web Consortium or its subgroups.
The names currently defined in this namespace are listed below.
They should not be used with conflicting semantics by any Working
Group, specification, or document instance.
</p>
<p>
See further below in this document for more information about <a href="#usage">how to refer to this schema document from your own
XSD schema documents</a> and about <a href="#nsversioning">the
namespace-versioning policy governing this schema document</a>.
</p>
</div>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>Father (in any context at all)</h3>
<div class="bodytext">
<p>
denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
</p>
<blockquote>
<p>
In appreciation for his vision, leadership and
dedication the W3C XML Plenary on this 10th day of
February, 2000, reserves for Jon Bosak in perpetuity
the XML name "xml:Father".
</p>
</blockquote>
</div>
</div>
<div id="usage" xml:id="usage" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="usage">About this schema document</a>
</h2>
<div class="bodytext">
<p>
This schema defines attributes and an attribute group suitable
for use by schemas wishing to allow <code>xml:base</code>,
<code>xml:lang</code>, <code>xml:space</code> or
<code>xml:id</code> attributes on elements they define.
</p>
<p>
To enable this, such a schema must import this schema for
the XML namespace, e.g. as follows:
</p>
<pre>
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
</pre>
<p>
or
</p>
<pre>
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
</pre>
<p>
Subsequently, qualified reference to any of the attributes or the
group defined below will have the desired effect, e.g.
</p>
<pre>
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
</pre>
<p>
will define a type which will schema-validate an instance element
with any of those attributes.
</p>
</div>
</div>
<div id="nsversioning" xml:id="nsversioning" xmlns="http://www.w3.org/1999/xhtml">
<h2>
<a name="nsversioning">Versioning policy for this schema document</a>
</h2>
<div class="bodytext">
<p>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>.
</p>
<p>
At the date of issue it can also be found at
<a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd</a>.
</p>
<p>
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML
Schema itself, or with the XML namespace itself. In other words,
if the XML Schema or XML namespaces change, the version of this
document at <a href="http://www.w3.org/2001/xml.xsd">
http://www.w3.org/2001/xml.xsd
</a>
will change accordingly; the version at
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd
</a>
will not change.
</p>
<p>
Previous dated (and unchanging) versions of this schema
document are at:
</p>
<ul>
<li>
<a href="http://www.w3.org/2009/01/xml.xsd">
http://www.w3.org/2009/01/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2007/08/xml.xsd">
http://www.w3.org/2007/08/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2004/10/xml.xsd">
http://www.w3.org/2004/10/xml.xsd</a>
</li>
<li>
<a href="http://www.w3.org/2001/03/xml.xsd">
http://www.w3.org/2001/03/xml.xsd</a>
</li>
</ul>
</div>
</div>
Abstract Base type for all types of Actions.
Abstract Base type for all types of Actions.
Abstract Base type for all types of Actions.
Abstract Base type for all types of Actions.
Abstract Base type for all types of Actions.
Abstract Base type for all types of Actions.
Abstract Base type for all types of Actions.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
A registry query.
A QueryExpression child element is not required when invoking a stored query.
Common base type for all types that have unique identity.
If id is provided and is not in proper URN syntax then it is used for
linkage within document and is ignored by the registry. In this case the
registry generates a UUID URN for id attribute.
id must not be null when object is retrieved from the registry.
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h3>lang (as an attribute name)</h3>
<p>
denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml">
<h4>Notes</h4>
<p>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
</p>
<p>
See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
and the IANA language subtag registry at
<a href="http://www.iana.org/assignments/language-subtag-registry">
http://www.iana.org/assignments/language-subtag-registry</a>
for further information.
</p>
<p>
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</p>
</div>
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
Classification is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A Classification specifies references to two registry entrys.
The classifiedObject is id of the Object being classified.
The classificationNode is id of the ClassificationNode classying the object
ExternalIdentifier is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
Association is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
An Association specifies references to two previously submitted
registry entrys.
The sourceObject is id of the sourceObject in association
The targetObject is id of the targetObject in association
allowed types on Associations are HasMember, urn:oasis:names:tc:ebxml-regrep:AssociationType:HasMember, urn:ihe:iti:2007:AssociationType:RPLC, urn:ihe:iti:2007:AssociationType:XFRM, urn:ihe:iti:2007:AssociationType:APND, urn:ihe:iti:2007:AssociationType:XFRM_RPLC, and urn:ihe:iti:2007:AssociationType:signs
OCL
(not self.associationType.oclIsUndefined()) and
(
(self.associationType = 'urn:oasis:names:tc:ebxml-regrep:AssociationType:HasMember') or
(self.associationType = 'urn:ihe:iti:2007:AssociationType:RPLC') or
(self.associationType = 'urn:ihe:iti:2007:AssociationType:XFRM') or
(self.associationType = 'urn:ihe:iti:2007:AssociationType:APND') or
(self.associationType = 'urn:ihe:iti:2007:AssociationType:XFRM_RPLC') or
(self.associationType = 'urn:ihe:iti:2007:AssociationType:signs') or
(self.associationType = 'HasMember')
)
An Event that forms an audit trail in ebXML Registry.
An Event that forms an audit trail in ebXML Registry.
An Event that forms an audit trail in ebXML Registry.
An Event that forms an audit trail in ebXML Registry.
An Event that forms an audit trail in ebXML Registry.
An Event that forms an audit trail in ebXML Registry.
An Event that forms an audit trail in ebXML Registry.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
Use to reference an Object by its id.
Specifies the id attribute of the object as its id attribute.
id attribute in ObjectAttributes is exactly the same syntax and semantics as
id attribute in RegistryObject.
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationNode is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationNode is used to submit a Classification tree to the Registry.
The parent attribute is the id to the parent node. code is an optional code value for a ClassificationNode
often defined by an external taxonomy (e.g. NAICS)
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ClassificationScheme is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExternalLink is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
ExtrinsicObject is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Notification of registry events.
Notification of registry events.
Notification of registry events.
Notification of registry events.
Notification of registry events.
Notification of registry events.
Notification of registry events.
Abstract Base type for all types of Notify Actions
Abstract Base type for all types of Notify Actions
Abstract Base type for all types of Notify Actions
Abstract Base type for all types of Notify Actions
Abstract Base type for all types of Notify Actions
Abstract Base type for all types of Notify Actions
Abstract Base type for all types of Notify Actions
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
TelephoneNumber is the mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
RegistryPackage is the mapping of the same named interface in ebRIM.
It extends RegistryObject.
A RegistryPackage is a named collection of objects.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
A Subscription for specified Events in an ebXML V3+ registry.
A Subscription for specified Events in an ebXML V3+ registry.
A Subscription for specified Events in an ebXML V3+ registry.
A Subscription for specified Events in an ebXML V3+ registry.
A Subscription for specified Events in an ebXML V3+ registry.
A Subscription for specified Events in an ebXML V3+ registry.
A Subscription for specified Events in an ebXML V3+ registry.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
Mapping of the same named interface in ebRIM.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.
referenceURI is used by reference attributes within RIM.
Each attribute of type referenceURI references a RegistryObject with
specified URI as id.