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: Minutes for Code List Representation TC call 24 September 2021 14:00 UTC

Minutes for Code List Representation TC call
24 September 2021 - 9:00 MSP/10:00 Ottawa/14:00 UTC/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

Pres. Name Organization Status
(A) 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
(A) Ger Clancy IBM Persistent non-voting Member
(A) Jim Harris National Center for State Courts Member
(P) Ken Holman Crane Softwrights Ltd. Voting Member
(L) Natalie Muric Publications Office of the European Union Voting Member
(A) Levine Naidoo IBM Persistent non-voting Member

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

TC Members gaining voting rights after this meeting

TC Members losing voting rights
after this meeting

Review of last call minutes

In case the minutes cannot be approved during the meeting due to lack of quorum, they will be considered approved if no objection is raised during the meeting or received within 7 days from now.

Confirmation of Meeting Schedule

  • 2021-10-08: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
  • 2021-10-22: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
  • 2021-11-05: 10:00MSP/11:00Ottawa/15:00UTC/16:00Europe
  • 2021-11-19: 09:00MSP/10:00Ottawa/15:00UTC/16:00Europe
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
As recorded in the last minutes Ken posted genericode CSD04WD05 for internalreview and candidate for a public review:

Is CSD04WD05 acceptable to be distributed for public review?
In general, is anything missing or in need of correction?
Is the JSON transformation acceptable?
Are the examples in XML and JSON sufficient?
If acceptable CSD04WD05 will be marked as CSD04 and a Committee Ballot started to approve a public review. 

Agreed to proceed to public review, Ken will build genericode CSD04 (identical to CSD04WD05) and send a note to the mailing list. On that basis a ballot will be set up to approve starting the public review on CSD04.

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.

Other Business

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