.cdm-java.6.0.0-dev.82.source-code.cdm-event-common-Trade.schema.json Maven / Gradle / Ivy

Go to download
{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "$anchor": "cdm.event.common",
  "type": "object",
  "title": "Trade",
  "description": "Defines the output of a financial transaction between parties - a Business Event. A Trade impacts the financial position (i.e. the balance sheet) of involved parties.",
  "properties": {
    "product": {
      "description": "The underlying product to be included in a contract or execution.",
      "$ref": "cdm-product-template-NonTransferableProduct.schema.json"
    },
    "tradeLot": {
      "description": "Specifies the price, quantity and effective date of each trade lot, when the same product may be traded multiple times in different lots with the same counterparty. In a trade increase, a new trade lot is added to the list, with the corresponding effective date. In a trade decrease, the existing trade lot(s) are decreased of the corresponding quantity (and an unwind fee may have to be settled). The multiple cardinality and the ability to increase existing trades is used for Equity Swaps in particular.",
      "type": "array",
      "items": {
        "$ref": "cdm-product-template-TradeLot.schema.json"
      },
      "minItems": 1
    },
    "counterparty": {
      "description": "Specifies the parties which are the two counterparties to the transaction.  The product is agnostic to the actual parties to the transaction, with the party references abstracted away from the product definition and replaced by the counterparty enum (e.g. CounterpartyEnum values Party1 or Party2). The counterparty enum can then be positioned in the product (e.g. to specify which counterparty is the payer, receiver etc) and this counterparties attribute, which is positioned outside of the product definition, allows the counterparty enum to be associated with an actual party reference.",
      "type": "array",
      "items": {
        "$ref": "cdm-base-staticdata-party-Counterparty.schema.json"
      },
      "minItems": 2,
      "maxItems": 2
    },
    "ancillaryParty": {
      "description": "Specifies the parties with ancillary roles in the transaction. The product is agnostic to the actual parties involved in the transaction, with the party references abstracted away from the product definition and replaced by the AncillaryRoleEnum. The AncillaryRoleEnum can then be positioned in the product and this AncillaryParty type, which is positioned outside of the product definition, allows the AncillaryRoleEnum to be associated with an actual party reference.",
      "type": "array",
      "items": {
        "$ref": "cdm-base-staticdata-party-AncillaryParty.schema.json"
      },
      "minItems": 0
    },
    "adjustment": {
      "description": "Specifies the conditions that govern the adjustment to the quantity of a product being traded: e.g. execution, portfolio rebalancing etc. It is typically used in the context of Equity Swaps.",
      "$ref": "cdm-product-common-NotionalAdjustmentEnum.schema.json"
    },
    "tradeIdentifier": {
      "description": "Represents the identifier(s) that uniquely identify a trade for an identity issuer. A trade can include multiple identifiers, for example a trade that is reportable to both the CFTC and ESMA, and then has an associated USI (Unique Swap Identifier) UTI (Unique Trade Identifier).",
      "type": "array",
      "items": {
        "$ref": "cdm-event-common-TradeIdentifier.schema.json"
      },
      "minItems": 1
    },
    "tradeDate": {
      "description": "Specifies the date which the trade was agreed.",
      "$ref": "com-rosetta-model-metafields-FieldWithMetaString.schema.json"
    },
    "tradeTime": {
      "description": "Denotes the trade time and timezone as agreed by the parties to the trade.",
      "$ref": "cdm-base-datetime-metafields-FieldWithMetaTimeZone.schema.json"
    },
    "party": {
      "description": "Represents the parties to the trade. The cardinality is optional to address the case where the trade is defined within a BusinessEvent data type, in which case the party is specified in BusinessEvent.",
      "type": "array",
      "items": {
        "$ref": "cdm-base-staticdata-party-Party.schema.json"
      },
      "minItems": 0
    },
    "partyRole": {
      "description": "Represents the role each specified party takes in the trade. further to the principal roles, payer and receiver.",
      "type": "array",
      "items": {
        "$ref": "cdm-base-staticdata-party-PartyRole.schema.json"
      },
      "minItems": 0
    },
    "executionDetails": {
      "description": "Represents information specific to trades that arose from executions.",
      "$ref": "cdm-event-common-ExecutionDetails.schema.json"
    },
    "contractDetails": {
      "description": "Represents information specific to trades involving contractual products.",
      "$ref": "cdm-event-common-ContractDetails.schema.json"
    },
    "clearedDate": {
      "description": "Specifies the date on which a trade is cleared (novated) through a central counterparty clearing service.",
      "type": "string"
    },
    "collateral": {
      "description": "Represents the collateral obligations of a party.",
      "$ref": "cdm-product-collateral-Collateral.schema.json"
    },
    "account": {
      "description": "Represents a party's granular account information, which may be used in subsequent internal processing.",
      "type": "array",
      "items": {
        "$ref": "cdm-base-staticdata-party-Account.schema.json"
      },
      "minItems": 0
    }
  },
  "required": [
    "tradeDate"
  ]
}