4
10/20/2003 Raphaël Troncy - EON'20033 DOE: methodology implementation Writing of differential principles according to differential semantics Formal definition of concepts and relations, specification of their arity and domains, introduction of individuals Export into commonly-used ontology languages Formalization step Operationalization step DOE: help for taxonomy structuring The ontology has to be more formalized: using other editors (Protégé-like) Export mechanisms are a necessity

5
10/20/2003 Raphaël Troncy - EON'20034 DOE and the travel ontology

6
10/20/2003 Raphaël Troncy - EON'20035 Using XSLT for the import/export Most proposed languages for encoding ontologies are based on XML XSLT is meant to transform an XML document into another one XSLT seems to be adapted to perform the transformations of XML ontologies from one representation language to another

13
10/20/2003 Raphaël Troncy - EON' Interoperability via OWL (3/3) { Protégé, OilEd, WebODE }  DOE Moreover, two possible syntaxes: –OWL Presentation Syntax : exported but not imported –OWL Exchange Syntax (RDF-XML): DOE does not import instances … and OilEd mixes them Similar treatment difficulties: here again, it is necessary to deal with every possibility to import ontologies A little part of OWL expressiveness is used  the loop is more or less made with OWL

15
10/20/2003 Raphaël Troncy - EON' Conclusion The model of DOE is simple so ontologies can be easily exported to other environments XSLT enables satisfying exports to other ontological frameworks Import mechanism faces more problems linked with: –theoretical considerations (weak formal expressiveness) –Implementation shortfalls (XSLT limits) –Semantic Web standards (multiple syntaxes)  But the interoperability is quite successful  More important : the interoperability we aimed at is properly and simply dealt with

16
10/20/2003 Raphaël Troncy - EON' Proposition for further experiments The tool (and language ?) community has still work to do in order to achieve interoperability Proposition: –establish benchmarks, with every possible syntactic representation and semantics expressivity –systematize all the tests, between each environment, at the syntax level –systematize all the tests, between each environment, at the semantics level