W3C home > Mailing lists > Public > www-webont-wg@w3.org > September 2002

Re: ISSUE 5.6 - daml:imports as magic syntax

From: Jeff Heflin <heflin@cse.lehigh.edu>
Date: Tue, 10 Sep 2002 16:22:04 -0400
Message-ID: <3D7E546C.2768357C@cse.lehigh.edu>
To: "Peter F. Patel-Schneider" <pfps@research.bell-labs.com>
CC: www-webont-wg@w3.org

Peter,

Please see my responses inline below...

"Peter F. Patel-Schneider" wrote:
> 
> A very good summary of daml/owl:imports.
> 
> From: Jeff Heflin <heflin@cse.lehigh.edu>
> Subject: ISSUE 5.6 - daml:imports as magic syntax
> Date: Mon, 09 Sep 2002 17:23:46 -0400
> 
> > Problem:
> > --------
> > If daml:imports is just another RDF or OWL property, then users can
> > place restrictions, etc. on it. For example, consider a situation where
> > there was a max cardinality of 1 on imports. If an ontology imported two
> > or more ontologies, then this would effectively say that the ontologies
> > are equivalent. It is probably best to avoid such situations.
> >
> > Possible Solution:
> > ------------------
> > This seems to indicate that imports should be a "dark" property. Note
> > that this isn't an issue in the Abstract Syntax, since in it, everything
> > is essentially "dark."
> 
> A treatment of imports can be done completely syntactically, by replacing
> imports foo, where foo is a URI (or whatever) by the contents of the
> document pointed at by foo.   This is the way I would handle it in the
> abstract syntax and direct semantics.

Although imports could be treated syntactically (kind of like a
"#include" directive), I think that would be a big mistake.  The point
of imports is that knowledge from another source applies to the resource
in which it is expressed. The Semantic Web is fundamentally about
distributed ontologies and data sources, and as such its semantics
should discuss these things explicitly. A syntactic fix obscures one of
the things that differentiates the Semantic Web from traditional logic
approaches. Ontologies and the interrelationships between them are
important; they aren't just things to be swept under the rug.
 
> > In Pat Hayes' recent OWL model theory, it should
> > be sufficient to say that owl:imports is not an instance of owl:Object,
> > owl:DatatypeValue, owl:Class, owl:ObjectProperty, or
> > owl:DataTypeProperty. However, it would still be an rdfs:Property, but
> > any RDF graph that uses it as a subject or object would not be
> > well-formed OWL/RDF. Note, owl:imports doesn't fit into any of the
> > classifications in the table in section 2 of the Hayes model theory, so
> > perhaps a new classification called metaproperty or such is needed.
> 
> Even in this separated treatment, imports is problematic.  It would require
> a completely new kind of semantic rule, and one that brings new kinds of
> things into the semantics.

Sure this semantic rule is a little different from the kind that we
already have considered, but I don't think it would break things or make
them more confusing. In fact, I think it would illucidate how knowledge
sharing actually works on the Semantic Web.

> > Semantics:
> > ----------
> > It is important that the semantics of owl:imports be added to any
> > semantics documents. To do this, we need to be able to refer to sets of
> > OWL statements (such as a web page, a database with an OWL interface,
> > etc.) This could probably be called a resource, but that term is also
> > used to describe RDF instances, so for lack of a better term, I will
> > choose the term graph for the time being. Let graph be a function from a
> > URI (URL?) to an RDF/OWL graph. Each OWL graph has a set of entailments
> > that are determined by the model theory. The semantics of a statement:
> >
> > A owl:imports B.
> >
> > are:
> >
> > if graph(B) |= X then graph(A) |= X
> >
> > (Note: Here, "|=" is the OWL entailment relation)
> 
> This adds in a lot of error-prone machinery.

What is error prone about it? This simply says that anything entailed by
the ontology denoted by B is also entailed by the ontology denoted by A.

> > One question is whether we need something more specific in the model
> > theory that, for example, uses ICEXT and IEXT.
> 
> Something more is needed.  In particular, a relationship between the
> current graph and its name is needed.  Otherwise how can the condition
> be discharged in the conditional above?

The relationship can be implmented by using the HTTP GET function to
fetch the contents at the URL and then parsing it based on OWL
semantics. I don't see what the problem is.

> > Any comments or suggestions?
> >
> > Jeff
> 
> Note that the DAML+OIL axiomatization does not handle imports at all.
> 
> peter
Received on Tuesday, 10 September 2002 16:22:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:52 GMT