warning label

• Previous message: Benjamin Grosof: "more thoughts on evolution of Rules Lite syntax"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

As I promised during Tuesday's telecon, here's the first
draft of a "warning label" intended as a new section in [1].
Additions, corrections, and other suggestions are welcome.

	Mike

[1] http://www.cs.man.ac.uk/~horrocks/DAML/Rules/


6.0  Usage Suggestions

At least in the near term until OWL reasoners begin to
support OWL Rules directly, users who want to maximize
interoperability with existing rule engines and OWL
ontologies encoded in RDF/XML may want to limit their
classAtoms to use named classes defined in the same OWL XML
file or external OWL XML or RDF/XML documents, e.g. use

  <owlx:classAtom>
    <owlx:Class owlx:name="#PhysicianChild"/>
    <owlx:Variable owlx:name="x1"/>
  </owlx:classAtom>

with

  <owlx:Class owlx:name="PhysicianChild">
    <owlx:IntersectionOf>
      <owlx:Class owlx:name="#Person"/>
      <owlx:ObjectRestriction owlx:property="#hasParent"/>
        <owlx:someValuesFrom owlx:class="#Physician"/>
      </owlx:ObjectRestriction>
    </owlx:IntersectionOf>
  </owlx:Class>

rather than

  <owlx:classAtom>
    <owlx:Class owlx:name="PhysicianChild">
      <owlx:IntersectionOf>
        <owlx:Class owlx:name="#Person"/>
        <owlx:ObjectRestriction owlx:property="#hasParent">
          <owlx:someValuesFrom owlx:class="#Physician"/>
        </owlx:ObjectRestriction>
      </owlx:IntersectionOf>
    </owlx:Class>
    <owlx:Variable owlx:name="x1"/>
  </owlx:classAtom>

as this allows simpler translation of atoms into other rule
formats.

Users anticipating use of their rules with prioritized
conflict resolution, defaults, procedural attachments, or
other advanced features of rule engines based on Logic
Programming may want to limit their classAtoms to use named
classes within the expressiveness of Description Logic
Programs [Grosof 2003].  This limits [Benjamin fill in
here].

An example of an OWL class outside the expressiveness of
Description Logic Programs is

  <owlx:Class owlx:name="Orphan">
    <owlx:IntersectionOf>
      <owlx:Class rdf:name="#Person"/>
      <owlx:ObjectRestriction owlx:property="#hasParent"/>
        <owlx:allValuesFrom owlx:class="#Deceased"/>
      </owlx:ObjectRestriction>
    </owlx:IntersectionOf>
  </owlx:Class>

because of the use of owl:allValuesFrom.  Use of such a
class within a classAtom may cause difficulties in future
versions of OWL Rules.

Development of theoretical foundations and algorithms to
more fully combine the results of Description Logic and
Logic Programming is an active area of research.  OWL Rules
is expected to grow as such research comes to fruition.

Tools to convert between OWL Rules and RuleML 0.8 [RuleML] are
being developed.


[Grosof03]
	Description Logic Programs:  Combining Logic
	Programs with Description Logic.  Benjamin Grosof,
	Ian Horrocks, Raphael Volz, Stefan Decker.  Proc.
	WWW2003, Budapest, May 2003.
	http://www2003.org/cdrom/papers/refereed/p117/p117-grosof.html

[RuleML]
	http://www.ruleml.org

• Next message: Mike Dean: "Jacob Bloomfield Grosof birth announcement"
• Previous message: Benjamin Grosof: "more thoughts on evolution of Rules Lite syntax"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.4 : 10/05/03 EST