-----BEGIN PGP SIGNED MESSAGE-----
Consider the following URI:
In Firefox 3.6pre, IE8, Chrome 5 and Opera 10, it just works.
But there is _no_ justification for this, in 3023 or 3023bis. Why?
Because there is no ID with value 'element-key' in the XML document
identified by the above URI. It exists _only_ in the output of the
XSLT stylesheet named in an xml-stylesheet processing instruction
which appears therein.
Or so it seems to me.
I think we need to add this to the use cases on the table as we
consider the TAG's request  to think again about generic processing
and frag-ids. I'm tempted to say that we need to find a way to allow
application-specific frag-id semantics to co-exist with generic
One subsidiary question -- is this or is this not a "same-document
reference" ? Or, to put it another way, where if anywhere do we
find a definitive answer to the question of what the base URI is of
the _output_ of an XSLT stylesheet applied in these circumstances?
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 651-1426, e-mail:
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
-----END PGP SIGNATURE-----