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

From Odp

Jump to: navigation, search


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have informations about the evaluation process of this proposal

Current revision ID: 8954

General information

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.


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

Image:AdjacencyList_1.png


Ontology

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

Diagram

Image:Ontology.png


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. 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

Diagram

Image:Workflow_PR-NOR-CLTX-02.png


Scenario example

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.


Example of a Non-Ontological Resource

Description The FAO classification for water areas groups them according to some different criteria as environment, statistics, and jurisdiction, among others.
Graphical Representation

Diagram

Image:AdjacencyListWaterAreas_1.png

Web Reference http://www.fao.org/figis/servlet/RefServlet


Ontology example

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

Diagram

Image:WaterAreaOntology_1.png

Web Reference http://www.fao.org/aims/neon.jsp


Process example

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

Diagram

Image:Workflow_PR-NOR-CLTX-02_example.png


About

SubmittedBy BorisVillazón-Terrazas
Author BorisVillazón-Terrazas
Also known as
Known uses
Related to Use the Architectural Pattern: TX-AP-01
Other References

Additional information

Scenarios

Scenarios about Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema

No scenario is added to this Content OP.

Reviews

Reviews about Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema

There is no review about this proposal. This revision (revision ID 8954) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers