XML Schema Documentation

Complex Type: DefinePosition

[Table of contents]

Super-types: Position < DefinePosition (by extension)
Sub-types: None
Name DefinePosition
Used by (from the same schema document) Complex Type PositionsAsserted , Complex Type PositionsAsserted
Abstract no
Documentation A type that allows a position to be defined. It includes identification information (ID and version), trade information, etc.
XML Instance Representation
<...
id=" xsd:ID [0..1]">
<positionId> PositionId </positionId> [1]

'A version-independent identifier for the position, possibly based on trade identifier.'

<version> xsd:positiveInteger </version> [0..1]

'A version identifier. Version identifiers must be ascending, i.e. higher numbers imply newer versions. There is no requirement that version identifiers for a position be sequential or small, so for example timestamp-based version identifiers could be used.'

<reportingRoles> ReportingRoles </reportingRoles> [0..1]

'Information about the roles of the parties with respect to reporting the positions.'

<constituent> PositionConstituent </constituent> [1]

'The components that create this position.'

<scheduledDate> ScheduledDate </scheduledDate> [0..*]

'Position level schedule date, such as final payment dates, in a simple and flexible format.'

<valuation> AssetValuation </valuation> [0..*]

'Valuation reported for the position, such as NPV or accrued interest. The asset/object references in the valuations should refer to the deal or components of the deal in the position, e.g. legs, streams, or underlyers.'

<forceMatch> PositionReference </forceMatch> [0..1]

'An optional reference to a position supplied by the matching party that is known to match this one.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="DefinePosition">
<xsd:complexContent>
<xsd:extension base=" Position ">
<xsd:sequence>
<xsd:element name="forceMatch" type=" PositionReference " minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>