- From: Jorge Gracia del Río <jogracia@unizar.es>
- Date: Mon, 28 Jul 2025 08:00:00 +0100
- To: public-ontolex <public-ontolex@w3.org>
- Message-ID: <CAMe8T+sTSC7RSMT7m2nXLJk09AhRGUezdqP=N_NgGcehX4VPfQ@mail.gmail.com>
Dear Ontolex CG members, This email is to inform about some recent progress towards an Ontolex v2 specification. Recently, John McCrae and myself met at University of Galway and did an extensive review of the open issues and requirements, in preparation for the next community group meeting that will take place in September. This is a summary: - We merged all the requirements (terminology, lexicography, ...) in a single list and assigned unique identifiers. See https://github.com/ontolex/ontolex/blob/master/notes/requirements_all.md - We opened issues for all the requirements and added comments with possible ways to address them. Some of them contain code examples. Please go through them and feel free to complete with further ideas or examples. All this info will serve as a basis for discussion in our next plenary meeting in September. You can find the list of issues for this release at https://github.com/ontolex/ontolex/milestone/1 - We discussed the possibility of keeping the lexicog <https://www.w3.org/2019/09/lexicog/> module: (i) as it is, or (ii) partially merge it into the core of ontolex (i.e., moving the 'restrictedTo' and 'usage Example' properties into the ontolex namespace), or (iii) completely move it into ontolex core (all the classes and properties). Maybe you need more time and reflection to support one idea or another, but if you already have an opinion, you can express it by voting through this issue <https://github.com/ontolex/ontolex/issues/62> - Also, please start thinking on the pros/cons of having all the modules described in a single specification document (that includes frac and morph) or in separate ones. We can take a decision on this also in the next plenary Best regards, Jorge Gracia W3C Ontolex CG co-chair
Received on Monday, 28 July 2025 07:00:31 UTC