Agenda for Code List Representation TC call 11 March 2022 - 9:00MSP/10:00Ottawa/15: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
|
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
|
Member
|
(X)
|
Jim Harris
|
National Center
for State Courts
|
Member
|
(X)
|
Ken Holman
|
Crane
Softwrights Ltd.
|
Voting
Member
|
(X)
|
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 Erlend, James, Natalie
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
------------------------------------------------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:
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 ------------------------------------------
The public review on CSD04 closed on Dec 4th. One comment has been submitted: Ticket:
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:
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.htmlNo comment received so far.
Important items for this meeting ----------------------------------------------
Requirements to proceed with the approval of genericode as a Committee Specification: - the TC is temporarly 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
- confirm 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.
Therefore we require at least 2 meetings before approving the request to start the Special Majority Vote to allow at least one TC Member to gain voting rights.
The following questions are asked to all the attendees of todayâs meeting: - do you agree that the ticket https://issues.oasis-open.org/browse/CODELIST-1 resolves the issue raised during the public review on genericode CSD04?
- do you agree that CSD05 does not introduce material changes if compared with CSD04?
- do you have any comment on CSD05 to be considered before requesting a Special Majority Vote to approve CSD05 as Committee Specification
The meeting will be opened 5 minutes before the scheduled time and kept open at least 10 minutes past the scheduled opening time (or up to the scheduled closing time if required for the discussion). In case you cannot attend please be prepared to provide your position or abstention on the questions. Attendance is needed to ensure the TC can comply with the âMinimum Membershipâ requirement
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 |
|