These include relevant patterns for designations and identifiers, among others.

Note that the resolution to this issue depends on the resolution to FIGI12-2.

Revise the FIGI ontologies to be compatible with the patterns in Commons

The changes, which depend on prior application of the changes made in the resolution to FIGI 1.2-2, primarily impact the primary Global Instruments Ontology and related documentation. They require the use of Commons ontologies: Codes and Code Sets, Classifiers, Identifiers, and TextDatatype. Local constructs that are replaced will be deprecated and will reference the Commons equivalents, in order to maintain backwards compatibility for FIGI users.

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 rather than Specification Metadata

The resolution to this issue mainly affects the 3 FIGI ontologies, but there are a few places, mainly in tables, where corresponding changes are needed in the specification.

Some of the related text was revised via the 1.1 revision to the specification, and through issues raised in 1.2. The definitions and annotations in the FIGI ontology should be updated so that they are ISO 704 compliant and to reflect the updated details in the FIGI 1.1+ issues.

Deferred to 1.3 RTF

Deferred due to the need to publish the ANSI compatible version

The current list is unstructured and unanchored to any recognized classification scheme - there's no way to even review it.
Further it misses crypto assets now in scope for FIGI.
No information is given about each of the types besides their name, not even an external reference - hardly semantic!
Ideally there should be a link to FIBO or similar, without requiring FIBO compliance.

Some of the related text was revised via the 1.1 revision to the specification, and through issues raised in 1.2. The definitions and annotations in the FIGI ontology should be updated so that they are ISO 704 compliant and to reflect the updated details in the FIGI 1.1+ issues.

The list of sources is way out of date. A mechanism is needed for keeping them updated with the monthly-changing MIC codes.
FIBO already does this - they should share a mechanism if not a file.

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.