Re: @xml:base with @rendition (and maybe other pointers)
"John P. McCaskey" <[email protected]> Sat, 6 May 2017 12:51:24 -0400
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------6638230EA76F12E421DFB06D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
> 1. There are (at least) the following kinds of pointer value (URI) you=20
> can use in a TEI document:
> - prefixed : foo:bar
> - relative : foo.xml
> - fragmentary : #foo
> - absolute : http://foo.xml
> 4. To avoid misunderstanding, the TEI recommends use of the prefixed=20
> option, because it enables you to specify a mapping between an=20
> arbitrary prefix (like foo:) and an absolute value, using <prefixDef>=20
> (qv) in a painless and comparatively sane manner.
I myself would not recommend prefixes for the modest projects I see.=20
Learning XML and TEI is enough without learning regular expressions.
And there is the need to keep straight the difference between these TEI=20
prefixes and common URL prefixes. History student: =E2=80=9COh, you mean =
like=20
http:?=E2=80=9D Yes, it=E2=80=99s like your own custom http:. =E2=80=9CDo=
I need the //?=E2=80=9C Well,=20
no, it=E2=80=99s like a URL prefix, but different. More a URI prefix than=
a URL=20
prefix. Umm, forget that. Just don=E2=80=99t use one that=E2=80=99s alrea=
dy taken. Not=20
that it really matters. But, well, sometimes it could. =E2=80=9DKinda lik=
e=20
namespaces, which I=E2=80=99ve finally figured out in XML?=E2=80=9D Yes! =
=E2=80=9DGot it. Where=20
do I put the xmlns part?=E2=80=9D Well, no, <prefixDef> is used instead. =
=E2=80=9CSigh.=20
To point to my renditions, why can=E2=80=99t I just use #red=E2=80=9D? Yo=
u could . . .=20
but pull up a chair and I=E2=80=99ll explain more why we recommend otherw=
ise. Sigh.
I consider prefixes an advanced topic.
(By the way, is it still a URI once a TEI prefix is added? Or is it a=20
URI only after the prefix is processed?)
Whatever gets written, the reader should be able to walk away with=20
practical starting-point advice:
- =E2=80=9DWhat should I use for internal pointers?=E2=80=9D A # followed=
by any name=20
you choose. Then use the same name without the # as xml:id on the other e=
nd.
- =E2=80=9CHow should I encode file names?=E2=80=9C Just the file name. T=
hen enter the=20
directory as xml:base in <text>.
I would not have the first thing in the how-to be: =E2=80=9CThere are fou=
r kinds=20
of pointers. The first is a prefixed pointer. . . .=E2=80=9D
John
--------------6638230EA76F12E421DFB06D
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">
<font size=3D"-1"><br>
</font>
<blockquote
cite=3D"mid:[email protected]"
type=3D"cite"><font size=3D"-1">1. There are (at least) the followi=
ng
kinds of pointer value (URI) you can use in a TEI document:
<br>
=C2=A0- prefixed :=C2=A0 foo:bar
<br>
=C2=A0- relative=C2=A0 :=C2=A0 foo.xml
<br>
=C2=A0- fragmentary : #foo
<br>
=C2=A0- absolute : <a class=3D"moz-txt-link-freetext" href=3D"htt=
p://foo.xml">http://foo.xml</a>
<br>
</font></blockquote>
<blockquote
cite=3D"mid:[email protected]"
type=3D"cite"><font size=3D"-1">4. To avoid misunderstanding, the T=
EI
recommends use of the prefixed option, because it enables you to
specify a mapping between an arbitrary prefix (like foo:) and an
absolute value, using <prefixDef> (qv) in a painless and
comparatively sane manner.
</font><br>
</blockquote>
<br>
<font size=3D"-1">I myself would not recommend prefixes for the modes=
t
projects I see. Learning XML and TEI is enough without learning
regular expressions. <br>
<br>
And there is the need to keep straight the difference between
these TEI prefixes and common URL prefixes. History student: =E2=80=
=9COh,
you mean like <a class=3D"moz-txt-link-freetext" href=3D"http:?=E2=80=
=9D">http:?=E2=80=9D</a> Yes, it=E2=80=99s like your own custom http:. =E2=
=80=9CDo I
need the //?=E2=80=9C Well, no, it=E2=80=99s like a URL prefix, but=
different.
More a URI prefix than a URL prefix. Umm, forget that. Just don=E2=80=
=99t
use one that=E2=80=99s already taken. Not that it really matters. B=
ut,
well, sometimes it could. =E2=80=9DKinda like namespaces, which I=E2=
=80=99ve
finally figured out in XML?=E2=80=9D Yes! =E2=80=9DGot it. Where do=
I put the
xmlns part?=E2=80=9D Well, no, <prefixDef> is used instead. =E2=
=80=9CSigh.
To point to my renditions, why can=E2=80=99t I just use #red=E2=80=9D=
? You could .
. . but pull up a chair and I=E2=80=99ll explain more why we recomm=
end
otherwise. Sigh.<br>
<br>
I consider prefixes an advanced topic.<br>
<br>
(By the way, is it still a URI once a TEI prefix is added? Or is
it a URI only after the prefix is processed?)<br>
<br>
Whatever gets written, the reader should be able to walk away with
</font><font size=3D"-1">practical </font><font size=3D"-1">starting-=
point
advice:<br>
- =E2=80=9DWhat should I use for internal pointers?=E2=80=9D A # fo=
llowed by any
name you choose. Then use the same name without the # as <a class=3D=
"moz-txt-link-freetext" href=3D"xml:id">xml:id</a> on
the other end.<br>
- =E2=80=9CHow should I encode file names?=E2=80=9C Just the file n=
ame. Then enter
the directory as <a class=3D"moz-txt-link-freetext" href=3D"xml:bas=
e">xml:base</a> in <text>.<br>
<br>
I would not have the first thing in the how-to be: =E2=80=9CThere a=
re four
kinds of pointers. The first is a prefixed pointer. . . .=E2=80=9D<=
br>
<br>
John<br>
</font>
</body>
</html>
--------------6638230EA76F12E421DFB06D--