View source for Submissions:Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema ← Submissions:Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|Name=Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema
|Problem=Re-engineering a classification scheme, which follows the adjacency list model, to design an ontology schema.
}}
{{Reengineering OP Proposal NOR Template
|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=AdjacencyList_1.png
}}
{{Reengineering OP Proposal Ontology Template
|Description=The generated ontology 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 disambiguated by using an external resource. In the case of that the external resource does not provide any relation between two items, the pattern takes advantage of the use of logical patterns for asserting the relation partOf or subClassOf, as appropriate.
|Graphical Representation=Ontology.png
}}
{{Reengineering OP Proposal Process Template
|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. Using the external resource identify the semantics of the relation between Cj and Ci, and set up the relation identified.

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. Using the external resource identify the semantics of the relation between Ci class and the root class, and set up the relation identified.
|Graphical Representation=Workflow_PR-NOR-CLTX-02.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=Suppose that someone wants to build an ontology based on the water areas classification published by FAO. This classification scheme follows the adjacency list data model.
}}
{{Reengineering OP Proposal NOR Example Template
|Description=The FAO classification for water areas groups them according to some different criteria as environment, statistics, and jurisdiction, among others.
|Graphical Representation=AdjacencyListWaterAreas_1.png
|Web Reference=http://www.fao.org/figis/servlet/RefServlet
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The generated ontology 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 disambiguated by using an external resource. In the case of that the external resource does not provide any relation between two items, the pattern takes advantage of the use of logical patterns for asserting the relation partOf or subClassOf, as appropriate.
|Graphical Representation=WaterAreaOntology_1.png
|Web Reference=http://www.fao.org/aims/neon.jsp
}}
{{Reengineering OP Proposal Process Example Template
|Description=1. Create the Water area class.

2. Create the Environmental area class.

3. Using the external resource identify the semantics of the relation between
Environmental area class and the Water area class, and set up the relation identified.

3.1. Create the Inland/marine class.

3.2. Using the external resource identify the semantics of the relation between
Inland/marine class and the Environmental area class, and set up the relation identified.

3.3. Create the Ocean class.

3.4. Using the external resource identify the semantics of the relation between
Ocean class and the Environmental area class, and set up the relation identified.

3.5. Create the North/South/Equatorial class.

3.6. Using the external resource identify the semantics of the relation between
North/South/Equatorial class and the Environmental area class, and set up the relation identified.

4. Create the Fishing Statistical area class.

5. Using the external resource identify the semantics of the relation between Fishing Statistical area class and the Water area class, and set up the relation identified.

5.1. Create the FAO statistical area class.

5.2. Using the external resource identify the semantics of the relation between FAO statistical area class and the Fishing Statistical area class, and set up the relation identified.

5.3. Create the Areal grid system class.

5.4. Using the external resource identify the semantics of the relation between
Areal grid system class and the Fishing Statistical area class, and set up the relation identified.

6. Create the Jurisdiction area class.

7. Using the external resource identify the semantics of the relation between
Jurisdiction area class and the Water area class, and set up the relation identified.

|Graphical Representation=Workflow_PR-NOR-CLTX-02_example.png
}}
{{Reengineering OP Proposal Additional Information Template
|SubmittedBy=BorisVillazón-Terrazas, 
|Author=BorisVillazón-Terrazas, 
|Related to=Use the Architectural Pattern: TX-AP-01, 
}}

{{Scenarios about me}}
{{Reviews about me}}{{Modeling issues about me}}