That's indeed very hard to do. (01)
However, there is a very simple solution: one can simply create a Tag in XML
called, perhaps <kif: encoding>. The KIF code can then be stored there and
retrieved for use at will. (02)
Shiang-yu Lee, Ph. D.
Architecture and eBusiness, Information Systems
Boeing Commercial Airplanes (03)
P.O. Box 3707, M/S 2R-97
Seattle, WA 98124-2207
(206)-544-5252 (phone)
206)-544-5889 (fax)
email: shiang-yu.lee@xxxxxxxxxx (04)
-----Original Message-----
From: Adam Pease [mailto:apease@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, November 20, 2002 9:07 AM
To: ontolog@xxxxxxxxxxxxxxx
Cc: 'Christian Fillies'
Subject: Re: [ontolog] ontology tools and an ontology repository? (05)
Martin,
While that might be true in general, could you describe how an axiom in
first order logic could be translated into another formalism using
XSL? Translating SUMO for use in the SNARK theorem prover required
renaming predicates in the ontology itself, quoting certain kinds of
statements, and treating certain kinds of variables as macro statements
that require expansion. Translating SUMO for use in Protege would require
first detecting and then throwing away axioms such as the one below. At
that level of complexity I wonder what the advantage is of using a
scripting language like XSL over a full-blown programming language with
good string-processing support like Perl or Java? And why the penalty of a
far more verbose encoding is worth the trouble.
The point I'm converging on here is that it's all well and good to say
an XML encoding is a Good Thing, but we should be clear on why, and in
which use cases. (06)
Adam (07)
At 08:54 AM 11/20/2002 +0000, Martin Bryan wrote:
>Adam Pease wrote;
> > One could
> > just have a start and end tag around a KIF expression and that would be
a
> > valid XML document
> >
> > <kif>
> > (=>
> > (instance ?X Horse)
> > (exists (?Y)
> > (and
> > (instance ?Y Head-PartOfBody)
> > (part ?X ?Y))))
> > </kif>
> >
> > What would that sort of encoding allow or prohibit that the more
extensive
> > XML encoding that I provided below wouldn't?
>
>Adopting such an approach would make it impossible to use XSL
>Transformations to subset the KIF data, or to transform it into another
>format. By adopting a more complex XML representation for the KIF
statements
>you can begin to use standard transformation tools to subset your KIF
>statements into a form that could be used in other environments.
>
>Martin Bryan
>
>The SGML Centre, 29 Oldbury Orchard, Churchdown, Glos GL3 2PU, UK
>Phone/Fax: +44 1452 714029 E-mail: mtbryan@xxxxxxxxxxxxxx
>
>For further details about The SGML Centre visit http://www.sgml.u-net.com
> (08)
><implies>
> > > > > <antecedent>
> > > > > <clause>
> > > > > <predicate value="instance">
> > > > > <argument number=1 value="?X">
> > > > > <argument number=2 value="Horse">
> > > > > </clause>
> > > > > </antecedent>
> > > > > <consequent>
> > > > > <existential>
> > > > > <varlist><var name="?Y"></varlist>
> > > > > <and>
> > > > > <clause>
> > > > > <predicate value="instance">
> > > > > <argument number=1 value="?Y">
> > > > > <argument number=2 value="Head-PartOfBody">
> > > > > </clause>
> > > > > <clause>
> > > > > <predicate value="part">
> > > > > <argument number=1 value="?x">
> > > > > <argument number=2 value="?Y">
> > > > > </clause>
> > > > > </and>
> > > > > </existential>
> > > > > </consequent>
> > > > > </implies> (09)
--
To post messages mailto:ontolog@xxxxxxxxxxxxxxx
An archive of the [ontolog] forum can be found
at http://ontolog.cim3.org/forums/ontolog
--
To post messages mailto:ontolog@xxxxxxxxxxxxxxx
An archive of the [ontolog] forum can be found
at http://ontolog.cim3.org/forums/ontolog (010)
|