# XML Schema Documentation

### Complex Type: Position

#### [Table of contents]

Super-types: | None
Sub-types: | None

Name | Position
Abstract | no
Documentation | A collection of related trades or positions and the corresponding aggregate exposures generated by these.

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.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="Position">
<xsd:sequence>
<xsd:group ref=" PositionIdAndVersion.model "/>
<xsd:element name="reportingRoles" type=" ReportingRoles " minOccurs="0"/>
<xsd:element name="constituent" type=" PositionConstituent "/>
<xsd:element name="scheduledDate" type=" ScheduledDate " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="valuation" type=" AssetValuation " minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type=" xsd:ID "/>
</xsd:complexType>