A Fork Lay Ahead (was URI: Name or Network Location?)

Matt Halstead wrote:

>> I think RSS 1.0 does a good job of both clarifying and confusing
>> the separation of URI and URL.  A channel has a link which must
>> be a URL, whereas an image has a rule that one is to use the
>> about URI as also the URL of the image itself.

>> My opinion is that if you want to reference the location of
>> something, then add some structures to your Rdf, e.g. through a
>> property, that allows an unambiguous interpretation.


Just thinking aloud here:

I believe this gets to the heart of the matter.

Will the SemWeb overlay the existing web information space, providing typing
and other metadata for the information and objects described in HTML pages
which link together via hypertext?

(This HTML page is about elephants and links to this Image which is a
picture of an elephant and also links to this HTML page which is the
homepage of the Elephant Society ...)

Or will the SemWeb *supercede* the existing web and become its own
information space with the linkage becoming the URIs provided as values of
ObjectType properties -- with SOME objects having unambiguous properties the
URIs of which can be interpreted as dereferenceable URLs leading to
representations of resources.

(This Organization employs this Person who wrote this Article [all described
in the "abstract"] which can be retrieved [via some unambiguous property]
from this URL and this URL and this URL)

--- Stephen

Note:  The information contained in this message may be privileged and
confidential and protected from disclosure.  If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error,
please notify us immediately by replying to the message and deleting it from
your computer. Thank you.  ThruPoint, Inc.