[tei-council] Trac 152 (TC)
Lou Burnard
lou.burnard at computing-services.oxford.ac.uk
Wed Jun 13 17:54:55 EDT 2007
Daniel O'Donnell wrote:
> Here are some changes for TC:
> http://tei.oucs.ox.ac.uk/trac/TEIP5/ticket/152
>
> * Reverse TC and PH--This was assigned to Syd
>
I'm open-minded as to whether this really needs doing; final disposition
of the chapters is something we have already decided to defer anyway.
> * We should mention that app is a special form of choice in TC,
> because we do so in the element description for choice: "For a
> specialized version of <choice> for encoding multiple witnesses of a
> single work, see section 15.1 The Apparatus Entry, Readings, and
>
OK, have added a para :
<p>The <gi>app</gi> element is in one sense a more sophisticated and
complex version of the <gi>choice</gi> element introduced in <ptr
target="#COEDCOR"/> as a way of marking points where the encoding of a
passage
in a single source may be carried out in more than one way. Unlike
<gi>choice</gi>, however, the <gi>app</gi> element allows for the
representation of many different versions of the same passage taken
from different sources.</p>
> * 15.1.1: "The attributes loc, from, and to, are used to link the
> apparatus entry to the base text. Several methods may be used for
> such linkage, each involving a slightly different usage for these
> attributes. Linkage between text and apparatus is described below in
> section 15.2 Linking the Apparatus to the Text."
> * * This needs clarification, since apparatus can also exist
> without a base text: How about: "The attributes loc, from, and
> to, are used to link the apparatus entry to the base text , if
> present. In such cases, s everal methods may be used for such
> linkage, each involving a slightly different usage for these
> attributes. Linkage between text and apparatus is described
> below in section 15.2 Linking the Apparatus to the Text. For the
> use of the app element without a base text see... "
>
OK : (TCAPPS)
> * 15.1.2: The example from Klaeber may need a note explaining that
> while Klaeber's readings themselves record information about the
> text, they are treated as typographic features in the variorum
> apparatus. (Lou made this point most forcefully--perhaps he should
> supply the language)?
>
Already done, I think.
> * 15.1.4.3: In the example with <witness xml:id="c" included="#Cp
> #La #Sl2">Constant Group c</witness>, a better approach would be
> to nest the actual members of this group in an apparatus-like
> structure:
> <witList>
> <witness xml:id="c">Constant Group c</witness>
> <witList>
> <witness xml:id="Cp">Corpus Christi Oxford MS 198</witness>
> <witness xml:id="La">British Library Lansdowne 851</witness>
> <witness xml:id="Sl2">British Library Sloane MS 1686</witness>
> </witList>
> </witList>
>
>
>
Also already done: I think there was another ticket about removing the
@include attribute which caused me to do it, but I cant now find it
> -dan
>
More information about the tei-council
mailing list