element <proposedMatch> (local)

Namespace: | http://www.fpml.org/FpML-5/confirmation
Type: | EventProposedMatch
Content: | complex, 14 elements
Defined: | locally witnin ConfirmationStatus complexType in fpml-confirmation-processes-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<proposedMatch>
Content: | ((originatingEvent?, trade) | amendment | increase | (terminatingEvent?, termination) | novation | optionExercise | optionExpiry+ | deClear | additionalEvent), matchId?, difference*, matchScore?
</proposedMatch>

Content model elements (14):

  additionalEvent, amendment, deClear, difference, increase, matchId, matchScore, | novation, optionExercise, optionExpiry (defined in Events.model group), originatingEvent (defined in Events.model group), terminatingEvent (defined in Events.model group), termination, trade (defined in Events.model group)

Included in content model of elements (1):

  confirmationStatus

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

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

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.