csd03 progression readiness

When:  Apr 11, 2024 from 08:00 to 10:00 (UTC)



Review outstanding 2nd public review Issues and PRs


Decide on csd03 progression

Adjourn no later than 1000 UTC




Miloš, John, Simon, dF, Vojta, Michal 

6/6 voters


Extensive discussion of #72

The consensus seems to be tending to option 3 light

Headword is not extensible, except with inline

Is property of entry and a normalized string, hence protected from harmful extensibility

It can get metadata through siblings

Transcription is an object, child of pronunciation not extensible, except with inline


Everywhere the model has a text property, XML has to implement <text>


Definition gets full option 3 treatment (it is fully extensible)

Transcription gets full option 3 treatment

Anything else that doesn’t have the text property in the object model atm will be left w/o the text property/element and effectively not extensible

Extensive discussion of PR #111

Discussion of uniqueness

What is the uniqueness criterion in the Etymology module?

We agreed to add a clarification of uniqueness

Miloš to implement in the spec [encode key MUST, MAY, etc. key words properly]

Agreed meeting times:

  • Working meeting on 18th April 0800-0900 UTC

[dF regrets to be chaired by Michal, will not count towards voters eligibility]

Main objective is to merge pending PRs

Continue review and issue resolution via GitHub

  • Csd03 progression meeting on 20th May 1600-1700 UTC


Online Instructions:
Url: http://uni-lj-si.zoom.us/
Login: https://groups.oasis-open.org/higherlogic/ws/groups/0fd41fbb-72be-4771-8faf-018dc7d3f419/action_item?action_item_id=3946