Submissions:Classification scheme - path enumeration model - to Taxonomy

From Odp

This article has assigned reviews
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: 8952

General information

Name Classification scheme - path enumeration model - to Taxonomy
Problem Re-engineering a classification scheme which follows the path enumeration 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 path enumeration 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 path enumeration data model for classification schemes take advantage of that there is one and only one path from the root to every item in the classification. The path enumeration model stores that path as string by concatenating either the edges or the keys of the classification scheme items in the path.

Graphical Representation

Diagram

Image:PathEnumeration.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 mapped to subClassOf relations.
Graphical Representation

Diagram

Image:Ontology.png


Process

Description 1. Identify the classification scheme items whose their path enumeration values are equal to their key values, 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 path enumeration 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

Image:Wfcspesocheck.png


Scenario example

Description Suppose that someone wants to build an ontology based on the International Standard Classification of Occupations (for European Union purposes) ISCO-88 (COM). This classification scheme follows the path enumeration data model.


Example of a Non-Ontological Resource

Description The International Standard Classification of Occupations (for European Union purposes), 1988 version: ISCO-88 (COM) published by Eurostat is modeled with the path enumeration data model.
Graphical Representation

Diagram

Image:PathEnumerationOccupationscheck.png

Web Reference http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm? TargetUrl=LST_NOM&StrLanguageCode=EN&IntFamilyCode=260276&TxtSearch=


Ontology example

Description The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each occupation 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

Image:OccupationsOntology.png

Web Reference http://droz.dia.fi.upm.es/hrmontology/


Process example

Description 1. Create the LEGISLATORS, SENIOR OFFICIALS AND MANAGERS class.

1.1. Create the Legislators and senior officials class, and set up the subClassOf relation between the Legislators and senior officials class and the LEGISLATORS, SENIOR OFFICIALS AND MANAGERS class.

1.2. Create the Corporate managers class, and set up the subClassOf relation between the Corporate managers class and the LEGISLATORS, SENIOR OFFICIALS AND MANAGERS class.

2. Create the PROFESSIONALS class.

3. Create the Occupation class.

4. Set up the subClassOf relation between the LEGISLATORS, SENIOR OFFICIALS AND MANAGERS class and the Occupation class.

5. Set up the subClassOf relation between the PROFESSIONALS class and the Occupation class.

Graphical Representation

Diagram

Image:Wfcspesoexamplecheck.png


About

SubmittedBy Boris Villazón Terrazas
Author Boris Villazón Terrazas
Also known as Classification scheme - path enumeration model - to Taxonomy
Known uses
Related to Use the Architectural Pattern: TX-AP-01
Other References

Additional information

Scenarios

Scenarios about Classification scheme - path enumeration model - to Taxonomy

No scenario is added to this Content OP.

Reviews

Reviews about Classification scheme - path enumeration model - to Taxonomy
Review article Posted on About revision (current is 8952)
VioletaDamjanovic about Classification scheme - path enumeration model - to Taxonomy 24550838 September 2009 56295,629
KurtSandkuhl about Classification scheme - path enumeration model - to Taxonomy 24550838 September 2009 57125,712
GerdGroener about Classification scheme - path enumeration model - to Taxonomy 245508510 September 2009 57765,776

This revision (revision ID 8952) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about Classification scheme - path enumeration model - to Taxonomy

There is no Modeling issue related to this proposal.


References

Add a reference


Submission to event

WOP2009

Personal tools
Quality Committee
Content OP publishers