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 8 April 2022 14:00 UTC



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

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

Voting Member

(X)

Erlend Klakegg Bergheim

The Norwegian Agency for Public and Financial Management (DFO)

Voting Member

(X)

James Cabral

InfoTrack US

Voting Member

(X)

Andrea Caccia (chair)

Individual

Voting Member

(X)

Ger Clancy

IBM

Persistent non-voting Member

(X)

Pim van der Eijk

Sonnenglanz Consulting

Voting Member

(X)

Jim Harris

National Center for State Courts

Voting Member

(X)

Ken Holman

Crane Softwrights Ltd.

Voting Member

(L)

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 possibly gaining voting rights after this meeting
None

TC Members possibly losing voting rights
after this meeting

None
 
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-22: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
  • 2022-05-06: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
  • 2022-05-20: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
Change to DST has taken place in all affected countries

TC Deliverables planning
-----------------------------------
The ballot to approve Code List Representation (genericode) Version 1.0 with Non-Material Changes as a Committee Specification has passed:

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
    • future maintenance from OASIS
    • any IPR issue

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: 
https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00004.html
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: 
https://lists.oasis-open.org/archives/codelist/202106/msg00005.html

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
------------------------------------------
Genericode Version 1.0 has been approved as a Committee Specification and a ticket open by TC Admin:
Some editorial changes contingent to the publication process are needed and documented in the ticket. 


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 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]