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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
10
10
11
11
### Changed
12
12
13
+
* Updated definition of the `Instrument` context type to include optional market identifiers ([#819](https://github.com/finos/FDC3/pull/819))
Copy file name to clipboardExpand all lines: docs/context/ref/Instrument.md
+25-16Lines changed: 25 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,12 +15,14 @@ Notes:
15
15
- Not all applications will use the same instrument identifiers, which is why FDC3 allows for multiple to be specified.
16
16
In general, the more identifiers an application can provide, the easier it will be to achieve interoperability.
17
17
18
+
- The `market` map can be used to further specify the instrument and help achieve interoperability between disparate data sources. This is especially useful when using an `id` field that is not globally unique.
19
+
18
20
- It is valid to include extra properties and metadata as part of the instrument payload, but the minimum requirement
19
21
is for at least one instrument identifier to be provided.
20
22
21
-
- Try to only use instrument identifiers as intended. E.g. the `ticker` property is meant for stock tickers specifically,
22
-
if the identifier you want to share is not a stock ticker, or one of the other standardised ones, rather define
23
-
a property that makes it clear what value it is. This makes it easier for target applications.
23
+
- Try to only use instrument identifiers as intended. E.g. the `ticker` property is meant for tickers as used by an exhange.
24
+
If the identifier you want to share is not a ticker or one of the other standardised fields, define
25
+
a property that makes it clear what value represents. Doing so will make interpretation easier for the developers of target applications.
-**ISO 3166-1**, _Codes for the representation of names of countries and their subdivisions – Part 1: Country codes_, [https://www.iso.org/iso-3166-country-codes.html].
13
13
-**ISO 8601-1:2019**, _Date and time — Representations for information interchange — Part 1: Basic rules_, [https://www.iso.org/standard/70907.html]
14
+
-**ISO 10383:2012**, _Securities and related financial instruments — Codes for exchanges and market identification (MIC)_, [https://www.iso.org/standard/61067.html]
14
15
-**JSON Schema**, [https://json-schema.org/].
15
16
-**OpenAPI Standard v3.0**, [https://www.openapis.org/].
16
17
-**RFC 2119**, _Keywords for use in RFCs to Indicate Requirement Levels, March 1997_, [https://datatracker.ietf.org/doc/html/rfc2119].
0 commit comments