Super-types: | MessageHeader < RequestMessageHeader (by extension) |
---|---|
Sub-types: | None |
Name | RequestMessageHeader |
---|---|
Used by (from the same schema document) | Complex Type RequestMessage |
Abstract | no |
Documentation | A type refining the generic message header content to make it specific to request messages. |
'The unique identifier (name) for the conversation (session), this message is within. A conversation identifier is usually assigned by the initiator of a conversation. Conversations may only be initiated and terminated. Joining conversations has the effect of initiating new conversations. Conversations cannot be split; this instead has the effect of parallel activities on the same conversation or the initiation of a new conversation. Each message belongs to only one conversation. Conversation scopes are defined in the business process definition.'
'A unique identifier (within its coding scheme) assigned to the message by its creating party.'
'The unique identifier (within its coding scheme) for the originator of a message instance.'
'A unique identifier (within its coding scheme) indicating an intended recipent of a message.'
'A unique identifier (within the specified coding scheme) giving the details of some party to whom a copy of this message will be sent for reference.'
'The date and time (on the source system) when this message instance was created.'
'The date and time (on the source system) when this message instance will be considered expired.'
'Additional message information that may be provided by each involved party.'