OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] xml:base and fragments

On 05/05/17 17:48, Liam R. E. Quin wrote:
> 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.

We can now muddy the water by asking where the target 'apple' links to
in the example below, if we are processing valid XML and the schema/dtd
declares 'target' as IDREF.

<div xml:base="http://www.dictionary.com/a.html";>
    <item xml:id="apple">
      <p>A fruit, and a <link uri="http://www.apple.com/";>make
         of computer</a></p>
    <item xml:id="pear">
      <p>A fruit, certainly not an <ref target="apple">Apple</ref>.</p>

The 'uri' attribute has an absolute value, so it overrides any value
given in xml:base. The 'target' value is no longer a #fragment, and so I
assume it is regarded as out of scope for resolution wrt the xml:base.

I am clearly missing something here: why are people using #fragment
identifiers in XML (non-XHTML/HTML5) documents (eg TEI)?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS