6.2.3 This is not sufficient to individuate the financial instrument,
however, as organizations issue financial instruments with exactly the same name but that trade on different exchanges.
This is a distinction that is absent in other identifiers, but serves as an individuating characteristic for FIGI.If FIGI is used a the master key in a reference database inconsistencies arise "

I do ot believe the FIGI implementation adheres to this - namely

1) All preferred's on North American Exchanges have the same FIGI yet these a discrete tradeabe instruments on different exchanges , exactly like cash equities
EP053763@SYBT Pfd
EP053763@SBOX Pfd,

2) Multiple FIGI's can exist for the same Index Instrument
Original Alternative
M00IEF$O M1EFMVOL
MMDLESU MXEUGMC
M3DE MSDUGR

3) BBG create duplicate futures for option series , these all have different FIGI yet they link to the same instrument
EDZ1 Comdty GEZ1 Comdty

FIGI is not aligned to unique instrument identifiers

This is an issue with the implementation of FIGI, not the specification itself. The Registration Authority is researching the issues and will work towards a solution. This requires no changes to the specification.

This issue represents specification modifications that are editorial in nature only, and that correspond to the changes made when this specification was promoted for standardization through ANSI X9.

The goal with this revision (FIGI 1.1) is to update the standard to match precisely what ANSI published, with no other changes included.

See the attached MS Word document for the changes, using track changes.

Revise the FIGI specification to reflect the revisions made by ANSI X9

The attached document includes change barred revisions that correspond to those made for the ANSI X9 publication. These revisions should be made to the FIGI specification for publication as the FIGI 1.1 specification.

Additional editorial updates, such as dates, footers, document numbers and copyright details will be made to the convenience document(s) submitted with the RTF report, but no other changes will be included in this update.

Currently, the FIGI ontologies use the specification metadata, which, although it is still used to manage the online catalog, is no longer used for ontology documentation. Instead, all new submissions are using the Commons Annotation Vocabulary, which is a formal OMG standard rather than an internal file.

The ontologies and metadata files for FIGI should be updated accordingly.

Revise the FIGI ontologies to use the Commons Annotation vocabulary

This work is planned for the FIGI 1.2 revision task force. The FIGI 1.1 RTF is limited to those changes made for promotion with ANSI X9.