adding some references about mapping definitions
This commit is contained in:
parent
f99be4d3a3
commit
31de87dfca
|
@ -36,6 +36,26 @@
|
||||||
bibsource = {dblp computer science bibliography, https://dblp.org}
|
bibsource = {dblp computer science bibliography, https://dblp.org}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@MISC{atl,
|
||||||
|
title = {ATL - A model transformation technology},
|
||||||
|
note={\url{https://www.eclipse.org/atl/}},
|
||||||
|
author = {Eclipse Fondation}
|
||||||
|
}
|
||||||
|
|
||||||
|
@inproceedings{BGPP95,
|
||||||
|
author = {Yamine A{\"{\i}}t Ameur and
|
||||||
|
Frederic Besnard and
|
||||||
|
Patrick Girard and
|
||||||
|
Guy Pierra and
|
||||||
|
Jean{-}Claude Potier},
|
||||||
|
title = {Formal Specification and Metaprogramming in the {EXPRESS} Language},
|
||||||
|
booktitle = {SEKE'95, The 7th International Conference on Software Engineering
|
||||||
|
and Knowledge Engineering, June 22-24, 1995, Rockville, Maryland,
|
||||||
|
USA, Proceedings},
|
||||||
|
pages = {181--188},
|
||||||
|
publisher = {Knowledge Systems Institute},
|
||||||
|
year = {1995}
|
||||||
|
}
|
||||||
|
|
||||||
@MISC{owl2012,
|
@MISC{owl2012,
|
||||||
title = {OWL 2 Web Ontology Language},
|
title = {OWL 2 Web Ontology Language},
|
||||||
|
|
|
@ -1039,9 +1039,10 @@ definition Computer_Hardware_to_Hardware_morphism :: "'a Computer_Hardware_schem
|
||||||
|
|
||||||
|
|
||||||
To check the coherence of our local ontology, we define a relationship between the local ontology
|
To check the coherence of our local ontology, we define a relationship between the local ontology
|
||||||
and the reference ontology using morphism functions (or mapping rules). These rules are applied to
|
and the reference ontology using morphism functions (or mapping rules as in ATL framwork~@{cite "atl"}
|
||||||
define the relationship between one class of the local ontology to one or several other class(es)
|
or EXPRESS-X language~@{cite "BGPP95"}). These rules are applied to define the relationship
|
||||||
described in the reference ontology.
|
between one class of the local ontology to one or several other class(es) described in the reference
|
||||||
|
ontology.
|
||||||
|
|
||||||
For example, \<^const>\<open>Product_to_Component_morphism\<close> and \<^const>\<open>Computer_Hardware_to_Hardware_morphism\<close>
|
For example, \<^const>\<open>Product_to_Component_morphism\<close> and \<^const>\<open>Computer_Hardware_to_Hardware_morphism\<close>
|
||||||
definitions, detailed in \autoref{fig-mapping-example},
|
definitions, detailed in \autoref{fig-mapping-example},
|
||||||
|
@ -1051,6 +1052,10 @@ This mapping shows that the structure of a (user) ontology may be quite differen
|
||||||
from the one of a standard ontology it references.
|
from the one of a standard ontology it references.
|
||||||
\<close>
|
\<close>
|
||||||
|
|
||||||
|
text\<open>
|
||||||
|
The advantage of using the \<^dof> framework compared to approaches like ATL or EXPRESS-X is
|
||||||
|
the possibility of formally validating the mapping rules and also of proving the preservation
|
||||||
|
of invariants, as we will demonstrate in the following example.\<close>
|
||||||
|
|
||||||
(* Bu, can you take care of commenting on these last lemmas? *)
|
(* Bu, can you take care of commenting on these last lemmas? *)
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue