The Global Technical Committee has reviewed and preliminarily approved the Gap Analysis submitted by Deutsche Börse Group. This gap analysis proposal seeks to address a gap in the FIX Protocol related to the unique identification of derivative instruments where the core reference data attributes are not sufficient. An additional, generic attribute SecurityReferenceDataKey (name is still subject to review and may change) may be used in conjunction with other functional attributes for disambiguation. It is not intended to be used standalone or as an alternative for Symbol(55) or SecurityID(48).
The document now enters a public comment period in which public review and feedback is encouraged. Once the public comment period closes, the GTC will review public comments before final approval by the GTC Governance Board.
Please post feedback, comments, and questions as replies to this discussion thread. The public comment period ends on November 8, 2022.
@christophjohn it’s actually two difference things. The proposed new field (we still need a better name actually - not keen on the term “key” either so this is a placeholder) is about some other characteristic of the security that is needed to disambiguate it for trading reasons. The characteristics used might not be an “ID” in the classic sense - I rather not see the term “ID” used in this case.
The tag 2390 you referenced, that really is an ID and it meant to carry an identifier.
@christophjohn, we will now be proposing to use the term “supplement” instead of “key”. It is important to avoid the notion of the new field being available as sole field for the identification of a security. SecurityReferenceDataSupplement expresses the fact that it is intended to go along with multiple other fields that provide the uniqueness.
This thread is now being closed for public comments.
