Submissions:ConceptTerms

From Odp

(Difference between revisions)
Jump to: navigation, search
Line 9: Line 9:
|CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?
|CompetencyQuestion=How to distinguish a preferred term or label from synonyms in order to name a concept?, How to enable cross language searching?, How to allow adding properties on term?
|ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.
|ContentODPDescription=A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.
-
|ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl?attredirects=0
+
|ReusableOWLBuildingBlock=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl
|Consequences=Compare to labels on a concept class, this solution has a higher data load.
|Consequences=Compare to labels on a concept class, this solution has a higher data load.
|Scenario=Used for terminology representation. For example, a preferred term "car" in english could be translated in "voiture" in french and linked to the same concept. Here translation relation is possible thanks to the term entity.
|Scenario=Used for terminology representation. For example, a preferred term "car" in english could be translated in "voiture" in french and linked to the same concept. Here translation relation is possible thanks to the term entity.

Revision as of 09:07, 16 August 2009


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 5513

Image:ConceptTermsPattern.jpg

General description

Name: ConceptTerms
Submitted by: Pierre-YvesVandenbussche
Also Known As:
Intent: This CP allows designers to represent language complexity for concept description (preferred term, synonyms...). For instance, synonyms (simple non preferred terms) give various possibilities to access a resource; translation relation between terms enables multilingual vocabularies searches and therefore broaden results.
Domains:
Competency Questions:
  • How to distinguish a preferred term or label from synonyms in order to name a concept?
  • How to enable cross language searching?
  • How to allow adding properties on term?
Solution description: A concept is named in a particular language by a preferred term and a set of simple non preferred terms. Those terms artifacts specialize the term entity which owns common properties for terms such as: language, source information (when creating vocabulary from corpora). This list of properties may be extended depending on vocabulary specific needs.
Reusable OWL Building Block: http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTerms.owl (628)
Consequences: Compare to labels on a concept class, this solution has a higher data load.
Scenarios: Used for terminology representation. For example, a preferred term "car" in english could be translated in "voiture" in french and linked to the same concept. Here translation relation is possible thanks to the term entity.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The ConceptTerms Content OP locally defines the following ontology elements:


Scenarios

Scenarios about ConceptTerms

This ontology describes example coming from Eurovoc(http://europa.eu/eurovoc/) where a concept has a preferred term "social sciences" in english and a simple non preferred term (i.e. synonyms) "humanities" in the same language whereas the same concept has a preferred term "sciences sociales" in french and a simple non preferred term "sciences humaines" in this language. We consider a second preferred term in english "award" which names a concept. In this particular information retrieval context, we define a coumpound non preferred term "social sciences awards" which is related to preferred terms "social sciences" and "award". >>>

Reviews

Reviews about ConceptTerms
Review article Posted on About revision (current is 5513)
WimPeters about ConceptTerms 24550838 September 2009 56265,626
MariCarmenSuarezFigueroa about ConceptTerms 24550838 September 2009 57145,714
VojtechSvatek about ConceptTerms 24550838 September 2009 57145,714

This revision (revision ID 5513) takes in account the reviews: WimPeters about ConceptTerms, VojtechSvatek about ConceptTerms, MariCarmenSuarezFigueroa about ConceptTerms

Other info at evaluation tab


Submission to event

WOP2009

Personal tools
Quality Committee
Content OP publishers