Community:Different types of relationships
From Odp
(New page: {{TitleDescription Template |Title=Different types of relationships for ontology representation |Description=The flexibility of the ontology editor to represent taxonomies based on differe...) |
Current revision (08:52, 5 October 2010) (view source) |
||
(5 intermediate revisions not shown.) | |||
Line 1: | Line 1: | ||
{{TitleDescription Template | {{TitleDescription Template | ||
|Title=Different types of relationships for ontology representation | |Title=Different types of relationships for ontology representation | ||
- | |Description= | + | |Description=In real applications, we need a flexible ontology editor that helps the user represent taxonomies based on different types of relationships between concepts and with specific features, constraints and rules for each type of relationship. E.g., specialization (is-a) taxonomies, composition (part-whole) taxonomies, lists, etc. The reason is that some features for the specialization taxonomies (represented by the existing editors, e.g., the property inheritance) are not always appropriate for taxonomies based on other types of relationships. |
- | Also, the editor | + | Also, the editor should be flexible enough to represent taxonomies based on new types of relationships and specific features, proposed by the user. |
+ | Our solution for a project in progress was to build an editor that allows the user choose the type of taxonomy and that automatically applies the property inheritance only for the specialization taxonomies. For the composition taxonomies, the concept properties are inherited on demand. And for the list-like taxonomies the inheritance is applicable only for properties defined at the ontology level (inherited by all concepts). The editor is not yet flexible enough to help the user add taxonomies based on new relationship types and with features he needs for an application. | ||
}} | }} | ||
{{Graphical representation}} | {{Graphical representation}} | ||
- | {{Modeling Issue Template}} | + | {{Modeling Issue Template |
+ | |Author=AlexandraGalatescu, | ||
+ | |Domain=Ontology | ||
+ | }} | ||
{{Additional information header}} | {{Additional information header}} | ||
{{My references}} | {{My references}} | ||
{{Modeling Issue toolbar}} | {{Modeling Issue toolbar}} | ||
+ | {{Submission to event | ||
+ | |Event=WOP:2010 | ||
+ | }} |
Current revision
Different types of relationships
Title: Different types of relationships for ontology representation
Description: In real applications, we need a flexible ontology editor that helps the user represent taxonomies based on different types of relationships between concepts and with specific features, constraints and rules for each type of relationship. E.g., specialization (is-a) taxonomies, composition (part-whole) taxonomies, lists, etc. The reason is that some features for the specialization taxonomies (represented by the existing editors, e.g., the property inheritance) are not always appropriate for taxonomies based on other types of relationships. Also, the editor should be flexible enough to represent taxonomies based on new types of relationships and specific features, proposed by the user. Our solution for a project in progress was to build an editor that allows the user choose the type of taxonomy and that automatically applies the property inheritance only for the specialization taxonomies. For the composition taxonomies, the concept properties are inherited on demand. And for the list-like taxonomies the inheritance is applicable only for properties defined at the ontology level (inherited by all concepts). The editor is not yet flexible enough to help the user add taxonomies based on new relationship types and with features he needs for an application.
Diagram (this article has no graphical representation)
About
Users | AlexandraGalatescu |
---|---|
Domains | Ontology |
Competency Questions | |
Scenarios | |
Proposed Solutions (OWL files) | |
Related patterns |
Additional information
References
Submission to event |
---|