Sending node: Message accepted for delivery and submitted
Active node on the delivery route: Message forwarded to next hop
Destination node:Successful delivery to Recipient in synchronous scenarios, to MsgBox if asynchronous
Only MsgBox node: Initial fetch of Message by Recipient from his MsgBox
Ultimate Recipient node, after acceptance of message, after successful decryption of payload
Message delivery time instants, quality and receipts requested
Timestamps, priority etc.
Production of content by Requester respective (response) Provider
Time when delivery was started (submission by Senders node)
Time when sending node should submit message
Date, when this message is obsolete; may be set by Initiator
Time of entry in a Recipients MsgBox or reception by Recipient in synchronous case
Time of first comitted fetch from MsgBox by recipient
Reception time set by the Ultimate Recipient ("Reader", target application)
Property like priority etc. - XTA here points to "Service Profile"
Receipts requested by sender or author
Logical identifier and optional security tokens of that entity (binary, may carry SAML, too)
Value of generic party identifier, as classified by @type attribute, e.g.: Prefix:Kennung
Orientation: ebMS Core: type, how to interpret Party-Id value, e.g.: xöv oder Justiz
optional "friendly name" value for displaying in user agents (as e.g. known from eMail)
Concrete role of party in business scenario (e.g. "buyer", "Meldehörde", "Standesamt"...)
Requester resp. (response-) Provider
Destinations of the message
If response expected different from value outlined in "From" address
Ultimate target of the message
Process ID message is realated to
Process may have a name, e.g. "order"
Referenced application level Message-Id(s)
References to business process-id's (like ebMS Conversation-Id, "Aktenzeichen" in Germany)
Ref on requester (Source Application) side
Ref on responder (Target Application) side, if different
Message subject text (informational)
Distinct service in a certain business scenario context; in the XÖV context this is the "Dienste URI"
Domain qualifier, e.g. Meldewesen, XVergabe...
Payload: Type of document or message. MessageTypes normally bound to specific BusinessScenario
Time stamps, receipts to be generated, service quality
Message originators and reply address
Actual and other destinations of Message
Message ID and Message relations
General payload properties, common to all scenarios
Scenarios specific payload properties, to be agreed upon per scenario
Sending node, entry may be added by Sender node
Other destinations of message - informational, as known from e-mail
Destinations in cc role
Message size in bytes
"true", if test-message; defaults to "false"