Re: Open Issues in the Model

Am 10.10.2014 20:07, schrieb John P. McCrae:
> Hi all,
>
> I went through the model and noted that while I believe we are very 
> close there are still a number of open issues that we should look to 
> resolve:
John,
thanks for this! some of the points you mention were an issue for me as 
well. I am adding some few comments below.
>
> Core:
>
>   * In core there is now a 'SenseLexicon' class but no property to
>     relate it any other elements in the model
>
Can then instances of "LexicalSense" be member of a SenseLexicon (and 
not only refer to ontologies outside of the Ontolex model?
>
>   * We could/should consider using dct:language instead of
>     ontolex:languageURI
>
I am in favor of this move.
>
>   * We cannot give conditions when a Lexical Sense should apply (lemon
>     had a condition property for this)
>
Yes I had this issue as well (the reason why I as attempting to use 
"ontolex:denotes")
>
>   * It would be useful to indicate when a mapping is dependent on the
>     range or domain of a property (possibly)
>   * Should we add subclasses of LexicalEntry as follows Word,
>     MultiWordExpression, Affix?
>
Sounds reasonable to me.
> Syntax and Semantics
>
>   * There is no property to indicate the conjugation (morphological
>     pattern) of a word
>
True. I was missing this as well.
> Variation
>
>   * Lexical Variant is defined between either forms /or/ lexical
>     entries... there should be a class that is only for forms and a
>     class that is only for entries
>   * All variants are specified only in their 'reified' form, do we
>     want to allow users to directly state variation between two
>     entries (or forms or senses) with a single triple?
>   * Are the Interlingual-/IntralingualVariant classes necessary?
>
> Metadata
>
>   * There is no link between the metadata module and any other module
>     in OntoLex
>   * The Lexicon class is a duplicate of one already in the core
>   * The language property is a duplicate of one defined in the core
>   * ConceptualizedLinguisticResource is not used by any other part of
>     module
>   * The 'lexical link set' class and property are not used by any
>     other part of the module
>   * Several properties are named the same as classes except for the
>     case of the first letter: resourceCoverage, language,
>     lexicalLinkSet and lexicalization
>   * Is the 'linguistic model' really required by every lexicalization?
>
Thanks!

Thierry
> Thierry Declerck, Senior Consultant at DFKI GmbH, Language Technology 
> Lab Stuhlsatzenhausweg, 3 D-66123 Saarbruecken Phone: +49 681 / 857 
> 75-53 58 Fax: +49 681 / 857 75-53 38 email: declerck@dfki.de 
> ------------------------------------------------------------- 
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH 
> Firmensitz: Trippstadter Strasse 122, D-67663 Kaiserslautern 
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster 
> (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: 
> Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 
> -------------------------------------------------------------