XML Schema Documentation

Complex Type: NovationConsentRequest

[Table of contents]

Super-types: NovationRequestMessage < NovationConsentRequest (by extension)
Sub-types: None
Name NovationConsentRequest
Abstract no
Documentation A request message that passes details of the previously negotiated transaction that the transferor wishes to novate as well as describing the identity and roles of each party. As the same message is sent to both the transferee and remaining party it must contain the complete description of the underlying transaction (rather than just a reference) as the transferee will not have record of it.
XML Instance Representation
<...
version=" xsd:token (value comes from list: {'4-0'|'4-1'|'4-2'|'4-3'|'4-4'}) [1]

'Indicate which version of the FpML Schema an FpML message adheres to.'

"

expectedBuild=" xsd:positiveInteger [0..1]

'This optional attribute can be supplied by a message creator in an FpML instance to specify which build number of the schema was used to define the message when it was generated.'

"

actualBuild="12 [0..1]

'The specific build number of this schema version. This attribute is not included in an instance document. Instead, it is supplied by the XML parser when the document is validated against the FpML schema and indicates the build number of the schema file. Every time FpML publishes a change to the schema, validation rules, or examples within a version (e.g., version 4.2) the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same.'

"
>
<header> RequestMessageHeader </header> [1]
<validation> Validation </validation> [0..*]
<novation> Novation </novation> [1]
<party> Party </party> [3..*]
</...>
Diagram
type_NovationRequestMessage
Schema Component Representation
<xsd:complexType name="NovationConsentRequest">
<xsd:complexContent>
<xsd:extension base=" NovationRequestMessage "/>
</xsd:complexContent>
</xsd:complexType>