FpML Issues Tracker
closed
Minor
Always
Architecture
hpegeron
andrew
Summary
FpML has been supporting a list of scheme values in the codelist format online. The proposal would be to keep the most recent version of each coding-scheme in a canonicalized URL pointing to an XML file.
The most recent version of any one scheme could then be referenced by the cononicalized URL and XML file.
Example: http://www.fpml.org/coding-scheme/business-center-6-1 is the most recent version of the businessCenterScheme as of Feb 05 2007 and http://www.fpml.org/coding-scheme/business-center-6-1.xml currently has the specific values for 6-1.
http://www.fpml.org/coding-scheme/business-center.xml could provide these same values, to be later replaced by the next version of the scheme. This would allow an implementation to simply reference http://www.fpml.org/coding-scheme/business-center.
Notes:
mgratacos
06/04/07 8:09 am
This was discussed in the AWG. Henri will put together a technical note.
matthew
06/05/07 1:31 pm
This paper is premised on a misunderstanding. The latest codelists is released with a release for convenience, but are not versioned along with the releases. You cannot associate a codelist to a release. However the underlying problem remains, which needs fixing.
I suggest a codelist is given a domain of applicability which is a time-window in which the values could be used.
For example code FRF was valid until EUR came along. There should be a new version of the currency code list along with the euro introduction. (This is what ISO does).
One solution is there is merely one code list, but the contents mark clearly the domain of applicability for each code.
matthew
06/07/07 2:33 pm
There was consensus at the AWG on 2007-06-07 that:
1. URIs should not be decomposed. They should be treated as pure names.
2. There is no concept of ‘versions’ of a scheme. Each coding scheme is unique and not a version of another.
3. Any change to the coding scheme is a new URI.
mgratacos
08/19/07 2:09 pm
Andrew Jacobs will convert Henri’s proposal into a technical paper.
mgratacos
05/15/08 1:25 pm
See attached Canonical Schemes.doc paper.
mgratacos
08/27/08 12:10 am
Separation of schemes from the full spec has been implemented in the trunk. It will be public with the publication of the first working draft for version 4.5.