[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes for Code List Representation TC call 7 October 2022 13:30 UTC
Minutes for Code List Representation TC call 06 October 2022 - 08:30MSP / 9:30Ottawa / 13:30UTC / 15:30 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
Presence legend (X): (P)=Present (A)=Absent (R)=Regrets (L)=Leave of absence TC Members gaining voting rights after this meeting None TC Members 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 ------------------------------------------------
Future meetings will keep the usual schedule but during DST change will keep fixed European local time. TC Deliverables planning ----------------------------------- The Code List Representation (genericode) Version 1.0 has been approved and published as OASIS Committee Specification 02. OASIS announcement: 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:
Here follows some information after an email exchange with OASIS Staff:
The steps involved in the submission to ISO:
During
the discussion at the previous meeting it was agreed among the experts
present that more information is needed to have an informed discussion
and have a basis to agree on the way forward. Possible alternatives are proposed in this post on the TC list for discussion: After the discussion it was agreed that the "short path" option (marked as number 1) is most pragmatic way forward. The steps foreseen are then the following ones: - progress genericode to be an OASIS standard - apply for the ISO PAS procedure, for example ISO/IEC JTC 1 (to be evaluated later) - then ISO ballot and eventual approval and publication (not an OASIS task) The TC agreed to start the process for the submission of genericode as a candidate for OASIS Standard, as specified in: In order to start the required Special Majority Vote to progress genericode three Statements of Use referencing genericode must be presented to the TC. Statement of use are specified here: Statement of use received so far:
A Statement of Use from NIEM Technical Architecture Committee (NTAC) was sent on September 29th but not present in the codelist mailing list - Andrea to check the reason. Andrea will check then if possible to start the procedure to progress genericode to become an OASIS Standard. All
the TC members, if using genericode or knowing any party using
genericode, are kindly asked to read carefully the requirements for a
statement of use referred above to facilitate the collection of eligible
statement by the TC to proceed as agreed. The
opportunity to submit genericode to ISO was agreed in principle but,
before progressing, a more clear justification is considered necessary. Its preparation will take place in parallel with the OASIS standards submission process. Genericode document editing ------------------------------------------ Genericode CS02 was published, no other editing is planned yet. No further editing is expected to submit genericode as a candidate for OASIS Standard. 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, 2021 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:
Other Business ---------------------- None |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]