Definition Type: Element
Name: conversationId
Namespace: http://www.fpml.org/2007/FpML-4-4
Type: fpml:ConversationId
Containing Schema: fpml-msg-4-4.xsd
MinOccurs 0
MaxOccurs (1)
Abstract
Documentation:
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.
Collapse XSD Schema Diagram:
Drilldown into conversationIdScheme in schema fpml-msg-4-4_xsd Drilldown into ConversationId in schema fpml-msg-4-4_xsdXSD Diagram of conversationId in schema fpml-msg-4-4_xsd (Financial products Markup Language (FpML®))
Collapse XSD Schema Code:
<xsd:element name="conversationId" type="ConversationId" minOccurs="0">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Attributes:
Name Type Default Value Use
conversationIdScheme fpml:conversationIdScheme Required
Collapse Derivation Tree: