Re: @xml:base with @rendition (and maybe other pointers)
"John P. McCaskey" <[email protected]> Wed, 3 May 2017 11:08:30 -0400
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------9CB34444FD029BD03BBFB1E9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
I opened up this ticket <https://github.com/TEIC/TEI/issues/1638> in GitH=
ub
*Make (or explain how to make) @rendition local*
A straightforward case is to encode relative file names throughout a
document (for images, for example) then use (and change as needed)
xml:base to set the absolute path to those files.
A straightforward use of renditions is to gather common renditions
in the teiHeader and encode references to those renditions
throughout the document.
It is not obvious how to combine these two practices, if that is
even possible. Setting xml:base breaks pointers to the local renditio=
ns.
Task: Address (in the schema or the guidelines) the needs of someone
trying to combine these two practices.
John
On 5/3/2017 10:43 AM, C. M. Sperberg-McQueen wrote:
>> On May 3, 2017, at 6:26 AM, John P. McCaskey <[email protected]=
> wrote:
>>
>> Another reason to design for internal renditions only:
>>
>> .,..
>> Corpus-wide formatting changes should be done with stylesheets, not ex=
ternal rendition pointers.
> While I sympathize with this point of view, up to a point, a few techni=
cal points
> which point the other way should be borne in mind:
>
> 1 One of the most fundamental decisions in the design of URIs is that t=
hey
> make no distinction in principle between pointers within a document and=
pointers
> between documents. (This is easily seen if one compares URIs to the ID=
/IDREF
> mechanism used in SGML and XML for in-document references, which leaves
> inter-document references in need of some other language for hyperlink =
addresses.)
>
> 2 In the design of any system, orthogonality and compositionality are a=
lmost always
> betters idea than non-orthogonality and non-compositionality. Where a=
language
> accepts an arithmetic expression, it should normally accept any arithme=
tic expression;
> where a language accepts a URI, it should normally accept any URI.
>
> If one has made the decision to use URIs and not some other addressing =
mechanism,
> it=E2=80=99s almost certainly a questionable idea to start imposing add=
itional rules that go
> against the grain of the design. (=E2=80=9COnly same-documentl referen=
ces here=E2=80=9D is an
> excellent example of what things look like at the top of the slippery s=
lope; at the
> bottom are languages with lots of special cases and exceptions. Been t=
here,
> done that; I assure you it=E2=80=99s not a good place to be.)
>
> 3 =E2=80=9CExternal=E2=80=9D is a slightly tricky concept for any syste=
m which, like XML and SGML,
> allows different parts of a single =E2=80=9Cdocument=E2=80=9D to be sto=
red in what the external
> environment regards and manages as distinct entities (e.g. files). If =
I wanted to
> have my renditions in a distinct file which is referenced either as an =
external
> entity or via XInclude, could you devise rules that could identify that=
case and
> rule it out? (I am pretty sure I can=E2=80=99t.)
>
> The independence of element structure and entity structure is one of th=
e
> fundamental design decisions of SGML, retained in XML with some restric=
tions
> aimed at simplifying partial processing. Decisions at the TEI level w=
ill normally
> work best if they go with rather than against the grain of the technolo=
gy.
>
>
> ********************************************
> C. M. Sperberg-McQueen
> Black Mesa Technologies LLC
> [email protected]
> http://www.blackmesatech.com
> ********************************************
>
--------------9CB34444FD029BD03BBFB1E9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<p><font size=3D"-1">I opened up <a
href=3D"https://github.com/TEIC/TEI/issues/1638">this ticket</a=
>
in GitHub</font></p>
<blockquote>
<p><font color=3D"#333333" size=3D"-1"><b>Make (or explain how to
make) @rendition local</b></font></p>
<p><font size=3D"-1">A straightforward case is to encode relative
file names throughout a document (for images, for example)
then use (and change as needed) <a class=3D"moz-txt-link-freete=
xt" href=3D"xml:base">xml:base</a> to set the absolute
path to those files.<br>
<br>
A straightforward use of renditions is to gather common
renditions in the teiHeader and encode references to those
renditions throughout the document.<br>
<br>
It is not obvious how to combine these two practices, if that
is even possible. Setting <a class=3D"moz-txt-link-freetext" hr=
ef=3D"xml:base">xml:base</a> breaks pointers to the
local renditions.<br>
<br>
Task: Address (in the schema or the guidelines) the needs of
someone trying to combine these two practices.</font><br>
</p>
</blockquote>
<font size=3D"-1">John<br>
</font><br>
<br>
<br>
<div class=3D"moz-cite-prefix">On 5/3/2017 10:43 AM, C. M.
Sperberg-McQueen wrote:<br>
</div>
<blockquote
cite=3D"mid:[email protected]"
type=3D"cite">
<pre wrap=3D"">
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">On May 3, 2017, at 6:26 AM, John P. McCaskey <a cl=
ass=3D"moz-txt-link-rfc2396E" href=3D"mailto:[email protected]">&l=
t;[email protected]></a> wrote:
Another reason to design for internal renditions only:
.,..
Corpus-wide formatting changes should be done with stylesheets, not exter=
nal rendition pointers.
</pre>
</blockquote>
<pre wrap=3D"">
While I sympathize with this point of view, up to a point, a few technica=
l points
which point the other way should be borne in mind:
1 One of the most fundamental decisions in the design of URIs is that the=
y
make no distinction in principle between pointers within a document and p=
ointers
between documents. (This is easily seen if one compares URIs to the ID/I=
DREF
mechanism used in SGML and XML for in-document references, which leaves
inter-document references in need of some other language for hyperlink ad=
dresses.) =20
2 In the design of any system, orthogonality and compositionality are alm=
ost always=20
betters idea than non-orthogonality and non-compositionality. Where a l=
anguage
accepts an arithmetic expression, it should normally accept any arithmeti=
c expression;
where a language accepts a URI, it should normally accept any URI.
If one has made the decision to use URIs and not some other addressing me=
chanism,
it=E2=80=99s almost certainly a questionable idea to start imposing addit=
ional rules that go
against the grain of the design. (=E2=80=9COnly same-documentl reference=
s here=E2=80=9D is an
excellent example of what things look like at the top of the slippery slo=
pe; at the
bottom are languages with lots of special cases and exceptions. Been the=
re,
done that; I assure you it=E2=80=99s not a good place to be.)
3 =E2=80=9CExternal=E2=80=9D is a slightly tricky concept for any system =
which, like XML and SGML,
allows different parts of a single =E2=80=9Cdocument=E2=80=9D to be store=
d in what the external=20
environment regards and manages as distinct entities (e.g. files). If I =
wanted to
have my renditions in a distinct file which is referenced either as an ex=
ternal=20
entity or via XInclude, could you devise rules that could identify that c=
ase and
rule it out? (I am pretty sure I can=E2=80=99t.)
The independence of element structure and entity structure is one of the=20
fundamental design decisions of SGML, retained in XML with some restricti=
ons
aimed at simplifying partial processing. Decisions at the TEI level wil=
l normally=20
work best if they go with rather than against the grain of the technology=
.
********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:cmsmcq@blackmesatech=
.com">[email protected]</a>
<a class=3D"moz-txt-link-freetext" href=3D"http://www.blackmesatech.com">=
http://www.blackmesatech.com</a>
********************************************
</pre>
</blockquote>
<br>
</body>
</html>
--------------9CB34444FD029BD03BBFB1E9--