/ Elliotte Rusty Harold <elharo@...> was heard to say:
| At 11:50 AM -0500 1/27/02, Norman Walsh wrote:
|
|>My request has absolutely nothing to do with the interpretation of
|>URIs. I have never suggested that one should call resolveURI() on a
|>namespace name, or an RDF URI, or any other URI for any purpose
|>*except to obtain the resource that it points to*.
|
| I understand what you're saying, but that's not my point. I may very
| well have different catalogs for stylesheets, schemas, XIncludes, and
| anything else that uses a resolvable URI in the document. Choosing
Hmm. Perhaps. Although I think I prefer a system like RDDL in cases like
this, where the resource located by a URI can direct a process to other
resources for different purposes.
In any event, I'm clearly of a minority opinion and I humbly withdraw
the request. I think this means, despite all of the good and rational
arguments why one might want to have different resolvers for different
applications, that many applications will either (1) not provide a
mechanism for doing catalog-based URI resolution for URIs other than
external identifiers or (2) will (ab)use resolveEntity() for this
purpose. C'est la vie.
Be seeing you,
norm
--
Norman Walsh <ndw@...> | Unprovided with original learning,
http://nwalsh.com/ | unformed in the habits of thinking,
| unskilled in the arts of composition, I
| resolved to write a book.--Edward Gibbon