| 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 | + | |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. | ||
|
Last modified date is: 2009-08-16 |
| 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: | |
| 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: | 1 (746) |
| 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: |
The ConceptTerms Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 5513) takes in account the reviews: ConceptTerms (WimPeters about ConceptTerms, VojtechSvatek about ConceptTerms, MariCarmenSuarezFigueroa about ConceptTerms)
Other info at evaluation tab
|
Submission to event |
|---|
'Ontology Design Patterns'
