Edit Reengineering OP Proposal Form: Submissions:Term-based – record-based model – thesaurus to lightweight ontology

From Odp

You have to log in to edit pages.

Re-engineering OP Proposal
Example
About
Reviews taken into account
Additional Information
Submitted to event

General Information

Nameinfo.pngThis field is associated with the property Name This property indicates a name for the entity it is associated with. The value of this property is of type String. :
Probleminfo.pngDescription in natural language of the re-engineering problem addressed by the pattern :	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

Descriptioninfo.pngDescription in natural language of the non-ontological resource. :	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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the non-ontological resource. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Ontology

Descriptioninfo.pngDescription in natural language of the output after applying the pattern. :	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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the ontology. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Solution

Descriptioninfo.pngDescription in natural language of the general process, using a sequence of activities. :

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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the sequence of activities. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Scenario

Descriptioninfo.pngDescription in natural language of an example of the re-engineering problem. :	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.

Non-Ontological Resource

Descriptioninfo.pngDescription in natural language of an example of the non-ontological resource. :	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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the non-ontological resource. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :
Web Referenceinfo.pngLink to a website which holds the non-ontological resource. :

Ontology

Descriptioninfo.pngDescription in natural language of an example of the non-ontological resource. :	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 Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the ontology generated. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :
Web reference info.pngLink to a website which holds the ontology generated. :

Solution

Descriptioninfo.pngDescription in natural language of the process applied to the non-ontological resource example, using the sequence of activities described in the pattern :

Graphical Representationinfo.pngThis field has to be assigned with the name of the file (including its extension) that graphically represents the sequence of activities. The image file must be uploaded on the wiki before through the Upload file function that can be accessed through the menu on the left. :

Summary:

This is a minor edit Watch this page

Cancel

Submitted byinfo.pngThis field can be assigned with multiple separated by comma. It is associated with the property submittedBy. This property indicates the ODP user who submitted either a Proposed Content OP, a Content OP, a Modeling Issue, or a Feedback. The value of this property are of type ODPUser. :
Authorinfo.pngThe author of the pattern :
Also known Asinfo.pngThis field can be assigned with multiple values separated by commas. It is associated with the property With this property you can indicate alternative names (if any) for the Ontology Design Pattern. The values of this property are of type String. :
Known usesinfo.pngThis field can be assigned with multiple values separated by commas. It is associated with the property KnownUse This property indicates existing ontologies where the Content OP is used as a building block. Note that such ontologies are different from the ontologies where the Content OP is extracted from (see the ExtractedFrom property). The value of this property is of type URL. This property is a subproperty of Property:PatternUsage. :
Related toinfo.pngThis field can be assigned with multiple values separated by commas. It is associated with the property This property is of type Page. :
Other Referencesinfo.pngLEGACY: DO NOT USE. Migrate existing references to new format. This field can be assigned with multiple values separated by commas. It is associated with the property Property:Reference :

Edit Reengineering OP Proposal Form: Submissions:Term-based – record-based model – thesaurus to lightweight ontology

From Odp

Views

Personal tools

Navigation

Contribute

Help

Catalogues

Quality Committee

Content OP publishers

Editorial Board

Administrator

WOP

Search

Toolbox