Re: Meaning of URIRefs

> But why should there be any need to have to agree to a pile of facts just
> to be able to use a term?  

If you don't, then you're much less likely to be using the term as

> > Isn't there a social convention that you don't use a word except in
> > accordance with its generally-accepted meaning?  And if you don't know
> > what meaning is generally accepted, then you don't use the word.  (Of
> > course there are exceptions, ways to indicate use-without-condfidence,
> > etc, but I believe this convention is the norm.)
> Well, not really, people abuse words all the time.  :-)  Just consider most
> of the modern US presidents, for example.
> There is some indication that natural language works best if its users can
> at least agree on the denotation of the terms they use.  However, there is
> absolutely no need to agree on any characteristics of the terms.  For
> example, you and may both use the term ``the Soviet Union'' without
> agreeing on any fact about the Soviet Union, even whether it ever has been
> a country.

And you think we could have a useful, productive conversation when you
think "the Soviet Union" means the Soviet Union and I think "the
Soviet Union" means my coffee pot?

> > On the Semantic Web, in the next few years, how is one to know the
> > generally-accepted meanings of terms?   
> > The proposal I'm advocating is that the we should consider the
> > "generally-accepted meaning" of a URI-Ref in RDF to be exactly the
> > meaning that is conveyed by the text at the URI.  
> And I'm advocating that the ``generally-acccepted meaning'' of a URI
> reference need not be so mandated.  If a community wants to provide a
> ``generally-accepted meaning'' for a URI, it can produce a document
> formally containing that meaning.  Agents can subscribe to that meaning if
> they so desire; if they want a different meaning then they can subscribe to
> another ``commonly-accepted meaning'' or even use their own meaning.
> Agents that share ``commonly-accepted meaning''s will (probably) work
> better together, but other groups of agents may need to use a different
> ``commonly-accepted meaning'' for a particular URI.

Are you suggesting that one URI-Ref can mean two different things?
(as in the coffee pot example above)

Or just that different groups may be aware of different facts about
it, without actually disagreeing about what it is.   Like you may know
the SU is something that was formed in 1922 and I may know it was
broken up in 1990.

> > I'm not sure what you'd consider the generally-accepted meaning of
> > "George-Bush-the-lesser".  I guess something like "the one of two
> > famous people named 'George Bush' who is in some overwhelming sense
> > less than the other."  It's a wonderful example of an English term
> > which has the same kind of tainted definition you're worried about my
> > proposal somehow forcing you to use.
> Ah, but this is precisely the point I am trying to make.  The denotation of
> George-Bush-the-lesser can be determined without accepting any of this
> ``generally-accepted meaning'', so it is possible for anyone to use the
> term.  The use can either agree with or disagree with this meaning, but
> will still be able to communicate.
> > Why is it not sufficient that my proposal gives you freedom to pick
> > whatever taint you want, trading it off against the ease and/or
> > ability of recognizing when you're talking about the same thing as
> > what someone else defines differently?    I don't see natural language
> > doing any better, and that makes me think we can't do any better.
> But natural language is indeed doing much better; you are using the term
> without agreeing to the ```taint''.  Forcing agents on the Semantic Web to
> accept such taints will, in my opion, place a severe chill on the Semantic
> Web.

I was only able to use it without taint by quoting it!

    -- sandro

Received on Friday, 25 October 2002 22:18:30 UTC