Submissions:Classification scheme - adjacency list model - to Taxonomy
From Odp
Line 94: | Line 94: | ||
|Event=WOP2009:Main | |Event=WOP2009:Main | ||
}} | }} | ||
+ | <headertabs/> |
Revision as of 17:35, 3 March 2010
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: ask for a review post your open review specify if this revision takes in account any of the review(s)add a new scenario for Classification scheme - adjacency list model - to Taxonomy In general, it could be useful to visit the evaluation section to have informations about the evaluation process of this proposal Current revision ID: 8747 |
- General information
- Scenario example
- About
- Additional information
- Scenarios
- Reviews
- Modeling issues
- References
Name | Classification scheme - adjacency list model - to Taxonomy |
---|---|
Problem | Re-engineering a classification scheme which follows the adjacency list model to design a taxonomy.
APPLICABILITY The semantics of the relation between parent and children items are subClassOf. There is no multi-inheritance nor cyclic relations. |
Non-Ontological Resource
Description | A non-ontological resource holds a classification scheme which follows the adjacency list model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity. The semantics of the hierarchical relation between parents and children concepts may vary depending of the context. The adjacency list data model for hierarchical classifications proposes to create an entity which holds a list of items with a linking column associated to their parent items. |
---|---|
Graphical Representation |
Diagram |
Ontology
Description | The ontology generated will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations. |
---|---|
Graphical Representation |
Diagram |
Process
Description | 1. Identify the classification scheme items which do not have a parent key value, i.e. classification scheme items without parents.
2. For each one of the above identified classification scheme items cei: 2.1. Create the corresponding ontology class, Ci class. 2.2. Identify the classification scheme items, cej , which are children of cei, by using the parent key values. 2.3. For each one of the above identified classification scheme items cej : 2.3.1. Create the corresponding ontology class, Cj class. 2.3.2. Set up the subClassOf relation between Cj and Ci. 2.3.3. Repeat from step 2.2 for cej as a new cei. 3. If there are more than one classification scheme items without parent cei 3.1. Create an ad-hoc class as the root class of the ontology. 3.2. Set up the subClassOf relation between Ci class and the root class. |
---|---|
Graphical Representation |
Diagram |