XML Schema Documentation

Super-types:	NovationResponseMessage < NovationConsentRefused (by extension)
Sub-types:	None

Name	NovationConsentRefused
Abstract	no
Documentation	Response message that should be sent by the transferee or remaining party if they cannot perform the requested novation.

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> ResponseMessageHeader </header> [1]

<validation> Validation </validation> [0..*]

Start Sequence [0..1]

<novation> Novation </novation> [1]

<party> Party </party> [3..*]

End Sequence

<reason> Reason </reason> [0..1]

</...>

Schema Component Representation

<xsd:complexType name="NovationConsentRefused">

<xsd:complexContent>

<xsd:extension base=" NovationResponseMessage ">

<xsd:sequence>

<xsd:element name="reason" type=" Reason " minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

Generated by <oXygen/> XML Editor using a modified version of xs3p that adds schema diagrams and chunking support.

Complex Type: NovationConsentRefused

[Table of contents]