schemas.fpml-4-6.fpml-msg-4-6.xsd Maven / Gradle / Ivy
Provides extra information not represented in the model that may be useful in processing the message i.e. diagnosing the reason for failure. In case the
extra information is in XML format, a CDATA section must be placed around the source message to prevent its interpretation as XML content.
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 type defining the basic structure of all FpML messages which is refined by its derived types.
The data type used for identifying a message address. It includes a partyIdScheme for keeping the type backward compatible with the PartyId complex type.
In the next major version, partyIdScheme attribute will be replaced by a messageAddressScheme attribute.
A type defining the content model for a generic message header that is refined by its derived classes.
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 data type use for message identifiers.
A type defining the content for a standard message sent when a recipient cannot interpret or process an earlier message.
A type defining the basic content for a message sent to inform another system that some 'business event' has occured. Notifications are not expected to be
replied to.
A type that refines the generic message header to match the requirements of a NotificationMessage.
A copy of the unique message identifier (within it own coding scheme) to which this message is responding.
A type defining additional information that may be recorded against a message.
Identifies that party that has ownership of this information.
Provides a lexical location (i.e. a line number and character for bad XML) or an XPath location (i.e. place to identify the bad location for valid XML).
The value of the locationType attribute defines which type of location has been given. It may take the values 'lexical' or 'xpath'.
DEPRECATED. It will be removed in FpML 5.0. New implementations are encouraged to use the locationType attribute.
A type defining a content model for describing the nature and possible location of a error within a previous message.
A machine interpretable error code.
A value indicating the location of the problem within the subject message.
Plain English text describing the associated error condition
A reference identifying a rule within a validation scheme
Any string of additional data that may help the message processor, for example in a rejection message this might contain a code value or the text
of any one of the messages (within a CDATA section).
Defines a list of machine interpretable error codes.
A type defining the basic content of a message that requests the receiver to perform some business operation determined by the message type and its
content.
A type refining the generic message header content to make it specific to request messages.
A type defining the content model for a message allowing one party to query the status of one or many trades previously sent to another party.
An instance of a unique trade identifier.
A legal entity or a subdivision of a legal entity.
Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time
during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation
transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
A type refining the generic message content model to make it specific to response messages.
A type refining the generic message header to make it specific to response messages.
A copy of the unique message identifier (within it own coding scheme) to which this message is responding.
A type defining the content model of a response message generated when an operation as requested on a trade unknown to the service.
An instance of a unique trade identifier.
A legal entity or a subdivision of a legal entity.
Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time
during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation
transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
A type defining the content model for a message normally generated in response to a RequestTradeStatus request.
A collection of data values describing the state of the given trade.
A legal entity or a subdivision of a legal entity.
Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time
during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation
transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
A type used in trade status enquiry messages which relates a trade identifier to its current status value.
An instance of a unique trade identifier.
The trade status value.
The type used to hold TradeStatusScheme values.
A model group which has exception elements.
An instance of the Reason type used to record the nature of any errors associated with a message.
Any string of additional data that may help the message processor, for example in a rejection message this might contain a code value or the text
of the original request (within a CDATA section).
Defines the structure that contains routing and identification information, which allows processing and transfer of the message. It contains only messaging
information that is applicable to all messages. If the information is not message related or is not applicable to all messages then it is not defined in the message header.
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.
An abstract trade error response message containing a singe trade or trade reference.
A legal entity or a subdivision of a legal entity.
Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time
during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation
transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
An error response message indicating that a trade has already been cancelled.
A type defining the content model for a message sent by a confirmation provider when it believes that one party has repeated a request to confirm a
trade.
An instance of a unique trade identifier.
A legal entity or a subdivision of a legal entity.
Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time
during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation
transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
An error response message indicating that a trade has already been terminated.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy