element <proposedMatch> (local)

Namespace: | http://www.fpml.org/FpML-5/reporting
Type: | PositionProposedMatch
Content: | complex, 9 elements
Defined: | locally witnin PositionMatchResult complexType in fpml-reconciliation-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<proposedMatch>
Content: | positionId?, version?, (reportingRoles?, constituent?, scheduledDate*, valuation*)?, matchId?, difference*, matchScore?
</proposedMatch>

Content model elements (9):

  constituent (defined in PositionWithoutId.model group), difference (defined in ProposedMatch.model group), matchId (defined in ProposedMatch.model group), matchScore, positionId, | reportingRoles (defined in PositionWithoutId.model group), scheduledDate (defined in PositionWithoutId.model group), valuation (defined in PositionWithoutId.model group), version (defined in PositionIdAndVersion.model group)

Included in content model of elements (1):

  positionMatchResult

Annotation
"Other side's" position that meets the minimimum matching criteria and is proposed as match to the position that is being asserted.
XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="proposedMatch" type="PositionProposedMatch"/>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.