ISFMessage
- Header
- The header contains information that is used within FTM. In particular, the element BusinessConcept specifies the business purpose of the transaction.
- Transaction Data
- Transaction Data contains the structure and content applicable for the transaction's business purpose
(BusinessConcept). The definition of ISFMessage references an abstract element called Transaction in this
position. An actual ISF XML document will contain a substitute element in place of Transaction that defines
the content applicable for the transaction type. Such an element is referred to as a transaction element.
ISF Core defines two transaction elements, Command, which is used for command messages from the FTM OAC, and Wrapper, which allows any content. The element Wrapper is typically used for transactions where the content is trivial and not worth modeling, or for transactions that are passed through the FTM system without regard to their content.
Typically, transaction elements are defined as part of an ISF Extension to support the transaction types defined by that extension. For more information, see Transaction data content and Standard extensions.
- Addenda
- Addenda is a placeholder for any other data that may be useful for a particular solution.
The element SourceData provides a place to record information about the source message that was mapped to the ISF document, and may contain the complete content of the original input message.
Addenda may contain any other elements that are qualified with a namespace prefix. Such elements need not be defined in the schema, and are not checked for validity when the ISF document is validated to the schema.