XML fragment identifier interpretation

ht@inf.ed.ac.uk (Henry S. Thompson) Thu, 24 June 2010 14:06 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5OE6q2f064625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Jun 2010 07:06:52 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o5OE6q2F064624; Thu, 24 Jun 2010 07:06:52 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from treacle.ucs.ed.ac.uk (treacle.ucs.ed.ac.uk [129.215.16.102]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5OE6oXV064617 for <ietf-xml-mime@imc.org>; Thu, 24 Jun 2010 07:06:51 -0700 (MST) (envelope-from ht@inf.ed.ac.uk)
Received: from nutty.inf.ed.ac.uk (nutty.inf.ed.ac.uk [129.215.33.33]) by treacle.ucs.ed.ac.uk (8.13.8/8.13.4) with ESMTP id o5OE6d95028359; Thu, 24 Jun 2010 15:06:41 +0100 (BST)
Received: from calexico.inf.ed.ac.uk (calexico.inf.ed.ac.uk [129.215.24.15]) by nutty.inf.ed.ac.uk (8.13.8/8.13.8) with ESMTP id o5OE6eV9032010; Thu, 24 Jun 2010 15:06:41 +0100
Received: from calexico.inf.ed.ac.uk (localhost [127.0.0.1]) by calexico.inf.ed.ac.uk (8.13.8/8.13.8) with ESMTP id o5OE6e1k002583; Thu, 24 Jun 2010 15:06:40 +0100
Received: (from ht@localhost) by calexico.inf.ed.ac.uk (8.13.8/8.13.8/Submit) id o5OE6dfU002582; Thu, 24 Jun 2010 15:06:39 +0100
X-Authentication-Warning: calexico.inf.ed.ac.uk: ht set sender to ht@inf.ed.ac.uk using -f
To: ietf-xml-mime@imc.org
Cc: public-xml-processing-model-wg@w3.org, public-xml-core-wg@w3.org, www-tag@w3.org, Richard Tobin <richard@inf.ed.ac.uk>
Subject: XML fragment identifier interpretation
From: ht@inf.ed.ac.uk
Date: Thu, 24 Jun 2010 15:06:18 +0100
Message-ID: <f5bocf08qzp.fsf@calexico.inf.ed.ac.uk>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Edinburgh-Scanned: at treacle.ucs.ed.ac.uk with MIMEDefang 2.60, Sophie, Sophos Anti-Virus, Clam AntiVirus
X-Scanned-By: MIMEDefang 2.60 on 129.215.16.102
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id o5OE6qXV064619
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Consider the following URI:

  http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.xml#element-key

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 [1] 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
semantics.

One subsidiary question -- is this or is this not a "same-document
reference" [2]?  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?

ht

[1] http://lists.w3.org/Archives/Public/www-tag/2010Jun/0125.html
[2] http://www.apps.ietf.org/rfc/rfc3986.html#sec-4.4
- -- 
       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: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [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)

iD8DBQFMI2ZvkjnJixAXWBoRAl2PAJ9idoD6tdM1NYnFmFh9m5re4WySSgCbBn2A
KnLZSKkCbdKkd9ELoR1dYPQ=
=OOr/
-----END PGP SIGNATURE-----