[
Lists Home |
Date Index |
Thread Index
]
- To: "Patrick Stickler" <patrick.stickler@nokia.com>
- Subject: RE: [xml-dev] URIs are simply names was:Re:[xml-dev]"Abstract"URIs
- From: "Manos Batsis" <m.batsis@bsnet.gr>
- Date: Tue, 19 Feb 2002 16:59:09 +0200
- Cc: "XML DEV" <xml-dev@lists.xml.org>
- Thread-index: AcG5T5j/66vnGayGSIiRjGkc+B+5GgAAwvfg
- Thread-topic: [xml-dev] URIs are simply names was:Re:[xml-dev]"Abstract"URIs
| -----Original Message-----
| From: Patrick Stickler [mailto:patrick.stickler@nokia.com]
| It seems to allow knowledge modelling, but I'm beginning to wonder
| if the representation-not-resource view of URLs is precise enough
| for knowledge modelling.
It is precise; but it may be poor as a design choice since one has to
provide the mapping between a "representation-not-resource" and what it
represents (whatever that may be). No good for network-aware
development.
The only case, IMHO, that justifies a URI that just represents
something, is when you have that something on the air (meaning runtime
space for example) and you need a handle for it because the system just
works that way, or because it's convenient to reuse the system's
implemented behavior.
Take RDF for example, (AFAIK and even worse, last time I checked) where
literals cannot be subjects in a sentence (triple). This essentially has
to do with the RDF model; a literal there is just that; what if the
system was able to uniquely identify this literal and refer to it with a
*unique* URI; all implemented features applicable to resources would be
available for literals as well.
This brings up some thoughts (and a problem) but this is the wrong
list...
Kindest regards,
Manos
|