Submissions:ConceptTerms Revision as of 15:12, 17 September 2009 by Pierre-YvesVandenbussche (Talk | contribs) (Reviews corrections) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2009-09-17

General description

Name:	ConceptTerms
Submitted by:	Pierre-YvesVandenbussche, JeanCharlet
Also Known As:
Intent:	This CP allows designers to represent both conceptual and linguistic part of a vocabulary. The pattern purpose is not to encompass all linguistic complexity as Linginfo(http://olp.dfki.de/LingInfo/index.php) or LMF(http://www.lexicalmarkupframework.org/) does, but to describe linguistic information in more details than simple labels on a concept as SKOS does. This pattern suits for various vocabularies (thesaurus, terminology, taxonomy…) and has been applied to GEMET, Eurovoc, CIM10 among other. Modeling takes into account: -the possibility to extend the current pattern in order to add some more precise linguistic information (for instance represent translation relation between two terms since term is a class) -minimal linguistic artifacts necessary for vocabulary resource access by providing a preferred Term to name a concept and some synonyms which are Simple non preferred terms.
Domains:	Linguistic, Vocabulary
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:	1 (746)
Consequences:	Compare to labels on a concept class, this solution has a higher data load.
Scenarios:	Used for vocabulary representation. For example in Eurovoc(http://europa.eu/eurovoc/), 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. If we wanted to add a translation relation between terms we could state that "social sciences" english term is a translation of "sciences sociales" french term. If we consider a second preferred term in english "award" which names a concept, in a particular information retrieval context, we could define a coumpound non preferred term "social sciences awards" which is related to preferred terms "social sciences" and "award".
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:	BS8723-5 model: http://schemas.bs8723.org/Examples.aspx In BS8723 model triangular-shaped relations are defined between a thesaurus concept a preferred term and some simple non preferred terms. We are convinced that maintaining this model can be optimized by reifying those relations in a single relation class. That is why we defines the Concept-Terms relation which reusing N-ary pattern in order to represent terms on a concept. Between all terms we distinguish a preferred term and some synonyms (simple non preferred terms).
Has Components:
Specialization Of:
Related CPs:

Elements

The ConceptTerms Content OP locally defines the following ontology elements:

Scenarios

Scenarios about ConceptTerms

No scenario is added to this Content OP.

Reviews

Reviews about ConceptTerms

There is no review about this proposal.

Some subquery has no valid condition.

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

Other info at evaluation tab

	Submission to event WOP2009