- From: Fahad Khan <anasfkhan81@gmail.com>
- Date: Tue, 4 Nov 2025 11:53:15 +0100
- To: "John P. McCrae" <john.mccrae@insight-centre.org>
- Cc: public-ontolex <public-ontolex@w3.org>
- Message-ID: <CAK+N+9giSRz2fJjRTus8G614ursHHk+RauDi==twZfkSNhdWxA@mail.gmail.com>
Dear John, IMHO the definition of Entry is too narrow (it is tied to a lexicographic source) and entails quite a complex encoding with the existence and alignment of different structural components and lexical components just to capture, e.g., the case of part of speech values associated with different senses (think of all the overhead in the case of a lexicon where this is common and the difficulty of writing SPARQL queries). The question isn't just one of providing a solution but a good one. For instance, I think David's solution of language specific categories might make interoperability between different resources more difficult and lead to a profusion of PoS categories. From what I understand the necessity of having a single part of speech per entry was a necessity for certain NLP tasks, but nowadays the creation of lexicons for language documentation/retrodigitsation is a much more frequent use case in LLOD. I think it makes sense to get rid of it. Cheers, Fahad Il giorno lun 3 nov 2025 alle ore 17:16 John P. McCrae < john.mccrae@insight-centre.org> ha scritto: > Hi all, > > As part of the OntoLex core model changes we are looking into the issues > of multiple part-of-speech values here: > > https://github.com/ontolex/ontolex/issues/47 > > In particular, this problem already appears to be solved by the use of the > `Entry` class from `lexicog` or as David Lindemann suggests by using more > general or language-specific categories. > > I was wondering if there are any use cases that anyone has that are not > solved by this modelling, or other comments > > Regards, > John > > PS. I will copy/summarize replies to this email to GitHub. You may also > post directly to GitHub. >
Received on Tuesday, 4 November 2025 10:53:32 UTC