Business-cXML
view release on metacpan or search on metacpan
t/xml-catalog/cXML-1.2.036/cXML.dtd view on Meta::CPAN
A Node is any entity connected to a Network.
type
A node can define itself as a router node or a copy node. Routers
assume responsibility for the transaction. Copy Nodes request to only
be aware of the transaction.
itemDetailsRequired
Intermediary Nodes may want to support special operations without
having to store specific information required to fulfill that operation.
This attribute tells the previous node to send ItemDetail information
when performing a PunchOutSetupRequest edit/inspect operation.
-->
<!ELEMENT Node (Credential+)>
<!ATTLIST Node
type (copy | route) #REQUIRED
itemDetailsRequired (yes) #IMPLIED
>
<!--
Identifies the previous document in the situation that a router node
forwards a message or request on to a more distant node.
payloadID
The payloadId of the original document.
-->
<!ELEMENT OriginalDocument EMPTY>
<!ATTLIST OriginalDocument
payloadID %string; #REQUIRED
>
<!--
A textual string representing who the UserAgent is conducting the cXML
conversation. Analogous to UserAgent for HTTP conversations.
-->
<!ELEMENT UserAgent (#PCDATA)>
<!--
DEPRECATED
Do not use this element.
-->
<!ELEMENT DigitalSignature ANY>
<!ATTLIST DigitalSignature
type %string; "PK7 self-contained"
encoding %string; "Base64"
>
<!--
A shared secret. Typically, this is a username/password type of secret
exchanged through a secure transport before communication takes place.
-->
<!ELEMENT SharedSecret ANY>
<!--
Represents an identity for a credential.
lastChangedTimestamp
When the underlying object last changed in the originating system.
This is used in cases where the same object (e.g. a buyer
organization) is replicated, and kept synchronized, across two
systems.
-->
<!ELEMENT Identity ANY>
<!ATTLIST Identity
lastChangedTimestamp %datetime.tz; #IMPLIED
>
<!--
A Credential Message Authentication Code (MAC). This is used in
situations where one party (the sender) must prove to another (the
receiver) that it is authenticated by a shared secret with a third
party trusted by both.
The MAC should be computed by the trusted third party and
transferred to the sender. The MAC should be opaque to the sender
(i.e., it should be secure and non-reversible). The MAC should
use as its inputs enough information to accomplish the following
goals:
(1) The MAC must prove to the receiver that it really originated
with the trusted third party. E.g., the MAC could use a shared
secret between the receiver and the trusted third party as its
secret key.
(2) The MAC should be usable only by a certain sender. E.g., the
MAC could authenticate an identifier for the sending organization.
(3) The MAC should prove that the sender is authorized to send on
behalf of the From organization. E.g., the MAC could authenticate
an identifier for the From organization.
(4) The MAC should limit the risk of the MAC being compromised and
used to impersonate the sender by another party communicating with
the receiver. E.g., the MAC could authenticate an expiration date
or sequence number.
type
An implementation-dependent identifier for the exact data
being authenticated and the method in which it is formatted
for authentication. Currently the only supported value is
"FromSenderCredentials".
algorithm
An implementation-dependent identifier for the exact MAC
algorithm used on the data. Currently the only supported
value is "HMAC-SHA1-96".
creationDate
The time at which this MAC was issued. The receiver must not
accept the MAC before this time.
expirationDate
The time at which this MAC expires. The receiver must not
accept the MAC after this time.
-->
<!ELEMENT CredentialMac (#PCDATA)>
<!ATTLIST CredentialMac
type %string; #REQUIRED
algorithm %string; #REQUIRED
creationDate %datetime.tz; #REQUIRED
( run in 2.573 seconds using v1.01-cache-2.11-cpan-98e64b0badf )