[
Lists Home |
Date Index |
Thread Index
]
Thanks John, for both points. So one can use the public ID for the namespace
name.
http://www.ietf.org/rfc/rfc3151.txt
Then one has to decide if resolution is required.
" Process of identifier resolution:
Identifiers in the "publicid" namespace may be resolved by the
same policies and procedures as public identifiers. Public
identifiers can be resolved in many different ways. Many existing
systems provide facilities for resolving them by way of OASIS
TR9401 [6] Catalog files. Other systems resolve them by mapping
each component to a local pathname component. And some systems
simply "know about" a fixed set of public identifiers. In
addition, URNs in the 'publicid' namespace may be resolvable by
other mechanisms unique to URIs (such as caches)."
No difference other than in
urn:publicid:{transcribed-public-identifier}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
the bracketed fellow has information in it that is extracted
and used according to some local policy.
Will XSLT trip over the public ID? I assume not.
It would be strange but an XPath buried in that guy into
the Schema would identify the direct context of the
definition. Not only who, but where. Ummmm.... maybe
it's easier to just put the schema inline. :-)
len
|
