You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "@experimental context type representing a tradable product. To be used with OMS and EMS systems.\n\nThis type is currently only loosely defined as an extensible context object, with an optional instrument field.\n\nThe Product schema does not explicitly include identifiers in the id section, as there is not a common standard for such identifiers. Applications can, however, populate this part of the contract with custom identifiers if so desired.",
7
-
"allOf": [
8
-
{
9
-
"type": "object",
10
-
"properties": {
11
-
"type": {
12
-
"const": "fdc3.product"
13
-
},
14
-
"id": {
15
-
"type": "object",
16
-
"additionalProperties": {
17
-
"type": "string"
18
-
},
19
-
"title": "Product Identifiers",
20
-
"description": "One or more identifiers that refer to the product. Specific key names for systems are expected to be standardized in future."
21
-
},
22
-
"name": {
23
-
"type": "string",
24
-
"title": "Product Name",
25
-
"description": "A human-readable summary of the product."
26
-
},
27
-
"instrument": {
28
-
"$ref": "instrument.schema.json",
29
-
"title": "Product Instrument",
30
-
"description": "A financial instrument that relates to the definition of this product"
"description": "@experimental context type representing a tradable product. To be used with OMS and EMS systems.\n\nThis type is currently only loosely defined as an extensible context object, with an optional instrument field.\n\nThe Product schema does not explicitly include identifiers in the id section, as there is not a common standard for such identifiers. Applications can, however, populate this part of the contract with custom identifiers if so desired.",
7
+
"allOf": [
8
+
{
9
+
"type": "object",
10
+
"properties": {
11
+
"type": {
12
+
"const": "fdc3.product"
13
+
},
14
+
"id": {
15
+
"type": "object",
16
+
"additionalProperties": {
17
+
"type": "string"
18
+
},
19
+
"title": "Product Identifiers",
20
+
"description": "One or more identifiers that refer to the product. Specific key names for systems are expected to be standardized in future."
21
+
},
22
+
"name": {
23
+
"type": "string",
24
+
"title": "Product Name",
25
+
"description": "A human-readable summary of the product."
26
+
},
27
+
"notes": {
28
+
"type": "string",
29
+
"title": "Notes",
30
+
"description": "A description or set of notes."
31
+
},
32
+
"instrument": {
33
+
"$ref": "instrument.schema.json",
34
+
"title": "Product Instrument",
35
+
"description": "A financial instrument that relates to the definition of this product"
"description": "@experimental context type representing a trade. To be used with execution systems.\n\nThis type currently only defines a required `id` field, which should provide a reference to the trade in one or more systems, an optional human readable `name` field to be used to summarize the trade and a required `product` field that may be used to provide additional detail about the trade, which is currently typed as a unspecified Context type, but `product` is expected to be standardized in future.\n\n The Trade schema does not explicitly include identifiers in the id section, as there is not a common standard for such identifiers. Applications can, however, populate this part of the contract with custom identifiers if so desired.",
7
-
"allOf": [
8
-
{
9
-
"type": "object",
10
-
"properties": {
11
-
"type": {
12
-
"const": "fdc3.trade"
13
-
},
14
-
"id": {
15
-
"type": "object",
16
-
"additionalProperties": {
17
-
"type": "string"
18
-
},
19
-
"title": "Trade Identifiers",
20
-
"description": "One or more identifiers that refer to the trade in an OMS, EMS or related system. Specific key names for systems are expected to be standardized in future."
21
-
},
22
-
"name": {
23
-
"type": "string",
24
-
"title": "Trade Name",
25
-
"description": "A human-readable summary of the trade."
26
-
},
27
-
"product": {
28
-
"$ref": "product.schema.json",
29
-
"title": "Traded product",
30
-
"description": "A product that is the subject of the trade."
"description": "@experimental context type representing a trade. To be used with execution systems.\n\nThis type currently only defines a required `id` field, which should provide a reference to the trade in one or more systems, an optional human readable `name` field to be used to summarize the trade and a required `product` field that may be used to provide additional detail about the trade, which is currently typed as a unspecified Context type, but `product` is expected to be standardized in future.\n\n The Trade schema does not explicitly include identifiers in the id section, as there is not a common standard for such identifiers. Applications can, however, populate this part of the contract with custom identifiers if so desired.",
7
+
"allOf": [
8
+
{
9
+
"type": "object",
10
+
"properties": {
11
+
"type": {
12
+
"const": "fdc3.trade"
13
+
},
14
+
"id": {
15
+
"type": "object",
16
+
"additionalProperties": {
17
+
"type": "string"
18
+
},
19
+
"title": "Trade Identifiers",
20
+
"description": "One or more identifiers that refer to the trade in an OMS, EMS or related system. Specific key names for systems are expected to be standardized in future."
21
+
},
22
+
"name": {
23
+
"type": "string",
24
+
"title": "Trade Name",
25
+
"description": "A human-readable summary of the trade."
26
+
},
27
+
"notes": {
28
+
"type": "string",
29
+
"title": "Notes",
30
+
"description": "A description or set of notes."
31
+
},
32
+
"product": {
33
+
"$ref": "product.schema.json",
34
+
"title": "Traded product",
35
+
"description": "A product that is the subject of the trade."
0 commit comments