FpML Issues Tracker

1220: Canonical Scheme URIs for Instrument Id

February 19, 2016

closed

Tweak

Always

Coding Scheme

andrew

mgratacos

Summary

None of the URIs for ISIN, CUSIP etc have a canonical form with no version number. I don't think it really mades sense to have a version number on a scheme that we do not control and which is changed on a regular basis.

We should add a canonical URI to all the legacy external schemes which still follow this pattern (e.g. RED, MIC, etc).

This change would only affect the documentation. There should be no schema impact.

Notes:

  • mgratacos

    01/18/18 11:20 am

    The current Architecture Specification 3.1 identifies this type of URI but it doesn’t say anything regarding versioning. Actually the example used by the specification is versioned:

    The URI for a scheme can be categorized as one of the following:

    • An external coding scheme, which has a well-known URI. In this case the URI is assigned by an external body, and may or may not have its own versioning and date syntax or semantics. The external body may be an open standards organization, or it may be a market participant.

    We should discuss this at the next AWG.

  • mgratacos

    01/25/18 10:38 am

    AWG 2018-01-25

    • Agreement to remove the version from the external schemes’ URI in the next new version, not in 5.10.

  • mgratacos

    07/16/18 4:51 pm

    Version number has been removed from the instrument id coding scheme URIs:

     

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue