In Reply-To: Syd Bauman <[log in to unmask]> of Mon, 16 Sep 1996
In-reply-to: Greg MacGowan's of Tue 1996-09-10 14:32Z
Patrick Durusau's of Mon 1996-09-09 14:41Z
[Sorry this has taken so long... I been busy]
pd> Foobar, Edward. Funny Things in the Park. Cambridge, Alice's Press. 1995.
pd> More Things in the Park. Cambridge, Rabbit's Press. 1996.
SB:My three favorite solutions to this problem, in order of preference,
follow. In searching for a proper answer I came to an astounding
discovery of what is probably a gross oversight in TEI: The AUTHOR
element does not have a key= (or reg=) attribute.
Well, whether or not it's gross, it isn't an oversight. The <author>
element is a bibliographic feature, and in real bibliographic databases
the sort of suppression/normalization you're talking about is Not Done.
You could certainly argue for the inclusion of <author> within the name
However, there is no need to make any changes to anything, if you use
the COPYOF attribute defined by the global analytic tagset, which is a
solution that Syd did not propose. This would require you to define
somewhere a list of definitive author names...
<head>Approved forms of authors names</head>
<item><name key=fooULike>Alonso Q Phoo</name></item>
<!-- .. more names here -->
>> <author rend='present(no)'>Foobar, Edward</author>
<Here the rendition keyword "present" indicates whether the content
>was present in the original. The default is "yes". This is similar
>to Mr. Durusau's "rend=implied", but follows the syntax of the WWP
>rendition ladder system, and uses a keyword that is not so easily
>confused with the #IMPLIED of SGML.
I find *very confusing* and I cannot see what it's for. If the content
wasn't in the original, what are you doing encoding it? Or, if you must,
why isn't it inside an <add> tag? I think that's a lot more plausible
than encoding it as an <abbr> -- to say that the null string is an
abbreviation for something strikes me as perverse.
>goals and objectives of the project, I sort of agree. One could
>simply encode the author's name everywhere it goes, and expect the
>output driver to be smart enough to suppress the output of AUTHOR if
<it was the same as the preceding AUTHOR. This can be done with
>DynaText style sheets, I am told.
This is the one that makes most sense to me. For most applications, you
want the author name explicitly there. Whether it gets rendered by
nothing, or by ditto marks, or by "ib" is all presentation. If you are
cross referring to a <bibl> from within a text (as in "See Foobar 97")
the last thing your application wants when it gets the appropriate
<bibl> is to find it's now got to go and look somewhere else for the
***** author name as well!
> I'm not really sure how one goes about altering TEI Lite, since
< the header comment to teilite.dtd says it is copyrighted and "may
> not be altered; modifications to these DTDs should be performed
> as specified in the Guidelines in chapter 'Modifying the TEI
> DTD.'". However, the DTD is not subject to the same kind of
You're not meant to modify TEI Lite, as the comments make clear. If you
want to use something *like* TEI Lite, but not quite, then you should
make your own set of TEI-conformant modification files. Why not start
from the ones that we used to generate TEI Lite itself -- I think
they're on the UIC server somewhere (Michael?)
best wishes (and apologies for taking so long to comment)