W3C home > Mailing lists > Public > www-tag@w3.org > April 2005

Re: httpRange-14: some dimensions of space of positions

From: Dan Connolly <connolly@w3.org>
Date: Fri, 29 Apr 2005 10:34:17 -0500
To: Harry Halpin <hhalpin@ibiblio.org>
Cc: www-tag <www-tag@w3.org>
Message-Id: <1114788857.3004.672.camel@localhost>

On Fri, 2005-04-29 at 10:53 -0400, Harry Halpin wrote:
> Clarifying the space of possible positions is *always* useful.
> On Thu, 28 Apr 2005, Dan Connolly wrote:
> > I think OWL is a standardized (and good) far-context mechanism.
> > far in the sense of possibly-far, i.e. arbitrarily-near-or-far...
> > it may be nearby or widely known/cached.
>  	OWL is good, but still misses the point sometimes. If you just
> make a new OWL statement that says
> http://www.example.org/PatHayes ex:Denotes "Pat Hayes"
> doesn't really work, cause sometimes Pat Hayes is Patrick Hayes,
> and "Pat Hayes" sure looks like an arbitrary string to me :)

What I'm suggesting is that you can coin terms for
the class "person" (or "agent") and the class "document",
say that they're disjoint, and say that something
is in one of them (and hence not the other), hence
disambiguating between a person an their homepage.

I can write this to say that I mean for
http://www.example.org/PatHayes to denote his homepage:

  foaf:homepage a owl:InverseFunctionalProperty;
    rdfs:domain foaf:Agent;
    foaf:range foaf:Document.
  foaf:Agent owl:disjointFrom foaf:Document.

  _:somebody foaf:homepage <http://www.example.org/PatHayes>.

And if somebody else writes

  adams:HoopyFrood rdfs:subClassOf foaf:Agent.
  <http://www.example.org/PatHayes> a adams:HoopyFrood.

then the machine can compute that we disagree.

That's the sense in which I think OWL is a (good) far-context
mechanism for disambiguation.

p.s. the examples above are written in N3, about
which see http://www.w3.org/2000/10/swap/Primer
I also assume http://esw.w3.org/topic/TheUsualPrefixes .

> http://www.example.org/PatHayes ex:Denotes 
> http://www.example2.org/PatrickHayes
> doesn't really work, since it just moves the problem to another
> potentially ambiguous URI.
> http://www.example.org/PatHayes ex:Denotes
> http://www.example.org/PatHayes
> where the second use of the URI means "the non-information resource this
> web-page is about" seems to break the idea of a URI being a global 
> identity. It's using one URI for two different things, breaking RDF graph
> merging etc.

Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Friday, 29 April 2005 15:34:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:08 UTC