Hi Ken,
thank you for letting us know, this reflects an international use of genericode as Peppol as, to my knowledge, at least Australia and Singapore are members.
This also is an example of requirement to have also a JSON representation.
Another source is the European Commission that, for the European electronic invoice standard, publishes a number of code lists, including a genericode representation for the version that is applicable from tomorrow May 17th:
https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Registry+of+supporting+artefacts+to+implement+EN16931#RegistryofsupportingartefactstoimplementEN16931-Codelists
The EAS.gc code list published by CEF that is based on ISO/IEC 6523 ICD. The Country.gc is a genericode representation of ISO 3166 country codes.
I did not check but there could be other code lists based on ISO standards.
This means that potential genericode users in this context are:
- ISO and/or IEC committees that - then drafting RA standards (i.e. standards reequiring a registration authority like ISO/IEC 6523) can include a genericode representation as machine processable representation of the code list to be published by the RA. This is also possible of course for other SDOs, for instance CEN and CENELEC have rules similar to the ISO ones.
- any RA, working on the basis of ISO, IEC or any other SDO as well
- any community that uses standard bases code lists where a standard machine readable format is not available, like the case of Peppol and CEF
Therefore targeting the publication of genericode as ISO standard makes a lot of sense to me.
Andrea
P.S. It was already mentioned that the EU Publication Office is publishing code lists using genericode (this is the first example found searching on the web, search for "genericode" here: https://espd.github.io/ESPD-EDM/v2.1.1/xml_guide.html). I am sure there are other examples outside Europe.
Il giorno 7 mag 2021, alle ore 19:22, G. Ken Holman <g.ken.holman@gmail.com> ha scritto:
Fellow CLRTC members,
Just this morning we were wondering about whether Peppol publishes its code lists in genericode.
Thirty minutes ago I discovered that they do!
https://docs.peppol.eu/edelivery/codelists/
The correct spelling of "genericode" aside (note we've always used lower-case "g" except at the start of a sentence), I'm glad to see it there!
A quick glance indicates they are using genericode properly and well.
Note that a version in JSON is available for each list.
One thing not mentioned at the meeting this morning is that we can lean on the argument that the tight binding JSON provides between application means that programmers will want to use their own JSON arrangement. If we stick to XML only, then projects can choose to publish in XML and have users convert the open standardized XML into bespoke JSON as they require for their application. What use is it publishing a committee JSON format if programmers are going to rearrange it anyway for their bespoke use?
But that's just food for thought while we go through our identified task of getting industry feedback.
Have a good weekend!
. . . . . . Ken
--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/m/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @US$125 (5 hours free) |
Essays (UBL, XML, etc.) http://www.linkedin.com/today/author/gkholman |
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php