See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace.
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
Note that local names in this namespace are intended to be defined
only by the World Wide Web Consortium or its subgroups. The
following names are currently defined in this namespace and should
not be used with conflicting semantics by any Working Group,
specification, or document instance:
base (as an attribute name): denotes an attribute whose value
provides a URI to be used as the base for interpreting any
relative URIs in the scope of the element on which it
appears; its value is inherited. This name is reserved
by virtue of its definition in the XML Base specification.
lang (as an attribute name): 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.
space (as an attribute name): denotes an attribute whose
value is a keyword indicating what whitespace processing
discipline is intended for the content of the element; its
value is inherited. This name is reserved by virtue of its
definition in the XML specification.
Father (in any context at all): 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:
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
This schema defines attributes and an attribute group
suitable for use by
schemas wishing to allow xml:base, xml:lang or xml:space attributes
on elements they define.
To enable this, such a schema must import this schema
for the XML namespace, e.g. as follows:
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>
Subsequently, qualified reference to any of the attributes
or the group defined below will have the desired effect, e.g.
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
will define a type which will schema-validate an instance
element with any of those attributes
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
http://www.w3.org/2001/03/xml.xsd.
At the date of issue it can also be found at
http://www.w3.org/2001/xml.xsd.
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. In other words, if the XML Schema namespace changes, the version
of this document at
http://www.w3.org/2001/xml.xsd will change
accordingly; the version at
http://www.w3.org/2001/03/xml.xsd will not change.
This element is an XML document root element that defines a request to update an existing
agreement. It references a
current agreement using its identifier and proposes a new indentifier
to be used for an updated version of the agreement. That updated agreement is to be
created by taking the
content of the current agreement and applying one or several
updates to it.
The configuration data of the current agreement is not exchanged in the message. It
is assumed that this data is known and shared by the
communication partners. Partners are not required to use the same storage mechanism
or syntax to store the configuration information. The update requests
define the semantics of the requested update which both partners are to apply.
An agreement update request can succeed or fail. The result of processing an update
request is communicated using an
AgreementUpdateResponse or an
AgreementUpdateException .
An agreement update is atomic, meaning either all requests have been applied or none.
In a request, this optional element defines the date and time at which the initiator
activitates the new agreement. If absent, the initiator must
have deployed the new agreement before sending an update request to the communication
partner, and the partner may start using the new
agreement immediately.
This optional element defines the date and time at which the agreement will expire.
If absent, no explicit expiration date is
set for the agreement. This element may be set by the initiator.
The identifier of an agreement to be created by copying the current agreement configuration,
applying all requested updates and then changing the agreement
identifier to the indicated value.
This element identifies a single update to be applied to an agreement. It is an abstract
element, that can be sub-classed for specific types of
updates using the XML schema substitution mechanism. This version of this schema
only support certificate updates, but future versions MAY add other types
of updates, such as IP address changes, or server URL address changes.
This element is used in
AgreementUpdateResponse and
AgreementUpdateException document to identify the
AgreementUpdateRequest document that these documents relate to.
(ds:PGPKeyID , ds:PGPKeyPacket{0,1} , ANY element from ANY namespace OTHER than 'http://www.w3.org/2000/09/xmldsig#') | (ds:PGPKeyPacket , ANY element from ANY namespace OTHER than 'http://www.w3.org/2000/09/xmldsig#')
A certificate update request indicates that in the updated agreement a new certificate
is to be used
instead of a particular identified existing certificate.
The new certificate is exchanged using the
ds:KeyInfo structure defined in the W3C XML Signature specification.
The
ds:KeyInfoType type is defined in the XML Signature schema. In the Agreement Update specification,
its use is profiled as follows:
The
ds:KeyName and
ds:KeyValue elements MAY be present exactly once.
The
ds:RetrievalMethod element MUST NOT be used.
Exactly one
ds:X509Data element MUST be present.
The
ds:X509Data element MUST include at least one
ds:X509Certificate element.
A
ds:X509Data element MAY contain multiple
ds:X509Certificate elements.
A
ds:X509Data element MAY contain one or multiple
dsig11:X509Digest elements. If more than
one
dsig11:X509Digest element is present, each occurrence MUST have a different value for the
Algorithm attribute. The element
ds:X509IssuerSerial MUST NOT be used.
A
ds:X509Data element MAY contain at most one
ds:X509SubjectName.
The elements
ds:PGPData,
ds:MgmtData and
ds:SPKIData MUST NOT be present.
If the new certificate is issued by a Certificate Authority, then the
ds:X509Data structure SHOULD contain multiple
ds:X509Certificates, representing the full certificate chain.
(ds:PGPKeyID , ds:PGPKeyPacket{0,1} , ANY element from ANY namespace OTHER than 'http://www.w3.org/2000/09/xmldsig#') | (ds:PGPKeyPacket , ANY element from ANY namespace OTHER than 'http://www.w3.org/2000/09/xmldsig#')
