codelist message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Minutes for Code List Representation TC call 10 September 2021 - 14:00 UTC (updated)
- From: Andrea Caccia <andrea.caccia.oasis@gmail.com>
- To: codelist@lists.oasis-open.org
- Date: Fri, 10 Sep 2021 17:22:29 +0200
Minutes for
Code List Representation TC call
10 September
2021 - 9:00 MSP/10:00 Ottawa/14:00 UTC/16:00 Central
Europe
http://www.timeanddate.com/worldclock/fixedtime.html?iso=2021-09-10T14:00:00
NOTE: this version
replaces document
https://lists.oasis-open.org/archives/codelist/202109/msg00003.html
and added text is marked in blue.
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) |
Jim Harris |
National
Center for State Courts |
Member |
(R) |
Ken Holman |
Crane
Softwrights Ltd. |
Voting Member |
(A) |
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
James changed employers however OASIS membership is
attached to the person, not the company, so he retains
voting rights standing even if they change employers
contrary to the minutes distributed previously, which
are therefore replaced by this version.
TC Members gaining voting
rights after this meeting
None
TC Members losing voting
rights after
this meeting
None
Review of last call minutes
https://lists.oasis-open.org/archives/codelist/202107/msg00012.html
The
minutes will be considered approved if no
objection will be received within 7 days
from now.
Confirmation
of Meeting Schedule
----------------------------------------------
- 2021-09-24:
09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
- 2021-10-08:
09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
- 2021-10-22:
09:00MSP/10:00Ottawa/14: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:
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
----------------------------------------
Ken volonteered to
continue dealing with Genericode document editing.
Ken posted genericode csd04wd04 then csd04wd05 for review.
Link to csd04wd05:
https://lists.oasis-open.org/archives/codelist/202109/msg00000.html
The document should be ready for public review, a decision
will be taken at the next meeting.
=====
We need to look into aligning the prose to ISO/IEC 15944-10
IT-enabled coded domains as semantic components in business
transactions.
Andrea and Ken volunteered for start taking care of this and make
proposals to the group.
Further discussion
on first attempt to put Genericode in scope of ISO/IEC 15944 and
Open-edi standards:
https://lists.oasis-open.org/archives/codelist/202104/msg00001.html
https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00003.html
Ken worked on alignment and posted for review
in CSD04WD02 working draft:
https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00013.html
See also for further information:
https://www.oasis-open.org/apps/org/workgroup/codelist/email/archives/202105/msg00011.html
JSON scheme
------------------
Erlend updated
the schema:
https://github.com/klakegg/genericode-schema
The group
discussed the examples in github and in particular it was
agreed that some refinements will improve the user
experience.
In the next weeks Ken and Erlend will further progress the
work.
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.
Other Business
-------------------
None.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]