Minutes for Code List Representation TC call 04 November 2022 14:30 UTC

Minutes for Code List Representation TC call 04 November 2022 - 09:30MSP / 10:30Ottawa / 14:30UTC / 15:30 Central Europe https://www.timeanddate.com/worldclock/fixedtime.html?iso=2022-11-04T14: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 (A) Kenneth Bengtsson Individual Member (A) 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 (A) Ger Clancy IBM Persistent non-voting Member (A) Pim van der Eijk Sonnenglanz Consulting Member (P) Jim Harris National Center for State Courts Voting Member (P) Ken Holman Crane Softwrights Ltd. Voting Member (P) Natalie Muric Publications Office of the European Union Voting Member (A) Levine Naidoo IBM Persistent non-voting Member Presence legend (X): (P)=Present (A)=Absent (R)=Regrets (L)=Leave of absence TC Members possibly gaining voting rights after this meeting None TC Members  possibly   losing voting rights  after this  meeting None   Review of last call minutes https://lists.oasis-open.org/archives/codelist/202210/msg00002.html Minutes approved. Confirmation of Meeting Schedule ------------------------------------------------ 2022-11-04:  09:30MSP/10:30Ottawa/14:30UTC /15:30Europe (this meeting) The TC has agreed to keep the following schedule if there is a need to meet. 2022-11-18: 08:30MSP/09:30Ottawa/14:30UTC/15:30Europe 2022-12-02: 08:30MSP/09:30Ottawa/14:30UTC/15:30Europe 2022-12-16: 08:30MSP/09:30Ottawa/14:30UTC/15:30Europe TC Deliverables planning ----------------------------------- The Code List Representation (genericode) Version 1.0 has been approved and published as OASIS Committee Specification 02. OASIS announcement: https://lists.oasis-open.org/archives/codelist/202204/msg00003.html Further discussion is needed for possible future work including for instance further improvements and/or adapt genericode for submission to ISO. Progression to ISO requires: adaptations needed on the text to adapt it to ISO and IEC Directives clear understanding on implications, such as: the consequences in terms of free availability OASIS to remain the maintenance agency for the specification any IPR issue 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 steps involved in the submission to ISO:  https://www.oasis-open.org/policies-guidelines/liaison/#submitwork The submission to ISO requires a strict sequence: Committee Specification OASIS Standard Submission to ISO The TC agreed the following steps: - progress genericode to be an OASIS standard - apply for the ISO PAS procedure, for example ISO/IEC JTC 1 (to be evaluated later) - then ISO ballot and eventual approval and publication (not an OASIS task) The TC agreed to start the process for the submission of genericode as a candidate for OASIS Standard, as specified in: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OASISstandard In order to start the required Special Majority Vote to progress genericode  three Statements of Use  referencing genericode must be presented to the TC. Statement of use are specified here: https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22/#dStatementUse Statement of use received so far: UBL TC:  https://lists.oasis-open.org/archives/codelist/202206/msg00002.html ECF TC:  https://lists.oasis-open.org/archives/codelist/202207/msg00004.html   NIEM Technical Architecture Committee (NTAC):  https://lists.oasis-open.org/archives/codelist-comment/202211/msg00000.html   The required minimum number of 3 Statement of Use have been received, submission of genericode CS02 as a candidate for OASIS Standard is then possible. Other statement of use are in any case welcome. The following motion is proposed for approval by simple majority to TC members: The OASIS CLR TC approves the Chair requesting that TC Administration holds a Special Majority Vote to approve submitting Genericode v1.0 Committee Specification 02 at https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.xml  as a Candidate OASIS Standard. Ken seconded the motion. The CRL TC approves unanimously the motion. The opportunity to submit genericode to ISO was agreed in principle but, before progressing, a more clear justification is considered necessary. Its preparation will take place in parallel with the OASIS standards submission process . Genericode document editing ----------- ------------------------------- Genericode CS02 was published, no other editing is planned yet. No further editing is expected to submit genericode as a candidate for OASIS Standard.  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/ 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