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

Re: [all] suggestions for consolidating requirements

From: Tadej Stajner <tadej.stajner@ijs.si>
Date: Thu, 26 Apr 2012 15:29:39 +0200
Message-ID: <4F994DC3.50109@ijs.si>
To: public-multilingualweb-lt@w3.org
On 4/26/2012 2:23 PM, David Lewis wrote:
> Dear all,
> I have four further suggestions for consolidating requirements that 
> I'd like to discuss briefly on the call with the relevant people:
> Moritz, Des: I think there is potential to combine 'confidentiality' 
> with 'contentLicensingTerms', with confidentiality being a specific 
> value of contentLicensingTerms, whcih could perhaps be relaised using 
> Creative Commons license classes
> DaveL, Moritz: Could localeSpecificContent be consolidated with 
> dropRule, e.g. specifying the content should be drops for specific 
> locales, for every translation, or for every translation except 
> specified locales?
> DaveL, Pedro: I think we could consolidate author, revisionAgent and 
> translationAgent, with a generic 'agent' bound to a process spec, 
> aligning with work in the W3C Provenance Working Group, 
> www.w3.org/2011/prov/
> Pedro, Dabiel, Declan, Tadej: I think there may be opportunity to 
> consolidate mtDisambiguationData, namedEntity, terminology and 
> textAnalyticsAnnotation. For instance is MT disambiguation really 
> terminology support for MT?

Yes, they all have a lot in common. The way I see it, textAnalytics 
annotation is the common superclass of the other three, mtDisambiguation 
seems to focus on difficult content, namedEntity on named entities and 
term on terms. They all allow referring to an ontology URI behind the 
fragment they are annotating - this property is equivalent across all 
three, but there are specifics in each category.

- what would qualify as difficult content under mtDisambiguation?
- is there anything MT-specific in mtDisambiguation? Or can we call it 
simply "disambiguation"?
- mtDisambiguation-domainSelector is very similar in functionality to 
term-terminologyResource, could we consolidate those?
- namedEntity-type can be seen as a special case of a 

My recommendation would be to gather some common properties and pull 
them in the textAnalyticsAnnotation superclass.

> comments weclome,
> Dave
Received on Thursday, 26 April 2012 13:30:09 UTC

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