OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

codelist message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Agenda for Code List Representation TC call 11 March 2022 15:00 UTC

Agenda for Code List Representation TC call
25 March 2022 - 10:00MSP/11:00Ottawa/15:00UTC/16:00 Central Europe

Conferencing info
Meeting ID: 878 5955 1232

Join from PC, Mac, Linux, iOS or Android:
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






Kenneth Bengtsson




Erlend Klakegg Bergheim

The Norwegian Agency for Public and Financial Management (DFO)

Voting Member


James Cabral

InfoTrack US

Voting Member


Andrea Caccia (chair)


Voting Member


Ger Clancy


Persistent non-voting Member


Pim van der Eijk

Sonnenglanz Consulting



Jim Harris

National Center for State Courts



Ken Holman

Crane Softwrights Ltd.

Voting Member


Natalie Muric

Publications Office of the European Union



Levine Naidoo


Persistent non-voting Member

Presence legend (X):
(L)=Leave of absence

TC Members possibly gaining voting rights after this meeting
Kenneth, Pim, Jim, Natalie

TC Members possibly losing voting rights
after this meeting

Review of last call minutes
in case minutes could not be approved during the meeting due to lack of quorum, they will be considered approved if no objection is received within 7 days from now.

Confirmation of Meeting Schedule
  • 2022-04-08: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
  • 2022-04-22: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
    2022-05-06: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
Please note highlighted the changes in future meetings taking into account different DST

TC Deliverables planning
Agreed that we first should focus on the first two deliverables:
- a semantic model / meta-model of genericode
- an XML serialization of the genericode semantic model, with the intent of backward compatibility (or even no changes) to the existing genericode
We need to look into how to express the semantic model of the existing markup vocabulary. What technologies should we look at and use?
Further discussion is needed.

Semantic model / meta-model
James volunteered for start looking into the  "semantic model / meta-model of genericode" topic and assessing if the fit of the metamodel to current Genericode specification.
The NIEM metamodel should be analysed,
Git repository:
Proposed extensions to the NIEM metamodel to support genericode features such as multiple columns and keys with mocked up example based on nc:LanguageCode that introduces 3 new elements to the NIEM metamodel, for discussion:

Ken observed the following about the metamodel in light of the work being done in JSON:
- it may be premature to continue work on the metamodel until we determine its utility in light of our earlier decision on JSON
- earlier it was decided that the JSON syntax is only a demonstration subset of genericode so that users can tailor the JSON to their own needs
- if we aren't going to create the entire genericode in JSON, what is the use of a metamodel?
- already proposals are made to have different names in the JSON than in the XSD, so what would we have to do in the metamodel to identify semantics that are labeled differently in the two syntaxes
- Ken proposed to suspend the metamodel preserving the work done so far and put our efforts into a parallel subset JSON and other responsibilities on the project
This was agreed at the 30 July 2021 meeting.

Genericode document editing

The public review on CSD04 closed on Dec 4th.
One comment has been submitted:

Discussion on received comment:
  • Agreed that it is useful to provide guidance on the lifecycle of codes
  • Guidance should not be prescriptive to allow the standard to remain as general as possible
  • An informative annex seems the best solution to accomodate this guidance
  • Examples would be very useful, members of the TC are asked to provide possible candidates, for example Natalie and Jim may be able to provide real life use cases
  • The annex could encourage custodians of code lists to include lifecycle information

Examples were posted and a discussion followed, see:

Agreed to keep the annex as proposed by Ken (see https://lists.oasis-open.org/archives/codelist/202201/msg00002.html) with a minor editorial change as agreed already on mailing list discussion.
Ken incorporated the Annex in  CSD05WD01-20220202-2113z for discussion:
Agreed to change the last sentence to "Therefore, this specification does not attempt..."

Agreed to include some excerpt of real life use of genericode with lifecycle clarifying they are only examples, TC members are asked to provide material for this.
No suitable example was posted and it was agreed not to insert examples in the specification.

Ken prepared CSD05: https://lists.oasis-open.org/archives/codelist/202203/msg00000.html
No comment received so far.

Requirements for the approval process

Requirements to proceed with the approval of genericode as a Committee Specification:
  • the TC is temporarily non compliant with the "Minimum Membership" requirement from OASIS to have at least 5 voting members, the TC needs to comply before the Special Majority Vote can start
  • The TC has confirmed that the issue raised during the public review was correctly addressed and resolved and approve the closure of the ticket https://issues.oasis-open.org/browse/CODELIST-1
  • The TC has confirmed that there are noi additional comments on CSD05 and that it does not introduce material changes if compared with CSD04 that has a public review.  

Motion proposed by Andrea:

Does the TC approve by simple majority that the Chair request that TC Administration hold a Special Majority Vote to approve Code List Representation (genericode) Version 1.0 Committee Specification Draft 05 contained in:
as a Committee Specification subject to any editing necessary for its publication?

As documented in https://lists.oasis-open.org/archives/codelist/202203/msg00004.html the TC affirms that the changes made since the last public review are documented in https://issues.oasis-open.org/browse/CODELIST-1 and the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange).

Use or potential use of Genericode
A question was raised to check about interest on having JSON serialization of genericode.
Possible users to reach:
- source authorities listed in the ICD list based on ISO/IEC 6523

Use of Code lists by OpenPEPPOL was spotted by Ken:
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:

The EU Publication Office is using genericode:

The OASIS LegalXML Electronic Court Filing specifications v4 and v5 use genericode.
ECF v4 is widely adopted among US state courts.

Ken started a poll to gather input from potential stakeholders to investigate on use of JSON with Genericode:

According to the results reported until June 14th 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
As come forward

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]