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: RE: [codelist] Agenda for Code List Representation TC call 01 June 2022 13:30 UTC

Dear CLR TC members

The following Statement of Use is hereby submitted on behalf of the ECF TC:


The OASIS LegalXML Electronic Court Filing Technical Committee is using the is using the Code List Representation (genericode) Version 1.0 Committee Specification 02, dated 06 April 2022, in its preparation of ECF 4.1 in conformance with the conformance clauses listed in its section 4.


Logo, company name

Description automatically generated

Jim Cabral

Vice President, Court Relations


Visit the site | Check out the blog | Contact us



From: Andrea Caccia
Sent: Friday, July 1, 2022 10:15 AM
To: Jim Cabral
Subject: Re: [codelist] Agenda for Code List Representation TC call 01 June 2022 13:30 UTC


thanks for letting me know.

Today we decided to cancel the next 2 meetings for the summer break, in the meantime we are seeking for statements of use it was mentioned that the ECF TC and NIEM are using genericode and can be potential parties declaring the use of genericode, the nuance to consider is that the declaration refers to Committee Specification 02, dated 06 April 2022 so a work published before that date does not conform to the letter of the requirement. However if a new specification is under preparation it is fine, look for example to the statement we received from UBL:


Here follows a possible boilerplate for the statement.


Kind regards


The <name of the party> is using the Code List Representation (genericode) Version 1.0 Committee Specification 02, dated 06 April 2022, in its preparation of <name the project/activity using genericode> in conformance with the conformance clauses listed in its section 4.
Best regards,


Il giorno 1 lug 2022, alle ore 14:27, Jim Cabral <Jim.Cabral@infotrack.com> ha scritto:


I am away on leave today and am unable to join the call.



Jim Cabral


From: Andrea Caccia <andrea.caccia.oasis@gmail.com>
Sent: Friday, July 1, 2022 8:21 AM
To: Code List Representation TC
Subject: [codelist] Agenda for Code List Representation TC call 01 June 2022 13:30 UTC


Agenda for Code List Representation TC call
01 July 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:
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






Kenneth Bengtsson




Erlend Klakegg Bergheim

The Norwegian Agency for Public and Financial Management (DFO)

Voting Member


James Cabral

InfoTrack US

Voting Member


Andrea Caccia (chair)


Voting Member


Ger Clancy


Persistent non-voting Member


Pim van der Eijk

Sonnenglanz Consulting



Jim Harris

National Center for State Courts



Ken Holman

Crane Softwrights Ltd.

Voting Member


Natalie Muric

Publications Office of the European Union

Voting Member


Levine Naidoo


Persistent non-voting Member



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

TC Members possibly gaining voting rights after this meeting

TC Members possibly losing voting rights after this meeting

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-06-17: 08:30MSP/9:30Ottawa/13:30UTC/15:30Europe - cancelled
  • 2022-07-01: 08:30MSP/9:30Ottawa/13:30UTC/15:30Europe
  • 2022-07-15: 08:30MSP/9:30Ottawa/13:30UTC/15:30Europe - consider cancellation for summer break
  • 2022-08-12: 08:30MSP/9:30Ottawa/13:30UTC/15:30Europe - consider cancellation for summer break
  • 2022-08-26: 08:30MSP/9:30Ottawa/13:30UTC/15:30Europe


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:

  • 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
    • OASIS to remain the maintenance agency for the specification
    • any IPR issue

Here follows some information after an email exchange with OASIS Staff:

  • The document to be submitted to ISO has to be an OASIS Standard
  • It is confirmed that for the first submission it is possible to avoid to adapt the text to ISO and IEC Directives
  • If accepted by ISO:
    • genericode will be likely charged but will remain freely available from OASIS.
    • OASIS will remain the maintenance agency for the specification


The steps involved in the submission to ISO: 


The submission to ISO requires a strict sequence:

  • Committee Specification
  • OASIS Standard
  • 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:


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:
- 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, 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:

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