W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > July 2004

RE: Fragment identifiers must not be used.

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 5 Jul 2004 10:37:16 -0700
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA20423D509@RED-MSG-30.redmond.corp.microsoft.com>
To: "Elliotte Rusty Harold" <elharo@metalab.unc.edu>, <www-xml-xinclude-comments@w3.org>

We've clarified this as you've requested, stating: "Fragment identifiers
must not be used; their appearance is a _fatal error_.".

> -----Original Message-----
> From: www-xml-xinclude-comments-request@w3.org
[mailto:www-xml-xinclude-
> comments-request@w3.org] On Behalf Of Elliotte Rusty Harold
> Sent: Wednesday, April 14, 2004 5:00 AM
> To: www-xml-xinclude-comments@w3.org
> Subject: Fragment identifiers must not be used.
> 
> 
> Section 3.1 states, "Fragment identifiers must not be used" (in URIs
> in href attributes. OK. However, what happens if one is used? Is this
> a fatal error? Should the processor just ignore it? I think this
> should be spelled out. I think my preferred solution would be a
> non-fatal error. IN fact, maybe this should instead read something
> like. "XInclude processors must not use the fragment identifier in
> the uRI if one is present."
> --
> 
>    Elliotte Rusty Harold
>    elharo@metalab.unc.edu
>    Effective XML (Addison-Wesley, 2003)
>    http://www.cafeconleche.org/books/effectivexml
> 
>
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaula
it
> A
Received on Monday, 5 July 2004 13:37:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:57 UTC