Minutes for Code List Representation TC call 17 February 2023 14:30 UTC

Minutes for Code List Representation TC call
17 February 2023 - 08:30MSP / 9:30Ottawa / 14:30UTC / 15:30 Central Europe
https://www.timeanddate.com/worldclock/fixedtime.html?iso=2023-02-17T14:30:00
Conferencing info

-------------------------

Meeting ID: 878 5955 1232  Join from PC, Mac, Linux, iOS or Android:  https://us02web.zoom.us/j/87859551232  Password is needed and sent separately, if you do not have it please send an email to the chair
TC Members presence and status at this meeting
See  https://www.oasis-open.org/committees/membership.php?wg_abbrev=codelist
Pres.
Name
Organization
Status
(X)
Kenneth Bengtsson
Individual
Member
(P)
Erlend Klakegg Bergheim
The Norwegian Agency for Public and Financial Management (DFO)

Voting Member
(P)
James Cabral
InfoTrack US
Voting Member
(P)
Andrea Caccia (chair)

Individual
Voting Member
(X)
Ger Clancy
IBM
Persistent non-voting Member
(X)
Pim van der Eijk
Sonnenglanz Consulting
Member
(X)
Jim Harris
National Center for State Courts
Voting Member
(P)
Ken Holman
Crane Softwrights Ltd.
Voting Member
(R)
Natalie Muric
Publications Office of the European Union
Voting Member
(X)
Levine Naidoo
IBM
Persistent non-voting Member
Presence legend (X): (P)=Present (A)=Absent (R)=Regrets (L)=Leave of absence
TC Members gaining voting rights after this meeting
None
TC Members

losing voting rights
after this
meeting
Jim

Review of last call minutes
https://lists.oasis-open.org/archives/codelist/202302/msg00008.html
minutes approved.
Confirmation of Meeting Schedule

------------------------------------------------

2023-02-17: 08:30MSP/09:30Ottawa/14:30UTC/15:30Europe (this meeting)  2023-03-03: 08:30MSP/09:30Ottawa/14:30UTC/15:30Europe
TC Deliverables planning

-----------------------------------

The  Code List Representation (genericode)

Version 1.0 has been approved as OASIS Standard. OASIS announcement:
https://www.oasis-open.org/2023/02/01/genericode-approved-as-an-oasis-standard/
The TC is extremely grateful and sincerely thanks Ken for his hard work as editor, which made it possible for genericode to become an OASIS Standard, and for the enormous work he has done since the committee was established.
Possible progression to ISO of genericode
Here follows some information after an email exchange with OASIS Staff:
The document to be submitted to ISO has to be an OASIS Standard  It is confirmed that for the first submission it is possible to avoid to adapt the text to ISO and IEC Directives  If accepted by ISO:
genericode will be likely charged but will remain freely available from OASIS.  OASIS will remain the maintenance agency for the specification
The TC is collecting examples of international use of genericode in support of submission to ISO.  Electronic Court Filing and NIEM were added to the list.  TC members are invited to provide any information available.
The steps involved in the submission to ISO:
https://www.oasis-open.org/policies-guidelines/liaison/#submitwork
Summary of main steps:
draft a terms of submission document  hold a Special Majority Vote to approve requesting OASIS to make the submission  if approved, OASIS TC Admin to start 30 day notice to the membership  OASIS  President (within 15 days) to either return the terms to the TC with a  request for changes or  announce to the membership that we will be  making the submission and move forward
Genericode document editing

-----------

-------------------------------

Code List Representation (genericode)

Version 1.0 OASIS Standard is published.
Announcement on the list:
https://lists.oasis-open.org/archives/codelist/202302/msg00011.html
Use or potential use of Genericode

---------------------------------

---
---  ---
---
-    A question was raised to check about interest on having JSON serialization of genericode. Possible users to reach: - ISO RAs - source authorities listed in the ICD list based on ISO/IEC 6523 - EU CEF
Use of Code lists by OpenPEPPOL was spotted by Ken:  https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00006.html  They publish code lists both in XML and JSON and also using genericode.  Use of genericode by the European Commission was identified with electronic invoicing:  https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00007.html
The EU Publication Office is using genericode:  https://op.europa.eu/en/web/eu-vocabularies/e-procurement/tables
The OASIS LegalXML Electronic Court Filing specifications v4 and v5 use genericode.  ECF v4 is widely adopted among US state courts.  http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/schema/
Electronic Court Filing Version 5.01  uses genericode
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.01/csd02/ecf-v5.01-csd02.html#_Toc105761872
NIEM Code Lists Specification  uses genericode
https://reference.niem.gov/niem/specification/code-lists/4.0.1/niem-code-lists-spec.html
Ken started a poll to gather input from potential stakeholders to investigate on use of JSON with Genericode:
https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00012.html
According to the results reported until June 14th, 2021 meeting minutes, JSON is used for internal use and not for publication. It  was also observed that any JSON serialization would not be able to  address XML features such as annotations and custom complex values in  columns.  The revision activities for ISO/IEC  6523 also started (ISO/IEC AWI 6523-1 and ISO/IEC AWI 6523-2) with  potential use of genericode can be foreseen for the publication of the  ICD list by the ISO/IEC 6523 RA.
New initiative  from the European Commission, proposed EU Regulation   on harmonised rules on fair access to and use of data   (Data Act)   with  the aim of ensuring fairness in the allocation of value from data among  actors in the data economy and to foster access to and use of data  (see:  https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=COM:2022:68:FIN
).
In   particular:
Recital 79:   Reusable  data structures and models (in form of core  vocabularies), ontologies, metadata application profile, reference data  in the form of core vocabulary, taxonomies,  code lists , authority tables, thesauri  should also be part of the technical specifications for semantic interoperability .
Article 28 -   Essential     requirements regarding interoperability
1.  Operators  of data spaces shall comply with, the following essential requirements  to facilitate interoperability of data, data sharing mechanisms and  services:
...
(b) the data structures, data formats, vocabularies, classification schemes, taxonomies and  code lists  shall be described in a publicly available and consistent manner
Other Business

------------------

----
None