m (Review has been assigned.)
m (Text replace - 'WOP2009:Main' to 'WOP:2009')
 
(8 intermediate revisions by 5 users 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 thesaurus to lightweight ontology – record-based model
+
|Name=Term-based – record-based model - thesaurus to lightweight ontology
|Problem=re-engineering a term-based thesaurus which follows the record-based
+
|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. An equivalentClass relation is defined between the new classes for the UF/USE 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=recordbasedtermbasedOntology.png
+
|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. Create the corresponding ontology class, Cq class, if it is not created yet.
+
2.7.1. Apply the SynonymOrEquivalence (SOE) pattern.
 
+
|Graphical Representation=wfthbrblocheck.png
2.7.2. Set up the equivalentClass relation between Cq and Ci
+
 
+
2.7.3. Repeat from step 2.6 for cq as a new ci.
+
 
+
|Graphical Representation=wfthbrblo.png
+
 
}}
 
}}
 
{{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. An equivalentClass relation is defined between the new classes for the UF/USE 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=recordbasedtermbasedOntologyETT.png
+
|Graphical Representation=recordbasedtermbasedOntologyETTcheck.png
 
}}
 
}}
 
{{Reengineering OP Proposal Process Example Template
 
{{Reengineering OP Proposal Process Example Template
Line 85: Line 81:
 
development.
 
development.
  
4. Create the achievement class and assert that achievement is equivalentClass
+
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=wfthtbrbloexample.png
+
 
}}
 
}}
 
{{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=WOP2009:Main
+
|Event=WOP:2009
 
}}
 
}}
[[Category:Review assigned]]
 
[[Category:Review assigned]]
 
[[Category:Review assigned]]
 

Latest revision as of 08:30, 31 May 2010

Retrieved from ""
The page [[Bootstrap:Footer]] was not found.