• From: "Liam R. E. Quin" <liam@w...>
• To: mailbox@j..., "xml-dev@l..." <xml-dev@l...>
• Date: Fri, 05 May 2017 12:48:51 -0400

On Thu, 2017-05-04 at 08:53 -0400, John P. McCaskey wrote:
> 
[...]
> In this excerpt from example.xml
> 
> <div xml:base="http://www.dictionary.com/a.html">; <p> <ref 
> target="#apple">Apple</ref> </p> </div>
> 
> does #apple refer to an element in example.xml that has id="apple" or
> to 
> http://www.dictionary.com/a.html#apple?
> 
> The first, right?

In slightly different language...

"example.xml" happens to be how you (the software) obtained a copy of a
representation of "a.html".

The relative URI reference #apple "points" to a location within the
representation you have, whose canonical URI is given to us as http://w
ww.dictionary.com/a.html regardless of how you came to find it.

There's no expectation in HTML at least that following a link to #apple
will involve fetching a different resource - rather, base, and
xml:base, tell us where we really are when we do that.

Liam

> 
> --
> 
> 
-- 
Liam R. E. Quin <liam@w...>
The World Wide Web Consortium (W3C)

• Follow-Ups:
  • Re: xml:base and fragments
    • From: Peter Flynn <peter@s...>

• References:
  • xml:base and fragments
    • From: "John P. McCaskey" <mailbox@j...>