Re: @xml:base with @rendition (and maybe other pointers)
"C. M. Sperberg-McQueen" <[email protected]> Fri, 5 May 2017 10:38:27 -0600
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <[email protected]> |
On May 5, 2017, at 8:44 AM, John P. McCaskey <[email protected]> = wrote: > Based on the recent discussion, am I correct to say that the example > in 1.3.1.1.5 Evaluation of Links is incorrect? It makes the same > mistake I was making, right? >> In essence xml:base is used to set a context for all relative URLs >> within the scope of the element on which it is specified. For >> example: >> <body> >> <div xml:base=3D"http://www.example.org/somewhere.xml"> >> <p> >> <!--... --> >> <ptr target=3D"#p1"/> >> <!--... --> =20 >> </p>=20 >> </div>=20 >> <div> =20 >> <p> >> <!--... --> =20 >> <ptr target=3D"#p1"/> >> <!--... --> =20 >> </p>=20 >> </div> >> </body> >> The first ptr element here is within the scope of a div which >> supplies a value for xml:base; its target is therefore to be found >> at http://www.example.org/somewhere.xml#p1. The second ptr, >> however, is within the scope of a div which does not change the >> default context, and its target is therefore some element within >> the current document with the value p1 for its xml:id >> attribute. Further discussion of this element and its effect on TEI >> linking methods is provided in chapter 16 Linking, Segmentation, >> and Alignment. > Both pointers in fact point to the same location, a location within > the current document, right? It's not clear that either here or on xml-dev the discussion of this question has achieved consensus. Certainly the description in 1.3.1.1.5 appears problematic in view of section 4.4 of RFC 3986 and should be revised, if consensus can be achieved on what it should say. But your correction seems equally problematic to me. The reasons should be clear from the mail on this subject I have sent over the last couple of days to this list and to xml-dev; I won't re-repeat them here. ******************************************** C. M. Sperberg-McQueen Black Mesa Technologies LLC [email protected] http://www.blackmesatech.com ********************************************