[
Lists Home |
Date Index |
Thread Index
]
So did I but I have to check. Using a URN is pretty much
using another style of PUBLIC ID (not precisely but
the same intent: not something to be directly dereferenced).
However, URIs are web critters. There are other forms
of PUBLIC IDs that could be used. It would be yet
another "you'll have to fallback to SGML" rule.
len
From: Thomas B. Passin [mailto:tpassin@comcast.net]
[Bullard, Claude L (Len)]
> The PUBLIC identifier, as you know, can have interesting
> information in it that has nothing to do with dereferencing
> a representation from a resource over a network protocol.
> Are you saying the URI in the PUBLIC id would point to a document
> for getting that information?
>
> That would also mean that nothing can be done with XML unless
> it is done "on the web". PUBLIC IDs are a way to hook up
> to other systems. You would be legislating away that right.
I just took it that John meant to use a __non-dereferenceable__ URI as an
identifier, since using URIs as has become standard practice by now (xslt,
RDF, OWL...). Now you could really confuse people by using a retrievable
http: URL for the Public Identifier!
|
