W3C

- DRAFT -

Kick-off teleconference for community group on ontology lexica

02 Dec 2011

See also: IRC log

Attendees

Present
Regrets
Chair
Philipp
Scribe
Philipp Cimiano, Armando Stellato

Contents


<cimiano> Scribe: Philipp Cimiano

<starred> Scribe: Armando Stellato

<cimiano> Hi all.

<cimiano> I am on the teleconference. It says the host has not arrived.

<cimiano> Who is the host? Mihael?

<cimiano> [take up] next agendum

<cimiano> tobias are you taking notes?

<tobiaswunner> Yes.

<cimiano> good thx

<tobiaswunner> Goals of meata requirements

<tobiaswunner> 6 requirements http://www.w3.org/community/ontolex/wiki/Goals_and_Scope_of_Ontology-Lexica_Community_Group

<cimiano> Nicoleta> agrees with requirement

<tobiaswunner> nicoletta M3 requires discussion (contextual aspects of meaning)

<tobiaswunner> cimiano > many aspects (pragmatic) cannot be expressed fully on ontological knowledge. semantic reference system should pick up the meaning.

<cimiano> aldo> semantics by reference can be confusing

<tobiaswunner> aldo > reference of uris to multiple uris. is the object a good representation of the meaning behind the lexical entry?

<tobiaswunner> cimiano > technical level to point to uri. specific choice of granularity for domain needs.

<tobiaswunner> cimiano > make deeper meaning distinctions for lexical entries when lexical entries might not represent that meaning?

<tobiaswunner> aldo > words do not need unique senses.

<tobiaswunner> aldo > as in wordnet.

<tobiaswunner> cimiano > agrees in principal. interpret meaning of words in context of ontology. more than wordnet.

<tobiaswunner> aldo > issue between reference of words and meaning. clarify requirements.

<cimiano> We will have at most 9 minutes more of discussion on the goals.

<cimiano> Who wants to speak? Please use q+ do indicate your intend to contribute to the discussion ;-)

<tobiaswunner> paulb > ontology-lexicon interface with ontology in first place. enrich ontologies to use them in nlp tasks.

<tobiaswunner> paulb > connect the ontology with lexical information.

<tobiaswunner> cimiano > group seems to agree on most of the requirements. semantic by reference (R3) requirement needs more discussion

<tobiaswunner> starred (armando stellato) > does a lexicon ontology meta model require a lexicon model? openess. many application should understand what the reference of a given lexicon is without understanding the lexicon. semantic reference inside a given lexicon (with or without synset).

<tobiaswunner> cimiano > lexicon ontology model includes a meta model

<tobiaswunner> cimiano > the goal is not only to develop a lexicon meta model but a lexicon meta model as part of an ontology (lexicon-ontology interface)

<tobiaswunner> starred > what is the lexicon not?

<cimiano> [take up] next agendum

