- From: Christian Chiarcos <christian.chiarcos@gmail.com>
- Date: Mon, 13 Mar 2023 13:28:35 +0100
- To: public-ontolex <public-ontolex@w3.org>
- Message-ID: <CAC1YGdihu=Wf1gtQg8uXE-6JobkZbz1r0Fk=g7yo6to9POrDWA@mail.gmail.com>
Dear all, im preparation of wrapping up the development of the OntoLex-Morph vocabulary, we decided at the last telco <https://docs.google.com/document/d/1iguZV9afJ-RrU7okJtYKLJ-cQ77MYba0srOVG8rlBpM/edit?usp=sharing> to *freeze the requirement elicitation* for OntoLex-Morph. This means that we will not accept the proposal of novel data sets or novel requirements *after a certain point in time* (see below). This does not imply freezing the vocabulary, so things may get renamed or restructured, but only if a dataset previously discussed in an OntoLex-Morph meeting requires it or the requirement has been recorded in wiki or minutes <https://www.w3.org/community/ontolex/wiki/Morphology>, or as GitHub issue <https://github.com/ontolex/morph/issues> before that date. We consider this necessary as a step to prepare finalization, and to synchronize the current diagram ( https://github.com/ontolex/morph/tree/master/doc/diagrams) with the latest draft (outdated, under https://github.com/ontolex/morph/blob/master/draft.md), publications (https://aclanthology.org/2022.ldl-1.10/, almost up to date, but very brief) and discussions (in the minutes). That is, all OntoLex contributors are hereby asked to either - raise objections against this decision (e.g., if you have a data set in preparation that you consider a game changer for current modelling decisions), or to - propose new data or new requirements *until March 21, 2023* Everyone is cordially invited to the regular meeting on March 22, 2023 (13-14:00 CET, see minutes/agenda document linked from the Wiki <https://www.w3.org/community/ontolex/wiki/Morphology>), where we will discuss the responses. It is possible that we will implement a transition period if requested, but unless decided so on March 22, we will freeze the requirement elicitation as of that day. The next step is then to track and address the remaining requirements and data samples and to implement a *feature freeze* as soon as possible. Best regards, Christian
Received on Monday, 13 March 2023 12:28:59 UTC