zakim

<scribe> Scribe: Philipp Cimiano

add agendum Core

SenseLexicon in the core model, but no property to related it to any other element

languageURI, use dublin core instead

conditions on Lexical Sense

MWE expressions as subclass of Lexical Entry

<jgracia> nobody against introducing a property linking SenseLexicon and LexicalSense

Decision: add senseEntry

Proposal of John: substitute ontolex:languageURI by dc:language

<jgracia> problem is redundancy of names

<jgracia> Philipp: but they are in different namespaces

Element Description: A language of the intellectual content of the resource. Recommended best practice for the values of the Language element is defined by RFC 3066 [RFC 3066, http://www.ietf.org/rfc/ rfc3066.txt] which, in conjunction with ISO 639 [ISO 639, http://www.oasis- open.org/cover/iso639a.html]), defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian, and "en-GB" for

English used in the United Kingdom.

Decision: use dc:language as definition seems to match (Philipp to do a final check of RDF vocabulary)

http://purl.org/dc/terms/language is down, returns 404

Decision: conditions on sense to be addedd

Should we add subclasses of LexicalEntry as follows Word, MultiWordExpression, Affix?

Decision: to add these subclasses

property to indicate conjugation of word

Decision: morphologicalPattern to be added to the model

thinks agendum

<jgracia> what about... SenseVariant, EntityVariant, FormVariant ?

ok, now I discovered my proposal, which was:

LexicalFormVariant, LexicalSenseVariant, LexicalFormVariant

I meant LexicalFormVariant, LexicalSenseVariant, LexicalEntryVariant

<jgracia> SenseRelation instead ? and FormRelation, EntityRelation ?

Proposal: LexicalFormVariant, LexicalEntryVariant and SenseRelation (to be decided)

wait for Elena

question: introudce property for every type of variant to to make the model easier to use and make it more precise

Jorge: use punning to use class URIs as property URIs ?

Proposal: property vs. classes the same up to lowe case / upper case

we decided to remove the interlingual and intrlalingual variants (Decision!)

Decision: we had source and target

<jgracia> name for the superpropery?

Name for superproperty of source and target: source, target -> edge (proposal by John)

<jgracia> John: edge

<jgracia> (to be confirmed)

Armando: example2.ttl generally fine, up to the fact that metadata and content has to be split and up to terminology used

Details to be discussed:

Armando: list of renamings to discuss

resourceCoverage --> coverage ResourceCoverage --> LexicalCoverage lexicalizedDataset --> referenceDataset lexicon --> lexiconDataset

lime: class --> lime:resourceType (proposed: not applied still in the examples)

resourceCoverage --> coverage ResourceCoverage --> LexicalCoverage lexicalizedDataset --> referenceDataset lexicon --> lexiconDataset

lime: class --> lime:resourceType (proposed: not applied still in the examples)

Other points: double use of property coverage

Example1.ttl is the same as lexicon.ttl

LexiconDataSet

LexicalizationSet

lexiconDataset

referenceDataset

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: cimiano
Found Scribe: Philipp Cimiano

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: Armando Decision Fahad John Jorge Philipp Proposal jgracia joined lime ontolex
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Got date from IRC log name: 17 Oct 2014
Guessing minutes URL: http://www.w3.org/2014/10/17-ontolex-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report