element <proposedMatch> (local)

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

Content Model Diagram

XML Representation Summary
<proposedMatch>
Content: | tradeCashflowsId?, (tradeIdentifyingItems?, adjustedPaymentDate?, payment*)?, matchId?, difference*, matchScore?
</proposedMatch>

Content model elements (7):

  adjustedPaymentDate (defined in TradeCashflows.model group),
  difference (defined in ProposedMatch.model group),
  matchId (defined in ProposedMatch.model group),
  matchScore,
  payment (defined in TradeCashflows.model group),
  tradeCashflowsId (defined in IdAndTradeCashflows.model group),
  tradeIdentifyingItems (defined in TradeCashflows.model group)

Included in content model of elements (1):

  tradeCashflowsMatchResult

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

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

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.