W3C home > Mailing lists > Public > public-ontolex@w3.org > October 2014

Re: telco today at 15:00

From: Thierry Declerck <declerck@dfki.de>
Date: Fri, 17 Oct 2014 14:17:24 +0200
Message-ID: <544108D4.1030304@dfki.de>
To: public-ontolex@w3.org

Am 17.10.2014 11:48, schrieb Philipp Cimiano:
> Dear all,
>
>  here are the access details for the ontolex teleconference today at 
> 15:00 (CET):
>
> https://www.w3.org/community/ontolex/wiki/Teleconference,_2014.17.10,_15-16_pm_CET
>
> The agenda is repeated here for the sake of convenience:
>
> Core:
>
>     In core there is now a 'SenseLexicon' class but no property to relate it any other elements in the model
Philipp, All,

I cannot join the telco. On this point 'SenseLexicon': my view on this 
-- instances of LexicalSense could be a member of an instance of a 
SenseLexicon.

Cheers

Thierry
>     We could/should consider using dct:language instead of ontolex:languageURI
>     We cannot give conditions when a Lexical Sense should apply (lemon had a condition property for this)
>     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?
>
> Syntax and Semantics
>
>     There is no property to indicate the conjugation (morphological pattern) of a word
>
> 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?
>     Representing confidence and human validation (Jorge)
>
> Metadata
>
>     Examples provided by Philipp => discussion
>     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?
>   
> Talk to you later,
>
> Philipp.
>
>
>
> -- 
> --
> Prof. Dr. Philipp Cimiano
> AG Semantic Computing
> Exzellenzcluster für Cognitive Interaction Technology (CITEC)
> Universität Bielefeld
>
> Tel: +49 521 106 12249
> Fax: +49 521 106 6560
> Mail:cimiano@cit-ec.uni-bielefeld.de
>
> Office CITEC-2.307
> Universitätsstr. 21-25
> 33615 Bielefeld, NRW
> Germany

-- 

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
-------------------------------------------------------------
Received on Friday, 17 October 2014 12:17:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:36:45 UTC