[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ubl-lcsc] Codelist listID, etc
Hi
I don't have posting access to CLSC so please would someone forward this to their list too.
Thanks.
In preparing the updated sample instances for draft 3 with a new RT Schema (as previously posted) I've found that it is now possible to add the code supplementary components, e.g. <cbt:PaymentMeansTypeCode listID="UNTDID-TRED-4451"
listVersionID="D03A"
listAgencyName="UNECE">ZZZ</cbt:PaymentMeansTypeCode>
In this example I have used for listID the ID value format I found in some old CBL archives
"UNTDID-TRED-4451".
Do we agree (or need to agree) on this format?
This could equally have been "tred4451", "tred 4451", "TRED-4451", etc. Do we not need a controlled vocabulary or
guidelines for
expressing such values?
I was nervous about adding a listAgencyID because it is yet another ID or Code needing a controlled vocabulary (or highly specialised knowledge of existing standards) or code list (perhaps the CC folk should have called these things listAgencyCode, etc and provided codelists). But a second reason was that I could not easily find a list of these agency ID's, merely anecdotal evidence that the ID for ISO is '6'. Tim, we really should, I think, define all these in the Codelist Catalogue for all the codes we wish people to use, at least. Please note my updated Codelist Catalogue version 1 draft 3 in the latest model posted for these further edits. All the best
Stephen Green
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]