complexType "RepoLegBase"
Namespace:
http://www.fpml.org/FpML-5/confirmation
Content:
complex, 1 attribute, 5 elements
Defined:
globally in fpml-repo-5-8.xsd; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
Content Model Diagram
XML Representation Summary
<...
   
id
 = 
xsd:ID
   
>
   
Content: 
buyerPartyReference, buyerAccountReference?, sellerPartyReference, sellerAccountReference?, settlementDate
</...>
Content Model Elements (5):
settlementDate (defined in RepoLegBase complexType)
Known Direct Subtypes (2):
RepoFarLeg, RepoNearLeg
All Direct / Indirect Based Elements (2):
farLeg (in repo),
Known Usage Locations
Annotation
A transaction leg for a repo is equivalent to a single cash transaction. It is augmented here to carry some values that are of interest for the repo. Also note that the BuyerSeller model in this transaction must be the exact opposite of the one found in the near leg.
Type Definition Detail
Type Derivation Tree
Leg (extension)
  RepoLegBase
XML Source (w/o annotations (3); see within schema source)
<xsd:complexType name="RepoLegBase">
<xsd:complexContent>
<!--2015-02-23: Sec WG: extends "leg" type-->
<!--2015-02-23: Sec WG: agreed to remove attribute "id", instead extension from base class "Leg" which already includes attribute "id"-->
<xsd:extension base="Leg">
<xsd:sequence>
<!--2015-02-23: Sec WG: agreed to remove element "id" of type “RepoLegId" until we have requirement for identifying the leg -->
<!--<xsd:element name="id" type="RepoLegId" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A reference to a party transaction ID. This is provided in case the message creator wishes to record that the repo leg is associated with a particular trade identifier; typically this can be used for identifying a UTI associated with the leg.</xsd:documentation>
</xsd:annotation>
</xsd:element>-->
<xsd:group ref="BuyerSeller.model"/>
<!--<xsd:annotation>
<xsd:documentation xml:lang="en">A group which has cash settlement elements.</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>-->
<xsd:element name="settlementDate" type="AdjustableOrRelativeDate"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Content Element Detail (all declarations; defined within this component only; 1/5)
settlementDate
Type:
AdjustableOrRelativeDate, complex content
Settlement or Payment Date for the transaction.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="settlementDate" type="AdjustableOrRelativeDate"/>
XML schema documentation generated with DocFlex/XML 1.10b5 using DocFlex/XML XSDDoc 2.8.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.