From NeOn Wiki
|Current Version||[[current version:= <ask format="template" template="CurrentVersion" limit="1" searchlabel="" sort="version number" order="descending" default="no version available"> 1.x/Ontology Mapping *</ask>]]|
|Homepage||[http://neon-project.org/resources/NeOnToolkit/ 1.x/Ontology Mapping Website]|
|License||Free for non-commercial use|
The mapping plugin is needed to build mappings and correlations between two or more F-logic ontologies. This plugin features graphical construction and representation of dependencies between ontologies.
OntoMap is a plug-in for the ontology-management platform NeOn Toolkit that supports the creation and management of ontology mappings via a graphical interface. Mappings can be specified based on graphical representation, using a schema-view of the respective ontologies. Users just have to understand the semantics of the graphical representation (e.g. an arrow connecting two concepts), they do not have worry about the logical representation of mappings. The user of OntoMap is supported by drag-and-drop functionality and simple consistency checks on property-mappings (automatic suggestion of necessary class-mappings) .
Before start a mapping keep this in mind: OntoMap allows the creation of different "Mapping" types (concept to concept, property to concept, property to property Before you can map attributes and/or relations to the target ontology, there must exist an attribute-concept or a concept-concept "Mapping", which specifies the identifier for the mapped instances within the Target ontology Filters can be specified for "concept-to-concept"- and "attribute-to-concept"-mappings and gives the user the possibility to limit those mapped instances over their characteristic values.
Action Buttons for mapping
1. opens a dialog to select a source ontology 2. opens a dialog to select a target ontology 3. shows/hides all attributes and relations of the ontologies
To create mapping switch to the integration perspective and drag&drop the source and target ontologies from the ontology navigator into the conecpt-tree of the mapping view. Within the concept tree the concept hierarchy of the ontology is visualized. When selecting a concept its attributes and relations are showen within the concept detail tree, categorized to their direct top concepts. The instances of the selected concept are listed within the instance table when the 'Link Instances with concept tree'-button is pushed or after the 'Refresh Instances'-butoon is cklicked.
To create a mapping between two concepts just drag&drop a concept from the source ontology (left-hand-side) onto a concept from the target ontology (right-hand-side). Another way to create mappings is to use a mapping template. Mapping templates are suggested in the mapping pane. Depending of the actual selection within the source and target ontology different templates are proposed. When choosing a template the system guides the user through the mapping definition process. In this process the user can fill in all necessary parameters needed for the mapping creation.
By creating a filter within the mapping pane it's possible to map only instances which hold for the given filter criteria. Further more the properties to be mapped can be specified by drag&drop from the source to the target property.
For property mappings it is possible to define a transformation during the mapping process. Therefore a transformation editor for the actual selected property mappings can be chosen within the mapping pane.
Within the instance table the outcome of the mapping process can be watched.
Relation-Shortcut-Pattern The 'Relation-Shortcut-Pattern' maps two source concepts with related intermediate concepts to two target concepts related directly E.g. within the target ontology ‘Car’ has a direct relation ‘hasWheels’ to the concept ‘Wheel’ whereas the relation between ‘Car’ and ‘Wheel’ in the source ontology is expressed by an intermediate concept ‘Chassis’
Attribute-To-Relation-Instance-Pattern The 'Attribute-To-Relation-Instance-Pattern' maps an attribute value to a relation by creating an instance of the target relation range with an corresponding attribute value E.g. the values for the source attribute ‘engine’ are mapped as instances of ‘Engine’ and values of the target attribute ‘type’ and the relation ‘hasEngine’ for the target concept ‘Car’
Note (this is important for the work with collaboration server):Mappings created within one client are not visible within other clients until a refresh on the Ontology Navigator has been done. This only holds for Collaboration Server.