.cdm-java.6.0.0-dev.82.source-code.cdm-observable-asset-CalculationAgent.schema.json Maven / Gradle / Ivy
{
"$schema": "http://json-schema.org/draft-04/schema#",
"$anchor": "cdm.observable.asset",
"type": "object",
"title": "CalculationAgent",
"description": "A class defining the ISDA calculation agent responsible for performing duties as defined in the applicable product definitions.",
"properties": {
"calculationAgentParty": {
"description": "Specifies the party which is the ISDA Calculation Agent for the trade. If more than one party is referenced then the parties are assumed to be co-calculation agents, i.e. they have joint responsibility.",
"$ref": "cdm-base-staticdata-party-AncillaryRoleEnum.schema.json"
},
"calculationAgentPartyEnum": {
"description": "Specifies the ISDA calculation agent responsible for performing duties as defined in the applicable product definitions. For example, the Calculation Agent may be defined as being the Non-exercising Party.",
"$ref": "cdm-observable-asset-PartyDeterminationEnum.schema.json"
},
"calculationAgentBusinessCenter": {
"description": "The city in which the office through which ISDA Calculation Agent is acting for purposes of the transaction is located The short-form confirm for a trade that is executed under a Sovereign or Asia Pacific Master Confirmation Agreement ( MCA ), does not need to specify the Calculation Agent. However, the confirm does need to specify the Calculation Agent City. This is due to the fact that the MCA sets the value for Calculation Agent but does not set the value for Calculation Agent City.",
"$ref": "cdm-base-datetime-metafields-FieldWithMetaBusinessCenterEnum.schema.json"
}
}
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy