W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > May 2012

[ACTION-80] consider consolidation of mtDisambiguationData, namedEntity, terminology and textAnalyticsAnnotation

From: Tadej Stajner <tadej.stajner@ijs.si>
Date: Wed, 09 May 2012 19:49:47 +0200
Message-ID: <4FAAAE3B.2060008@ijs.si>
To: public-multilingualweb-lt@w3.org
Hi, all,

this question is mostly directed to people working in MT with regard to 
disambiguation.

Since we came to a conclusion that there is strong overlap between the 
following data categories, we're consolidating them:
mtDisambiguationData
namedEntity
terminology
textAnalyticsAnnotation

First of all, there is an obvious common part to the first three. Let's 
call it the 'concept mention' recipe. It's meant to represent that some 
fragment of text is lexicalizing (mentioning) some concept with an URI.

namedEntity has the following specifics:
- type of entity (pointing to an URI, describing that type)
- alternative labels (names in different languages)

terminology has the following specifics:
- terminology lexicon
- alternative labels

mtDisambiguation also has the concept URI, but additionally define
- 'disambiguation data'
- 'semantic selector'

The open question is: that do these two additional attributes bring any 
additional infomation if we already have the fragment disambiguated with 
the URI?

  If not, is there anything else in mtDisambiguation that could not be 
covered by the namedEntity and terminology categories?

thanks for the input,
-- Tadej
Received on Wednesday, 9 May 2012 17:50:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:44 UTC