I am working on my dissertation. My pet peeve is having to use a kludge like:
<note type="draftComment">Expand discussion of the above ethnographies</note>
for comments that should show up in pre-publication formmated copies.
When working with transcription, archival, or literary material the same need
shows up when scholars need to attach ephemeral comments as reminders to
themselves or other team members.
<!-- *this is ae comment about the SGML code itself* -->
is unsatisfactory because you want to selectively access the draftComment
data for processing. Indeed, you might want to carry it indefinitely as a
way to automatically document the scholarly process.
I have a similar problem since I am working with the American Anthropological
A bibliographic pointer or short reference has the form:
This is very annoying because the optional-distinguishing-lowercase-letter
can *only* be resolved by an automata for the source list at the time of
publication. Formatting of in-text short bibliographic pointers depends on
the contents of the document's source list, so the in-text citations can also
only be resolved at publication.
The TEI recommendation to use ref elements works.
You assign <bibStruct id="uniqueID">,
then have <ptr type="in-text-citn" idref="uniqueID"/> and expand the pointer
The only problem is that this is very bad document-base design because the
coder has to remember a non-Mnmonic, posibly arbitrary string.
In theory, every entry in a AAA compliant source list should be uniquely
identified by author-group, year of publication, and the lesser of the
analytical or monograph title.
This results in:
This can be automatically rendered in the desired form
(Last-Name1 and Last-Name2 9999x?)
where the x? represents the optional lower-case letter that makes the AAA
in-text citation a unique reference.
Unfortunately "cooked" constructs like:
Thus, <bibl><author>Foo</author> (<date>9999</date>) does not adequately
address yadda; furthermore, <title>Tractus</title></bibl> blah blah ... .
That is, automatic processing cannot deal with every possible citation form
that occurs in real text.
Thus I use:
Alternatively one could use:
<note type="dummy" rend="hidden"><title>My-title</title></note>
Again, this seems an excessive use of the NOTE element.
On Tuesday 02 October 2001 13:01, Julia Flanders wrote:
> I do take your point--it would be great to have a separate element
> for this kind of bibliographic description, and the elements you
> mention sound well-conceived for this purpose. On the other hand,
> within the existing TEI framework, <note> is explicitly provided
> within <notesStmt> as a place to record descriptive information about
> the document, and its heritage as a species of "note" seems fairly
> authentic. (That is, the tag name is not misleading.)