OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

lexidma message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [lexidma] Working draft

We have no way to represent fine-grained morphosyntactic information, including gender of nouns and categories of inflections. For example the annotation on this entry and its inflected form âboiseâ

For gender (and other properties) of nouns (and other word classes) the idea is that implementers would conflate them with part-of-speech labels: they would create a âmasculine nounâ part-of-speech label, a âfeminine nounâ part-of-speech label, and so on.

For inflection categories, for example to say that this noun belongs in such-and-such inflectional paradigm, there my suggestion would again be to conflate this with the part-of-speech label, for example âfeminine noun of the second declensionâ.

Note that in DMLex, implementers can use the Controlled Vocabularies module to tell the world what their home-baked part-of-speech labels map to in some external data category ontology, for example to LexInfo.

For inflected forms, thatâs what the InflectedForm object type is for (but no tildas please).

We cannot give citations for sources of information, as is typical in historical dictionaries (see image)

True. This would be a good candidate for a module.

There is no etymology information (as discussed in the call). See example in Merriam-Webster:

True again, and again itâs a candidate for a module.

I am not sure how we intend to implement collocations (see example in FoclÃir Gaeilge-BÃarla)

My idea was that each collocation would be treated as an entry (with the full-form collocation as its headword, for example âlÃn boiseâ), and this entry would be connected to its âmotherâ entry through SubentryRelation.

To my mind, this is the only reasonable way to handle collocations if we want to avoid embedded subentries and headword overriding (see my report on subentrying earlier in Lexidma and also my presentation on recursion at eLex recently).

No modelling for hypernym relations

I was thinking most lexicographers would be happy enough to model hypernymy and hyponymy through SimilarityRelation in the Crossreferencing module. But, by all means, feel free to propose a more detailed inventory of relation types for this module if you want.

On a general note, Iâm sure people from both inside and outside Lexidma will have a lot of questions like these; how do I handle nound gender in DMLex, how do I handle collocations in DMLex, and so on. The standard itself is probably not the right place to answer them. So, perhaps we should think about producing some sort of a âcookbookâ to go with the standard as an additional, less formal guide to implementing DMLex.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]