Changes between Version 7 and Version 8 of AlignmentOntology


Ignore:
Timestamp:
07/04/06 11:15:49 (18 years ago)
Author:
endres
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AlignmentOntology

    v7 v8  
    1818== Integration/Alignment with other alignment ontologies == 
    1919 
     20=== Lockheed Martin Alignment === 
    2021An alignment between our AlignmentOntology and the [http://www.atl.lmco.com/projects/ontology/ Lockheed Martin ATL] [http://www.atl.lmco.com/projects/ontology/ontologies/core/alignment/Alignment.owl alignment specification] is given by the file [repos:trunk/PhaseLibs/AlignmentOntology/LMCOAlignment.rdf LMCOAlignment.rdf]. This file specifies the alignment using both schemes at the same time. 
    2122 
     23=== SKOS Mapping === 
     24The [http://www.w3.org/2004/02/skos/mapping/spec/ SKOS Mapping Vocabulary] defines mappings between topic maps. However, their scheme is not semantically equivalent to our alignment concept, since they use a set theory based approach on the documents attached to their concepts. Thus, the transformation of a SKOS mapping into a PhaseLibs alignment or vice versa is semantically questionable. 
     25 
     26In order to transform a set of simple (one-to-many) SKOS mappings you can do the following: 
     27 * the various degrees of matches can be mapped to the confidence property  
     28 * flat AND bag constructs can be transformed to refer instead to an artificial subclasse of the given class conjunction.   
     29 * flat OR bag constructs can be expressed by a number of Superordination/Subsumption relations. 
     30 * NOT constructs can be expressed by a number of Distinctions. 
    2231 
    2332== Ontology Description ==