IRC log of ontolex on 2014-10-17
Timestamps are in UTC.
- 13:04:40 [RRSAgent]
- RRSAgent has joined #ontolex
- 13:04:40 [RRSAgent]
- logging to http://www.w3.org/2014/10/17-ontolex-irc
- 13:04:51 [Zakim]
- Zakim has joined #ontolex
- 13:05:04 [cimiano]
- zakim
- 13:05:16 [cimiano]
- Meeting: ontolex
- 13:05:22 [cimiano]
- Scribe: Philipp Cimiano
- 13:05:32 [cimiano]
- Chair: Philipp Cimiano
- 13:05:56 [cimiano]
- add agendum Core
- 13:06:03 [cimiano]
- agenda+ Core
- 13:06:14 [cimiano]
- agenda+ Syntax and Semantics
- 13:06:18 [cimiano]
- agenda+ Variation
- 13:06:22 [cimiano]
- agenda+ Metadata
- 13:07:37 [cimiano]
- next agendum
- 13:08:16 [cimiano]
- SenseLexicon in the core model, but no property to related it to any other element
- 13:08:31 [cimiano]
- languageURI, use dublin core instead
- 13:08:46 [cimiano]
- conditions on Lexical Sense
- 13:08:51 [cimiano]
- MWE expressions as subclass of Lexical Entry
- 13:10:14 [jgracia]
- nobody against introducing a property linking SenseLexicon and LexicalSense
- 13:10:23 [cimiano]
- Decision: add senseEntry
- 13:11:30 [cimiano]
- Proposal of John: substitute ontolex:languageURI by dc:language
- 13:12:09 [jgracia]
- problem is redundancy of names
- 13:12:36 [jgracia]
- Philipp: but they are in different namespaces
- 13:14:55 [jgracia]
- rrsagent, make log public
- 13:16:12 [cimiano]
- 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
- 13:16:13 [cimiano]
- English used in the United Kingdom.
- 13:18:29 [Fahad]
- Fahad has joined #ontolex
- 13:19:17 [cimiano]
- Decision: use dc:language as definition seems to match (Philipp to do a final check of RDF vocabulary)
- 13:21:50 [cimiano]
- http://purl.org/dc/terms/language is down, returns 404
- 13:23:15 [cimiano]
- Decision: conditions on sense to be addedd
- 13:23:27 [cimiano]
- Should we add subclasses of LexicalEntry as follows Word, MultiWordExpression, Affix?
- 13:25:52 [cimiano]
- Decision: to add these subclasses
- 13:26:00 [cimiano]
- next agendum
- 13:26:22 [cimiano]
- property to indicate conjugation of word
- 13:28:48 [cimiano]
- Decision: morphologicalPattern to be added to the model
- 13:28:58 [cimiano]
- thinks agendum
- 13:29:03 [cimiano]
- next agendum
- 13:30:20 [jgracia]
- what about... SenseVariant, EntityVariant, FormVariant ?
- 13:33:30 [cimiano]
- ok, now I discovered my proposal, which was:
- 13:33:53 [cimiano]
- LexicalFormVariant, LexicalSenseVariant, LexicalFormVariant
- 13:34:18 [cimiano]
- I meant LexicalFormVariant, LexicalSenseVariant, LexicalEntryVariant
- 13:39:54 [jgracia]
- SenseRelation instead ? and FormRelation, EntityRelation ?
- 13:41:55 [cimiano]
- Proposal: LexicalFormVariant, LexicalEntryVariant and SenseRelation (to be decided)
- 13:42:58 [jgracia]
- rrsagent, draft minutes
- 13:42:58 [RRSAgent]
- I have made the request to generate http://www.w3.org/2014/10/17-ontolex-minutes.html jgracia
- 13:44:45 [cimiano]
- wait for Elena
- 13:46:11 [cimiano]
- question: introudce property for every type of variant to to make the model easier to use and make it more precise
- 13:48:00 [cimiano]
- Jorge: use punning to use class URIs as property URIs ?
- 13:50:29 [cimiano]
- Proposal: property vs. classes the same up to lowe case / upper case
- 13:51:10 [cimiano]
- we decided to remove the interlingual and intrlalingual variants (Decision!)
- 13:51:35 [cimiano]
- Decision: we had source and target
- 13:53:02 [jgracia]
- name for the superpropery?
- 13:53:04 [cimiano]
- Name for superproperty of source and target: source, target -> edge (proposal by John)
- 13:53:05 [jgracia]
- John: edge
- 13:53:25 [jgracia]
- (to be confirmed)
- 13:57:37 [jgracia]
- next agendum
- 14:04:23 [cimiano]
- Armando: example2.ttl generally fine, up to the fact that metadata and content has to be split and up to terminology used
- 14:13:18 [cimiano]
- Details to be discussed:
- 14:14:04 [cimiano]
- Armando: list of renamings to discuss
- 14:14:31 [cimiano]
- resourceCoverage --> coverage ResourceCoverage --> LexicalCoverage lexicalizedDataset --> referenceDataset lexicon --> lexiconDataset
- 14:14:32 [cimiano]
- lime:class --> lime:resourceType (proposed: not applied still in the examples)
- 14:14:37 [cimiano]
- resourceCoverage --> coverage ResourceCoverage --> LexicalCoverage lexicalizedDataset --> referenceDataset lexicon --> lexiconDataset
- 14:14:38 [cimiano]
- lime:class --> lime:resourceType (proposed: not applied still in the examples)
- 14:15:29 [cimiano]
- Other points: double use of property coverage
- 14:15:44 [cimiano]
- Example1.ttl is the same as lexicon.ttl
- 14:16:30 [cimiano]
- LexiconDataSet
- 14:16:33 [cimiano]
- LexicalizationSet
- 14:18:02 [cimiano]
- lexiconDataset
- 14:18:05 [cimiano]
- referenceDataset
- 14:19:50 [jgracia]
- rrsagent, draft minutes
- 14:19:50 [RRSAgent]
- I have made the request to generate http://www.w3.org/2014/10/17-ontolex-minutes.html jgracia
- 14:27:22 [cimiano]
- rrsagent bye
- 14:28:04 [cimiano]
- We agreed already on LexicalizationSet, lexiconDataset, referenceDataset
- 14:28:09 [cimiano]
- rrsagent, bye
- 14:28:09 [RRSAgent]
- I see no action items