element <party> (local)
Namespace: |
|
Type: |
|
Content: |
complex, 1 attribute, 2 elements |
Defined: |
|
Content Model Diagram
XML Representation Summary |
| <party |
| |
|
| |
> |
| |
|
| </party> |
Content model elements (2):
-
Included in content model of elements (43):
-
allocationAcknowledgement,
allocationApproved,
allocationRefused,
clearingAcknowledgement,
clearingConfirmed,
clearingRefused,
clearingStatus,
confirmationAcknowledgement,
confirmationAgreed,
confirmationDisputed,
confirmationStatus,
consentAcknowledgement,
consentGranted,
consentRefused,
dataDocument,
eventStatusResponse,
executionAcknowledgement,
executionAdvice,
executionAdviceAcknowledgement,
executionAdviceRetracted,
executionNotification,
executionRetracted,
maturityAcknowledgement,
maturityNotification,
optionExpirationNotification,
requestAllocation,
requestAllocationRetracted,
requestClearing,
requestClearingRetracted,
requestConfirmation,
requestConfirmationRetracted,
requestConsent,
requestConsentRetracted,
requestEventStatus,
requestExecution,
requestExecutionRetracted,
requestTradeReferenceInformationUpdate,
requestTradeReferenceInformationUpdateRetracted,
tradeChangeAdvice,
tradeChangeAdviceAcknowledgement,
tradeChangeAdviceRetracted,
tradeReferenceInformationUpdateAcknowledgement,
valuationDocument
Annotation
A legal entity or a subdivision of a legal entity.
Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
XML Source (w/o annotations (1); see within schema source)
| <xsd:element maxOccurs="unbounded" name="party" type="Party"/> |
