element <amendment> (local)

Namespace: | http://www.fpml.org/FpML-5/confirmation
Type: | TradeAmendmentContent
Content: | complex, 5 elements
Defined: | locally witnin Events.model group in fpml-business-events-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<amendment>
Content: | trade, agreementDate, executionDateTime?, effectiveDate, payment?
</amendment>

Content model elements (5):

  agreementDate,
  effectiveDate (defined in AgreementAndEffectiveDates.model group),
  executionDateTime (defined in AgreementAndEffectiveDates.model group),
  payment (defined in TradeAlterationPayment.model group),
  trade (in amendment)

Included in content model of elements (23):

  allegedEvent, assertedEvent, clearingConfirmed, clearingRefused, confirmationAgreed, confirmationDisputed, consentGranted, consentRefused, executionAdvice, executionAdviceRetracted, executionNotification, executionRetracted, history, optionExpirationNotification, proposedMatch, requestClearing, requestClearingRetracted, requestConfirmation, requestConfirmationRetracted, requestConsent, requestConsentRetracted, requestExecution, requestExecutionRetracted

XML Source (see within schema source)

<xsd:element name="amendment" type="TradeAmendmentContent"/>

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.