EnricoDaga (Talk | contribs) |
|||
| (14 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
| − | {{ | + | {{Graphical representation header}} |
| + | {{Graphical representation | ||
|ImageName=ConceptTermsPattern.jpg | |ImageName=ConceptTermsPattern.jpg | ||
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| − | |SubmittedBy=Pierre-YvesVandenbussche | + | |SubmittedBy=Pierre-YvesVandenbussche, JeanCharlet |
|Name=ConceptTerms | |Name=ConceptTerms | ||
| − | |Intent=This CP allows designers to represent | + | |Intent=This CP allows designers to represent jointly conceptual and linguistic part of a vocabulary. |
| + | The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept whith simple labels. | ||
| + | |Domain=Linguistic, Vocabulary, | ||
|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 | + | |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. This list of properties may be extended depending on vocabulary specific needs. |
| + | 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. | ||
|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 | + | |Scenario=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". |
| − | |ReengineeredFrom=BS8723-5 model: http://schemas.bs8723.org/ | + | |CPInstantiationExample=http://sites.google.com/site/pierreyvesvandenbussche/resources/ConceptTermsEurovocExample.owl |
| + | |ReengineeredFrom=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). | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| + | {{Takes in account review | ||
| + | |TakesInAccountReview=WimPeters about ConceptTerms | ||
| + | }} | ||
| + | {{Takes in account review | ||
| + | |TakesInAccountReview=VojtechSvatek about ConceptTerms | ||
| + | }} | ||
| + | {{Takes in account review | ||
| + | |TakesInAccountReview=MariCarmenSuarezFigueroa about ConceptTerms | ||
| + | }} | ||
| + | {{Additional information header}} | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
{{Submission to event | {{Submission to event | ||
|Event=WOP2009 | |Event=WOP2009 | ||
}} | }} | ||
|
Last modified date is: 2010-03-08 |
Diagram
| Name: | ConceptTerms |
|---|---|
| Submitted by: | Pierre-YvesVandenbussche, JeanCharlet |
| Also Known As: | |
| Intent: | This CP allows designers to represent jointly conceptual and linguistic part of a vocabulary.
The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept whith simple labels. |
| 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. This list of properties may be extended depending on vocabulary specific needs.
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. |
| 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: |
|
| 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 9079) 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'