<tobiaswunner> ACTION: starred add to wiki what lexicon is not [recorded in http://www.w3.org/2011/12/02-ontolex-minutes.html#action01]

<cimiano> close agendum

<tobiaswunner> Start requirements from the use case to scope work and take decisions to work on the model.

<tobiaswunner> cimiano > a lexicon model could include many things

<tobiaswunner> cimiano > idea of modules and around a core

<tobiaswunner> cimiano > with clear deadlines for methodology for each use case

<tobiaswunner> nicoleta > agrees and says goodbye

<tobiaswunner> cimiano > description and motivation for each use case. in a very concrete way using examples. as well as the type of knowledge.

<tobiaswunner> cimiano > proceeding in this way would be easy and could drive the development of the specification.

<tobiaswunner> starred > its fine

<tobiaswunner> cimiano > proposed tandems for each use case, which means two people each from different research institutes. to allow for different views/interests for a use case.

<tobiaswunner> cimiano > 1st use case: ontology-based information extraction; ontology lexicon gives information for extraction

<tobiaswunner> cimiano > plan is to extend the use cases with ongoing telcos

<tobiaswunner> cimiano > on wiki

<tobiaswunner> cimiano > 2nd ontology question answering; translate knowledge in sparql queries

<tobiaswunner> cimiano > 3rd natural language generation; going the other way from triples to text

<tobiaswunner> cimiano > 4th integrating and publishing of legacy data; proposes Aldo a second owner besides John.

<tobiaswunner> aldogangemi > agrees

<tobiaswunner> cimiano > Other interests in this use case: Veronique Malaise, Armando Stellato

<aldogangemi> (wave) to Armando

<tobiaswunner> paulb > two level of use cases. for example ontology-based IE with the general use and use cases on domain level (biomedical, financial, etc.). specifics with background the people are working in.

<tobiaswunner> cimiano > great idea.

<tobiaswunner> cimiano > so far discussed more the general level of use cases

<tobiaswunner> cimiano > 5th translation

<tobiaswunner> emontiel > someone interested in multilingual aspects in joining this use case?

<starred> I'll be

<tobiaswunner> emontiel > rich linguistic descriptions can help/contribute to provide better translations

<tobiaswunner> john > is ontology machine translation different from 4

<tobiaswunner> paulb > yes, the first is use ontologies to translate labels vs. translate text using the ontology

<tobiaswunner> cimiano > 6th use case: cross-lingual information extraction

<tobiaswunner> cimiano > Other interests: Maria Maleshkova from Open University

<tobiaswunner> cimiano > 7th use case: concept and named entity tagging in text. Use ontology to represent the named entities.

<tobiaswunner> cimiano > should we take this on board?

<tobiaswunner> armando > use of term named entities can be controversal because it might not be named entity recognition

<tobiaswunner> john > semantic light annotation using entities in ontology

<tobiaswunner> armando > how can this be made on ontology side; standard offline annotations?

<tobiaswunner> john > include also extra syntactic information which can be helpful to identify entities

<tobiaswunner> cimiano > it cannot be forseen in which particular way applications will use the model

<tobiaswunner> cimiano > for languages like english morphology might not play a big role but for other languages like arabic. annotations is not the primarily mission.

<tobiaswunner> cimiano > maybe rename use case

<tobiaswunner> cimiano > 6th use case: support to automatic ontology mediation

<tobiaswunner> armando > problem statement: many algorithms or alignments have been proposed without considering the environment as in automatic or manual alignment. how to automate this? performance issues for instance when the ontologies are too large.

<tobiaswunner> armando > here meta properties can be helpful

<tobiaswunner> armando > for agents

<tobiaswunner> armando > for example in FAO work the agrovoc vocabulary used skos which did not have enough linguistic knowledge. lack of implementations.

<tobiaswunner> armando > knowing the model in advance is useful for the algorithm

<tobiaswunner> cimiano > useful for other use cases as well

<tobiaswunner> armando > trade off for each use case. how much to talk about use case and how much too talk about the model.

<tobiaswunner> cimiano > given a vocabulary for the ontology-lexicon model the algorithm aggregates the this information

<tobiaswunner> armando > half of the labels are english half not

<tobiaswunner> armando > ontology is linked to wordnet synsets. synsets can be used as "labels".

<tobiaswunner> armando > synsets as anchors more precise as words

<tobiaswunner> john > which lexical resource you link to seems not particular to lexical linked data but linked data in general. be careful on existing approaches on linked data to not duplicate them in this use case

<tobiaswunner> john > existing linking mechanisms mainly developed in linked data community

<tobiaswunner> armando > agree to check duplication in community

<tobiaswunner> armando > agree as in issue of alignment is broader than lexical linked data

<tobiaswunner> cimiano > a requirement to the model should be the possibility of linking concepts to synsets?

<tobiaswunner> ciminao > we presented use cases now

<tobiaswunner> cimiano > q1: Are there any use cases we did not mention?

<tobiaswunner> cimiano > q2: Any people we should still invite?

<tobiaswunner> cimiano > q3: Timeline?

<tobiaswunner> aldo > fact extraction in obie use case?

<tobiaswunner> aldo > two problems extraction of facts and resolving entities

<tobiaswunner> cimiano > part of the use case

<tobiaswunner> cimiano > also semantic tagging use case would contain the issue of resolving

<tobiaswunner> aldo > information extraction stuff could also be merged depending on purpose of use cases.

<tobiaswunner> helene > normalization of text data

<tobiaswunner> paulb > lexis-nexis use case about semantic tagging in law texts

<aldogangemi> i was saying that IE and NER use cases might be merged or not depending on the scope of the model(s) this CG wants to deliver

<tobiaswunner> thanks

<tobiaswunner> helene > use a lexicon to normalize linked data

<tobiaswunner> helene > annotate document by creating rdf based on meta data

<tobiaswunner> paul > tagging the document by meta data which then can be used for indexing

<tobiaswunner> cimiano > sounds like semantic tagging by using the tag to index the document. more interesting would be to have a domain

<tobiaswunner> paulb > nexis-lexis in law domain

<tobiaswunner> cimiano > helene do you want to add use case description?

<tobiaswunner> helene > yes

<tobiaswunner> ACTION: Helene Rabault to add semantic tagging in legal text use case description on wiki [recorded in http://www.w3.org/2011/12/02-ontolex-minutes.html#action02]

<tobiaswunner> cimiano > good. as start to agree on most uses to get going.

<tobiaswunner> cimiano > any other people to invite?

<tobiaswunner> helene > Christophe Tricot ontology terminology society in france

<tobiaswunner> cimiano > agenda target: end of march specification of use cases

<tobiaswunner> cimiano > two more telcos to finalize the use cases, january 13th, february 3rd

<tobiaswunner> cimiano > best time proposals

<tobiaswunner> cimiano > 2pm or 3pm CET

<tobiaswunner> cimiano > thanks all for participating. have a good day.

Summary of Action Items

[NEW] ACTION: Helene Rabault to add semantic tagging in legal text use case description on wiki [recorded in http://www.w3.org/2011/12/02-ontolex-minutes.html#action02]
[NEW] ACTION: starred add to wiki what lexicon is not [recorded in http://www.w3.org/2011/12/02-ontolex-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2011/12/02 13:36:03 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Philipp Cimiano
Found Scribe: Armando Stellato

WARNING: 0 scribe lines found (out of 149 total lines.)
Are you sure you specified a correct ScribeNick?

Scribes: Philipp Cimiano, Armando Stellato

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: ChChiarcos aldogangemi cimiano emontiel gaguado gaguadod jgracia joined left mihael mlefranc ontolex paulb starred tobiaswunner
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Got date from IRC log name: 02 Dec 2011
Guessing minutes URL: http://www.w3.org/2011/12/02-ontolex-minutes.html
People with action items: add helene rabault starred

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


[End of scribe.perl diagnostic output]