- From: Dan Connolly <connolly@w3.org>
- Date: 05 Mar 2003 09:16:05 -0500
- To: "Peter F. "Patel-Schneider <pfps@research.bell-labs.com>
- Cc: Jim Hendler <hendler@cs.umd.edu>, www-rdf-logic@w3.org
On Wed, 2003-03-05 at 09:03, Peter F. Patel-Schneider wrote:
[...]
> In OWL Full, as in RDF, data values cannot be subjects of triples, so,
> although it could make sense to have a property whose domain was zipcodes,
> you can do very little with it.
Not currently; but I expect that limitation to be addressed, in
due course.
"Resolution: On the 15th February 2002, at the RDFCore WG telecon, the
WG:
* resolved that the current syntaxes (RDF/XML, n-triples, graph
syntax) do not allow literals as subjects.
* noted that it is aware of no reason why literals should not be
subjects and a future WG with a less restrictive charter may extend the
syntaxes to allow literals as the subjects of statements."
-- http://www.w3.org/2000/03/rdf-tracking/#rdfms-literalsubjects
So I don't see any reason why owl:SymmetricProperty should
be constrained to be a subclass of owl:ObjectProperty.
> In particular, the ``triples'' you use
> below are not allowable in RDF.
>
> > i.e.
> >
> > if zipcode is a datatype property
> > and SameStateAs is a property with range:zipcode, domain:zipcode
> > then saying
>
> > SameStateAs is transitive is useful
> >
> > i.e.
> >
> > 20852 SameStateAs 20740
> > 20740 SameStateAs 20861
> >
> > therefore
> > 20852 SameStateAs 20861
> >
> > so I don't need an interstate shipping permit if sending a package
> > between 20852 and 20861.
> > -JH
> > p.s. note that I cannot actually define a zipcode in OWL based on the
> > stuff about derived classes. Assume, therefore, I just use
> > xsd:nonNegativeInteger and am careful to use only legal zipcodes.
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Wednesday, 5 March 2003 09:16:08 UTC