Submissions:Term-based – record-based model – thesaurus to lightweight ontology
From Odp
m (Review has been assigned.) |
Current revision (08:30, 31 May 2010) (view source) m (Text replace - 'WOP2009:Main' to 'WOP:2009') |
||
| (8 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
{{Reengineering_OP_Proposal_toolbar}} | {{Reengineering_OP_Proposal_toolbar}} | ||
{{Reengineering OP Proposal General Information Template | {{Reengineering OP Proposal General Information Template | ||
| - | |Name=Term-based | + | |Name=Term-based – record-based model - thesaurus to lightweight ontology |
| - | |Problem= | + | |Problem=Re-engineering a term-based thesaurus which follows the record-based |
model to design a lightweight ontology. | model to design a lightweight ontology. | ||
| + | APPLICABILITY | ||
| + | |||
| + | The semantics of the relation between narrower and broader terms are subClassOf. | ||
}} | }} | ||
{{Reengineering OP Proposal NOR Template | {{Reengineering OP Proposal NOR Template | ||
| Line 10: | Line 13: | ||
A thesaurus represents the knowledge of a domain with a collection of terms and a limited set of relations between them. | A thesaurus represents the knowledge of a domain with a collection of terms and a limited set of relations between them. | ||
The record-based data model is a denormalized structure, uses a record for every term with the information about the term, such as synonyms, broader, narrower and related terms. | The record-based data model is a denormalized structure, uses a record for every term with the information about the term, such as synonyms, broader, narrower and related terms. | ||
| - | |||
|Graphical Representation=recordbasedtermbased.png | |Graphical Representation=recordbasedtermbased.png | ||
}} | }} | ||
{{Reengineering OP Proposal Ontology Template | {{Reengineering OP Proposal Ontology Template | ||
| - | |Description=The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. A subClassOf relation is defined between the new classes for the BT/NT relation. A relatedClass relation is defined between the new classes for the RT relation. | + | |Description=The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. A subClassOf relation is defined between the new classes for the BT/NT relation. A relatedClass relation is defined between the new classes for the RT relation. For the UF/USE relations the SynonymOrEquivalence (SOE) pattern is applied. |
| - | |Graphical Representation= | + | |Graphical Representation=recordbasedtermbasedOntologycheck.png |
}} | }} | ||
{{Reengineering OP Proposal Process Template | {{Reengineering OP Proposal Process Template | ||
| Line 51: | Line 53: | ||
2.7. For each one of the above identified thesaurus term tq: | 2.7. For each one of the above identified thesaurus term tq: | ||
| - | 2.7.1. | + | 2.7.1. Apply the SynonymOrEquivalence (SOE) pattern. |
| - | + | |Graphical Representation=wfthbrblocheck.png | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | |Graphical Representation= | + | |
}} | }} | ||
{{Reengineering OP Proposal Scenario Example Template | {{Reengineering OP Proposal Scenario Example Template | ||
|Description=Suppose that someone wants to build a lightweight ontology based on the European Training | |Description=Suppose that someone wants to build a lightweight ontology based on the European Training | ||
Thesaurus (ETT), which is a term-based thesaurus and it follows the record-based model. | Thesaurus (ETT), which is a term-based thesaurus and it follows the record-based model. | ||
| - | |||
}} | }} | ||
{{Reengineering OP Proposal NOR Example Template | {{Reengineering OP Proposal NOR Example Template | ||
| Line 73: | Line 69: | ||
}} | }} | ||
{{Reengineering OP Proposal Ontology Example Template | {{Reengineering OP Proposal Ontology Example Template | ||
| - | |Description=The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. A subClassOf relation is defined between the new classes for the BT/NT relation. A relatedClass relation is defined between the new classes for the RT relation. | + | |Description=The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. A subClassOf relation is defined between the new classes for the BT/NT relation. A relatedClass relation is defined between the new classes for the RT relation. For the UF/USE relations the SynonymOrEquivalence (SOE) pattern Is applied. |
| - | |Graphical Representation= | + | |Graphical Representation=recordbasedtermbasedOntologyETTcheck.png |
}} | }} | ||
{{Reengineering OP Proposal Process Example Template | {{Reengineering OP Proposal Process Example Template | ||
| Line 85: | Line 81: | ||
development. | development. | ||
| - | 4. | + | 4. Assert that achievement is label of the performance class. |
| - | of performance. | + | |
5. Assert that competence is relatedClass of performance. | 5. Assert that competence is relatedClass of performance. | ||
| Line 101: | Line 96: | ||
6.3. Create the success class and assert that success is subClassOf | 6.3. Create the success class and assert that success is subClassOf | ||
performance. | performance. | ||
| - | + | |Graphical Representation=wfthtbrbloexamplecheck.png | |
| - | |Graphical Representation= | + | |
}} | }} | ||
{{Reengineering OP Proposal Additional Information Template | {{Reengineering OP Proposal Additional Information Template | ||
| - | |SubmittedBy=Boris Villazón Terrazas, | + | |SubmittedBy=Boris Villazón Terrazas, |
|Author=Boris Villazón Terrazas | |Author=Boris Villazón Terrazas | ||
| + | |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= | + | |Event=WOP:2009 |
}} | }} | ||
| - | |||
| - | |||
| - | |||
Current revision
| 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 Term-based – record-based model – thesaurus to lightweight ontology In general, it could be useful to visit the evaluation section to have informations about the evaluation process of this proposal Current revision ID: 9709 |
General information
| Name | Term-based – record-based model - thesaurus to lightweight ontology |
|---|---|
| Problem | Re-engineering a term-based thesaurus which follows the record-based
model to design a lightweight ontology. APPLICABILITY The semantics of the relation between narrower and broader terms are subClassOf. |
Non-Ontological Resource
| Description | A non-ontological resource holds a term-based thesaurus which follows the record-based model.
A thesaurus represents the knowledge of a domain with a collection of terms and a limited set of relations between them. The record-based data model is a denormalized structure, uses a record for every term with the information about the term, such as synonyms, broader, narrower and related terms. |
|---|---|
| Graphical Representation |
Diagram
|
Ontology
| Description | The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. A subClassOf relation is defined between the new classes for the BT/NT relation. A relatedClass relation is defined between the new classes for the RT relation. For the UF/USE relations the SynonymOrEquivalence (SOE) pattern is applied. |
|---|---|
| Graphical Representation |
Diagram
|
Process
| Description | 1. Identify the records which contain thesaurus terms without a broader term.
2. For each one of the above identified thesaurus terms ti: 2.1. Create the corresponding ontology class, Ci class, if it is not created yet. 2.2. Identify the thesaurus term, tj , which are narrower terms of ti. They are referenced in the same record which contains ti. 2.3. For each one of the above identified thesaurus term tj : 2.3.1. Create the corresponding ontology class, Cj class, if it is not created yet. 2.3.2. Set up the subClassOf relation between Cj and Ci 2.3.3. Repeat from step 2.2 for cj as a new ci 2.4. Identify the thesaurus term, tr, which are related terms of ti. They are referenced in the same record which contains ti. 2.5. For each one of the above identified thesaurus term tr: 2.5.1. Create the corresponding ontology class, Cr class, if it is not created yet. 2.5.2. Set up the relatedClass relation between Cr and Ci 2.5.3. Repeat from step 2.4 for cr as a new ci 2.6. Identify the thesaurus term, tq, which are equivalent terms of ti. They are referenced in the same record which contains ti. 2.7. For each one of the above identified thesaurus term tq: 2.7.1. Apply the SynonymOrEquivalence (SOE) pattern. |
|---|---|
| Graphical Representation |
Diagram
|
Scenario example
| Description | Suppose that someone wants to build a lightweight ontology based on the European Training
Thesaurus (ETT), which is a term-based thesaurus and it follows the record-based model. |
|---|
Example of a Non-Ontological Resource
| Description | The European Training Thesaurus (ETT) constitutes the controlled vocabulary of reference
in the field of vocational education and training (VET) in Europe. The relation semantics between the sub-ordinate and the super-ordinate concepts is subClassOf. |
|---|---|
| Graphical Representation |
Diagram
|
| Web Reference | http://libserver.cedefop.europa.eu/ett/en/ |
Ontology example
| Description | The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. A subClassOf relation is defined between the new classes for the BT/NT relation. A relatedClass relation is defined between the new classes for the RT relation. For the UF/USE relations the SynonymOrEquivalence (SOE) pattern Is applied. |
|---|---|
| Graphical Representation |
Diagram
|
| Web Reference |
Process example
| Description | 1. Create the learning class and the personal development class.
2. Create the competence class and assert that competence is subClassOf learning. 3. Create the performance class and assert that performance is subClassOf development. 4. Assert that achievement is label of the performance class. 5. Assert that competence is relatedClass of performance. 6. Create the learning class and assert that learning is equivalentClass of competence. 6.1. Create the efficiency class and assert that efficiency is subClassOf performance. 6.2. Create the failure class and assert that failure is subClassOf performance. 6.3. Create the success class and assert that success is subClassOf performance. |
|---|---|
| Graphical Representation |
Diagram
|
About
| SubmittedBy | Boris Villazón Terrazas |
|---|---|
| Author | Boris Villazón Terrazas |
| Also known as | |
| Known uses | |
| Related to | Use the Architectural Pattern: TX-AP-01 |
| Other References |
Additional information
Scenarios
No scenario is added to this Content OP.
Reviews
| Review article | Posted on | About revision (current is 9709) |
|---|---|---|
| PierluigiMiraglia about Term-based thesaurus to lightweight ontology – record-based model | 24550838 September 2009 | 56305,630 |
| MartaSabou about Term-based thesaurus to lightweight ontology – record-based model | 24550838 September 2009 | 57035,703 |
This revision (revision ID 9709) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
| Submission to event |
|---|
