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 MAY be used to defines the date and
time at which the initiator wishes to activitate 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 attribute support messaging protocols that specify an
attribute that indicates how the parties sending and receiving the message
will interpret the agreement value. There is no restriction on the value
of the type attribute; this choice is left to profiles of this
specification or depends on the messaging protocol used for the agreement.
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 attribute support messaging protocols that specify an
attribute that indicates how the parties sending and receiving the message
will interpret the agreement value. There is no restriction on the value
of the type attribute; this choice is left to profiles of this
specification or depends on the messaging protocol used for the agreement.
A description, in natural language, of the reason for the request, or other
free form textual information potentially useful for processing the request.
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 element is used in
AgreementUpdateResponse
and
AgreementUpdateException
document. It MUST be set to the
ID of the
AgreementUpdateRequest document that
these documents relate to.
This element is an XML document root element that defines a request to terminate an
existing
agreement. It references a current agreement using its identifier. The reason for
the
request can be communicated using the
Reason element.
An agreement termination request can succeed or fail. The result of processing an
update request is
communicated using an
AgreementTerminationResponse or an
AgreementTerminationException.
In a request, this optional element MAY be used to defines the date and
time at which the initiator wishes to terminate the agreement.
If absent, the responder MUST terminate the agreement as
soon as possible.
An agreement identifier is a non-empty-string value, possibly qualified using
a
type attribute. If the type attribute is not present, some protocols
require that the string content of the agreement identifier element MUST be a URI.
This attribute support messaging protocols that specify an
attribute that indicates how the parties sending and receiving the message
will interpret the agreement value. There is no restriction on the value
of the type attribute; this choice is left to profiles of this
specification or depends on the messaging protocol used for the agreement.
This attribute support messaging protocols that specify an
attribute that indicates how the parties sending and receiving the message
will interpret the agreement value. There is no restriction on the value
of the type attribute; this choice is left to profiles of this
specification or depends on the messaging protocol used for the agreement.