finos · kriswest · Jul 28, 2023 · Jul 7, 2023 · Jul 7, 2023 · Jul 7, 2023
diff --git a/docs/context/ref/Order.md b/docs/context/ref/Order.md
@@ -0,0 +1,69 @@
+---
+id: Order
+sidebar_label: Order
+title: Order
+hide_title: true
+---
+# `Order`
+
+[`@experimental`](/docs/fdc3-compliance#experimental-features) context type representing an order. To be used with OMS and EMS systems.
+
+This type currently only defines a required `id` field, which should provide a reference to the order in one or more systems, an optional human readable `name` field to be used to summarize the order and an optional `details` field that may be used to provide additional detail about the order, including a context representing a `product`, which may be extended with arbitrary properties. The `details.product` field is currently typed as a unspecified Context type, but both `details` and `details.product` are expected to be standardized in future. require not just a single trade, but multiple.
+
+## Type
+
+`fdc3.order`
+
+## Schema
+
+<https://fdc3.finos.org/schemas/next/order.schema.json>
+
+## Details
+
+| Property     | Type       | Required | Details             |
+|--------------|------------|----------|---------------------------|
+| `type`       | string     | Yes      | `'fdc3.order'`        |
+| `id`         | object     | Yes      | One or more identifiers that refer to the order in an OMS, EMS or related system. Specific key names for systems are expected to be standardized in future. E.g.:`{ myOMS: '12345' }` |
+| `name`       | string     | No       | An optional human-readable summary of the order.    |
+| `details`    | object     | No       | Optional additional details about the order, which may include a product element that is an, as yet undefined but extensible, Context  |
+| `details.product`    | Product     | No       | The product that the order relates to  |
+
+## Examples
+
+```js
+const order1 = {
+    "type": "fdc3.order",
+    "name": "...",
+    "id": {
+        "myOMS": "12345"
+    },
+    "details": {
+        "product": {
+            "type": "fdc3.product",
+            "instrument": {
+                "type": "fdc3.instrument",
+                "id": {
+                    "ticker": "MSFT"
+                }
+            }
+        }
+    }
+};
+```
+
+```js
+const order2 = {
+    "type": "fdc3.order",
+    "id": {
+        "myOMS": "ABC123"
+    }
+};
+```
+
+## See Also
+
+Other Types
+
+- [OrderList](OrderList)
+- [Product](Product)
+- [Trade](Trade)
diff --git a/docs/context/ref/OrderList.md b/docs/context/ref/OrderList.md
@@ -0,0 +1,58 @@
+---
+id: OrderList
+sidebar_label: OrderList
+title: OrderList
+hide_title: true
+---
+# `OrderList`
+
+[`@experimental`](/docs/fdc3-compliance#experimental-features) A list of orders. Use this type for use cases that require not just a single order, but multiple.
+
+Notes:
+
+- The OrderList 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.
+
+## Type
+
+`fdc3.orderList`
+
+## Schema
+
+<https://fdc3.finos.org/schemas/next/orderList.schema.json>
+
+## Details
+
+| Property     | Type       | Required | Example Value             |
+|--------------|------------|----------|---------------------------|
+| `type`       | string     | Yes      | `'fdc3.orderList'`        |
+| `id`         | object     | No       | `{ listId: '1234' }` |
+| `name`       | string     | No       | `'Today's orders'`    |
+| `orders`     | Trade[]    | Yes      | `[order1, order2]`  |
+
+## Example
+
+```js
+const orderList = {
+    type: "fdc3.orderList",
+    orders: [
+        {
+            "type": "fdc3.order",
+            "id": {
+                "myOMS": "ABC123"
+            }
+        },
+        {
+            "type": "fdc3.order",
+            "id": {
+                "myOMS": "DEF456"
+            }
+        }
+    ]
+};
+```
+
+## See Also
+
+Other Types
+
+- [Order](Order)
diff --git a/docs/context/ref/Product.md b/docs/context/ref/Product.md
@@ -0,0 +1,53 @@
+---
+id: Product
+sidebar_label: Product
+title: Product
+hide_title: true
+---
+# `Product`
+
+[`@experimental`](/docs/fdc3-compliance#experimental-features) 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.
+
+Notes:
+
+- The 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.
+
+## Type
+
+`fdc3.product`
+
+## Schema
+
+<https://fdc3.finos.org/schemas/next/product.schema.json>
+
+## Details
+
+| Property     | Type       | Required | Example Value             |
+|--------------|------------|----------|---------------------------|
+| `type`       | string     | Yes      | `'fdc3.product'`        |
+| `id`         | object     | Yes      | One or more identifiers that refer to the product. Specific key names for systems are expected to be standardized in future. |
+| `name`       | string     | No       | A human-readable summary of the product. |
+| `instrument` | Product[]  | No       | A financial instrument that relates to the definition of this product. |
+
+## Example
+
+```js
+const product = {
+    "type": "fdc3.product",
+    "instrument": {
+        "type": "fdc3.instrument",
+        "id": {
+            "ticker": "MSFT"
+        }
+    }
+};
+```
+
+## See Also
+
+Other Types
+
+- [Instrument](Instrument)
+- [ProductList](ProductList)
+- [Order](Order)
+- [Trade](Trade)
diff --git a/docs/context/ref/Trade.md b/docs/context/ref/Trade.md
@@ -0,0 +1,60 @@
+---
+id: Trade
+sidebar_label: Trade
+title: Trade
+hide_title: true
+---
+# `Trade`
+
+[`@experimental`](/docs/fdc3-compliance#experimental-features) context type representing a trade. To be used with execution systems.
+
+This 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.
+
+Notes:
+
+- 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.
+
+## Type
+
+`fdc3.trade`
+
+## Schema
+
+<https://fdc3.finos.org/schemas/next/trade.schema.json>
+
+## Details
+
+| Property     | Type       | Required | Details             |
+|--------------|------------|----------|---------------------------|
+| `type`       | string     | Yes      | `'fdc3.trade'`        |
+| `id`         | object     | Yes      | 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. |
+| `name`       | string     | No       | A human-readable summary of the trade, e.g. `'100 TSLA @ 290.85 USD'`    |
+| `product`    | Product    | Yes      | A tradeable product  |
+
+## Example
+
+```js
+const trade = {
+    "type": "fdc3.trade",
+    "name": "...",
+    "id": {
+        "myEMS": "12345"
+    },
+    "product": {
+        "type": "fdc3.product",
+        "instrument": {
+            "type": "fdc3.instrument",
+            "id": {
+                "ticker": "MSFT"
+            }
+        }
+    }
+};
+```
+
+## See Also
+
+Other Types
+
+- [Product](Product)
+- [TradeList](TradeList)
diff --git a/docs/context/ref/TradeList.md b/docs/context/ref/TradeList.md
@@ -0,0 +1,77 @@
+---
+id: TradeList
+sidebar_label: TradeList
+title: TradeList
+hide_title: true
+---
+# `TradeList`
+
+[`@experimental`](/docs/fdc3-compliance#experimental-features) A list of trades. Use this type for use cases that require not just a single trade, but multiple.
+
+Notes:
+
+- The TradeList 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.
+
+## Type
+
+`fdc3.tradeList`
+
+## Schema
+
+<https://fdc3.finos.org/schemas/next/tradeList.schema.json>
+
+## Details
+
+| Property     | Type       | Required | Example Value             |
+|--------------|------------|----------|---------------------------|
+| `type`       | string     | Yes      | `'fdc3.tradeList'`        |
+| `id`         | object     | No       | `{ listId: '1234' }` |
+| `name`       | string     | No       | `'Today's trades'`    |
+| `trades`     | Trade[]    | Yes      | `[trade1, trade2]`  |
+
+## Example
+
+```js
+const tradeList = {
+    type: "fdc3.tradeList",
+    trades: [
+        {
+            "type": "fdc3.trade",
+            "name": "...",
+            "id": {
+                "myEMS": "12345"
+            },
+            "product": {
+                "type": "fdc3.product",
+                "instrument": {
+                    "type": "fdc3.instrument",
+                    "id": {
+                        "ticker": "MSFT"
+                    }
+                }
+            }
+        },
+        {
+            "type": "fdc3.trade",
+            "id": {
+                "myEMS": "67890"
+            },
+            "product": {
+                "type": "fdc3.product",
+                "instrument": {
+                    "type": "fdc3.instrument",
+                    "id": {
+                        "ticker": "TSLA"
+                    }
+                }
+            }
+        }
+    ]
+};
+```
+
+## See Also
+
+Other Types
+
+- [Trade](Trade)
diff --git a/docs/context/spec.md b/docs/context/spec.md
@@ -184,6 +184,14 @@ The following are standard FDC3 context types:
 - [`fdc3.transactionResult`](ref/TransactionResult) ([schema](/schemas/next/transactionresult.schema.json))
 - [`fdc3.valuation`](ref/Valuation) ([schema](/schemas/next/valuation.schema.json))
 
+The following are [`@experimental`](/docs/fdc3-compliance#experimental-features) types, which are in the process of being defined:
+
+- [`fdc3.order`](ref/Order) ([schema](/schemas/next/order.schema.json))
+- [`fdc3.orderList`](ref/OrderList) ([schema](/schemas/next/orderList.schema.json))
+- [`fdc3.product`](ref/Product) ([schema](/schemas/next/product.schema.json))
+- [`fdc3.trade`](ref/Trade) ([schema](/schemas/next/trade.schema.json))
+- [`fdc3.tradeList`](ref/TradeList) ([schema](/schemas/next/tradeList.schema.json))
+
 ### Examples
 
 The below examples show how the base context data interface can be used to define specific context data objects.