| Line 21: | Line 21: | ||
[[Image:NormalizationGenericStructure1.png|Generic structure of the Normalization ODP used to represent a FCS.]] | [[Image:NormalizationGenericStructure1.png|Generic structure of the Normalization ODP used to represent a FCS.]] | ||
| − | The figure below represents a further generalization of the Normalization ODP and introduces the following notation: | + | The figure below represents a further generalization of the [[Submissions:Normalization|Normalization]] ODP and introduces the following notation: |
* '':TDC'' denotes a primitive class representing the domain concept being normalized. | * '':TDC'' denotes a primitive class representing the domain concept being normalized. | ||
* '':Module_i'' denotes a primitive class that represents one of the modules. | * '':Module_i'' denotes a primitive class that represents one of the modules. | ||
| Line 27: | Line 27: | ||
* '':hasModule_i'' denotes an object property that links every module '':Module_i'' to the different subclasses of the target domain concept '':M_iClass_jTDC'' and '':SpecificTDC_x''. | * '':hasModule_i'' denotes an object property that links every module '':Module_i'' to the different subclasses of the target domain concept '':M_iClass_jTDC'' and '':SpecificTDC_x''. | ||
* '':M_iClass_jTDC'' denotes a defined class that represents a subset of the target domain concept class '':TDC''. Every class '':M_iClass_jTDC'' is defined based on its relationship to the single corresponding class '':M_iClass_j'' that it is derived from. | * '':M_iClass_jTDC'' denotes a defined class that represents a subset of the target domain concept class '':TDC''. Every class '':M_iClass_jTDC'' is defined based on its relationship to the single corresponding class '':M_iClass_j'' that it is derived from. | ||
| − | * '':SpecificTDC_x'' denotes a primitive class that represents a subset of the target domain concept class '':TDC'' and an entity from the domain to be classified. Every class '':SpecificTDC_x'' is described based on its relationship to various classes '':M_iClass_j'' from potentially different modules. As a consequence of this relationship, the classes '':SpecificTDC_x'' could introduce the polyhierarchy scenarios in the ontology model that the Normalization ODP aims to manage and untangle. | + | * '':SpecificTDC_x'' denotes a primitive class that represents a subset of the target domain concept class '':TDC'' and an entity from the domain to be classified. Every class '':SpecificTDC_x'' is described based on its relationship to various classes '':M_iClass_j'' from potentially different modules. As a consequence of this relationship, the classes '':SpecificTDC_x'' could introduce the polyhierarchy scenarios in the ontology model that the [[Submissions:Normalization|Normalization]] ODP aims to manage and untangle. |
|Graphical Representation=NormalizationGenericStructure2.png | |Graphical Representation=NormalizationGenericStructure2.png | ||
}} | }} | ||
{{Reengineering OP Proposal Process Template | {{Reengineering OP Proposal Process Template | ||
| − | |Description=Mapping between the elements in the generic structure of a Faceted Classification Scheme and the Normalization ODP. | + | |Description=Mapping between the elements in the generic structure of a Faceted Classification Scheme and the [[Submissions:Normalization|Normalization]] ODP. |
| − | Based on the principle of representating each facet of a FCS as a module of the Normalization ODP, the underlying ideas behind the mappings in the figure(table) below can be outlined as follows: | + | Based on the principle of representating each facet of a FCS as a module of the [[Submissions:Normalization|Normalization]] ODP, the underlying ideas behind the mappings in the figure(table) below can be outlined as follows: |
| − | * The target domain concept ''TDC'' represents the domain of discourse of both a FCS and the Normalization ODP. The primitive class '':TDC'' fulfills that role in the normalized ontology. | + | * The target domain concept ''TDC'' represents the domain of discourse of both a FCS and the [[Submissions:Normalization|Normalization]] ODP. The primitive class '':TDC'' fulfills that role in the normalized ontology. |
| − | * A facet ''Facet_i'' from a generic FCS corresponds to a module '':Module_i'' in the Normalization ODP, therefore it becomes a primitive class '':Facet_i'' in the normalized ontology model. | + | * A facet ''Facet_i'' from a generic FCS corresponds to a module '':Module_i'' in the [[Submissions:Normalization|Normalization]] ODP, therefore it becomes a primitive class '':Facet_i'' in the normalized ontology model. |
| − | * A facet ''Facet_i'' from a FCS also becomes an object property '':hasFacet_i'' in the normalized ontology, given that for every module '':Module_i'' in the Normalization ODP, there is an object property '':has_Module_i''. | + | * A facet ''Facet_i'' from a FCS also becomes an object property '':hasFacet_i'' in the normalized ontology, given that for every module '':Module_i'' in the [[Submissions:Normalization|Normalization]] ODP, there is an object property '':has_Module_i''. |
| − | * From the relationship between facet and module, it follows that a facet term ''F_iTerm_j'' from a FCS maps to a module subclass '':M_iClass_j'' from the Normalization ODP. Both elements represents the same notion in their respective conceptual models. A subvidision, a refinement of the facet or module that they complement respectively. Therefore, a facet term ''F_iTerm_j'' from a FCS becomes a primitive class '':F_iTerm_j'' in the normalized ontology. | + | * From the relationship between facet and module, it follows that a facet term ''F_iTerm_j'' from a FCS maps to a module subclass '':M_iClass_j'' from the [[Submissions:Normalization|Normalization]] ODP. Both elements represents the same notion in their respective conceptual models. A subvidision, a refinement of the facet or module that they complement respectively. Therefore, a facet term ''F_iTerm_j'' from a FCS becomes a primitive class '':F_iTerm_j'' in the normalized ontology. |
| − | * A facet term ''F_iTerm_j'' from a FCS also produces a defined class '':F_iTerm_jTDC'' in the normalized ontology, given that for every primitive class '':M_iClass_j'' in the Normalization ODP, there is a corresponding defined class '':M_iClass_jTDC''. | + | * A facet term ''F_iTerm_j'' from a FCS also produces a defined class '':F_iTerm_jTDC'' in the normalized ontology, given that for every primitive class '':M_iClass_j'' in the [[Submissions:Normalization|Normalization]] ODP, there is a corresponding defined class '':M_iClass_jTDC''. |
| − | * Every item ''Item_x'' to be classified in the FCS aligns to a class '':Specific_x'' that is automatically classified by a reasoner in the Normalization ODP. Therefore, every element ''Item_x'' is represented as a primitive class '':SpecificTDC_x'' in the normalized ontology. | + | * Every item ''Item_x'' to be classified in the FCS aligns to a class '':Specific_x'' that is automatically classified by a reasoner in the [[Submissions:Normalization|Normalization]] ODP. Therefore, every element ''Item_x'' is represented as a primitive class '':SpecificTDC_x'' in the normalized ontology. |
[[Image:MappingFCSNormalizationODP.png]] | [[Image:MappingFCSNormalizationODP.png]] | ||
|
Last modified date is: 2010-09-06 |
| Name | Faceted Classification Scheme (FCS) |
|---|---|
| Problem | Ontological representation of a specific domain concept conceptualized using a Faceted Classification Scheme (FCS). |
| Description | A FCS is defined as: "a set of mutually exclusive and jointly exhaustive categories, each made by isolating one perspective on the items (a facet), that combine to completely describe all the objects in question, and which users can use, by searching and browsing, to find what they need" (Denton, 2003).
The following notation is introduced to refer to the elements of a generic FCS in the figure below:
|
|---|---|
| Graphical Representation |
Diagram
|
| Description | Generic structure of the Normalization ODP used to represent a Faceted Classification Scheme.
The symbol (≡) denotes an OWL defined class.
The figure below represents a further generalization of the Normalization ODP and introduces the following notation:
|
|---|---|
| Graphical Representation |
Diagram
|
| Description | Mapping between the elements in the generic structure of a Faceted Classification Scheme and the Normalization ODP.
Based on the principle of representating each facet of a FCS as a module of the Normalization ODP, the underlying ideas behind the mappings in the figure(table) below can be outlined as follows:
[[Image:MappingFCSNormalizationODP.png |
|---|---|
| Graphical Representation |
Diagram
|
| Description | To create an ontology model to represent an existing Faceted Classification Scheme for a specific domain concept. |
|---|
| Description | The figure below recaps the final FCS developed for the "Dishwashing Detergent" domain example in (Denton, 2003)(§ 2.4). The elements of the schema fit into the generic structure of a FCS presented in section Non-Ontological Resource earlier, where:
|
|---|---|
| Graphical Representation |
Diagram
|
| Web Reference | http://www.miskatonic.org/library/facet-web-howto.html |
| Description | OWL representation of the "Dishwashing Detergent" domain concept Faceted Classification Scheme applying the Normalization ODP.
The symbol (≡) denotes an OWL defined class. [[Image:FacetedClassificationSchemeOntoExObjProp.png |
|---|---|
| Graphical Representation |
Diagram
|
| Web Reference | http://dl.dropbox.com/u/1666716/Attachments/detergent_fcs_normalisation_prot3x_owl.owl |
| Description | Using the mappings from the table. |
|---|---|
| Graphical Representation |
Diagram
|
| SubmittedBy | BenedictoRodriguezCastro |
|---|---|
| Author | BenedictoRodriguezCastro, HughGlaser, LesCarr |
| Also known as | |
| Known uses | |
| Related to | Submissions:Normalization, Submissions:Partition, Submissions:ClassAsPropertyValue |
| Other References |
No scenario is added to this Content OP.
This revision (revision ID 10019) takes in account the reviews: none
Other info at evaluation tab
|
Submission to event |
|---|
'Ontology Design Patterns'
