m (Article is waiting for review.) |
|||
| (9 intermediate revisions by 5 users not shown) | |||
| Line 3: | Line 3: | ||
|Name=Classification scheme - path enumeration model - to Taxonomy | |Name=Classification scheme - path enumeration model - to Taxonomy | ||
|Problem=Re-engineering a classification scheme which follows the path enumeration model to design a 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. | ||
}} | }} | ||
{{Reengineering OP Proposal NOR Template | {{Reengineering OP Proposal NOR Template | ||
| Line 36: | Line 42: | ||
3.2. Set up the subClassOf relation between Ci class and the root class. | 3.2. Set up the subClassOf relation between Ci class and the root class. | ||
| − | |Graphical Representation= | + | |Graphical Representation=Wfcspesocheck.png |
}} | }} | ||
{{Reengineering OP Proposal Scenario Example Template | {{Reengineering OP Proposal Scenario Example Template | ||
| Line 43: | Line 49: | ||
{{Reengineering OP Proposal NOR Example Template | {{Reengineering OP Proposal NOR Example Template | ||
|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. | |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= | + | |Graphical Representation=PathEnumerationOccupationscheck.png |
|Web Reference=http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm? TargetUrl=LST_NOM&StrLanguageCode=EN&IntFamilyCode=260276&TxtSearch= | |Web Reference=http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm? TargetUrl=LST_NOM&StrLanguageCode=EN&IntFamilyCode=260276&TxtSearch= | ||
}} | }} | ||
| Line 54: | Line 60: | ||
|Description=1. Create the LEGISLATORS, SENIOR OFFICIALS AND MANAGERS class. | |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. | |
| − | 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 | |
| − | between the Corporate managers class and the LEGISLATORS, SENIOR | + | MANAGERS class. |
| − | 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. | |
| − | OFFICIALS AND MANAGERS class and the Occupation class. | + | |
| − | + | 5. Set up the subClassOf relation between the PROFESSIONALS class and the Occupation class. | |
| − | Occupation class. | + | |Graphical Representation=Wfcspesoexamplecheck.png |
| − | |Graphical Representation= | + | |
}} | }} | ||
{{Reengineering OP Proposal Additional Information Template | {{Reengineering OP Proposal Additional Information Template | ||
| Line 79: | Line 81: | ||
|Related to=Use the Architectural Pattern: TX-AP-01 | |Related to=Use the Architectural Pattern: TX-AP-01 | ||
}} | }} | ||
| − | + | {{Additional information header}} | |
| + | [[Category:Review assigned]] | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
{{Submission to event | {{Submission to event | ||
|Event=WOP2009 | |Event=WOP2009 | ||
}} | }} | ||
| − | |||
|
Last modified date is: 2010-03-05 |
| 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. |
| 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
|
| 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
|
| 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
|
| 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
|
| Web Reference | http://droz.dia.fi.upm.es/hrmontology/ |
| 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
|
| 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 |
No scenario is added to this Content OP.
This revision (revision ID 8952) takes in account the reviews: none
Other info at evaluation tab
|
Submission to event |
|---|
'Ontology Design Patterns'
