[tei-council] concerns regarding <charDesc>

[Lou Burnard]

I could live with this change. However:

(a) I have an ousttanding action to make all listXXX things look the
same, and I don't think that would work for listChar (which would
presumably contain a mixture of char and glyph elements and wouldn'tt
self-nest)
(b) the pattern elsewhere in the header is to have a *decl including
multiple *desc
(c) each individual <char> or <glyph> is really a *desc

How about

nonstandardChars containing (charDesc|glyphDesc)+

I dunno what the <desc> is doing inside the current <charDesc> --
wouldnt it be more use be inside each <glyph> and <char> ?


Christian Wittern wrote:
> Dear Council members,
>
> As I mentioned briefly during the call, I found a few problems in the
> WD-Nonstandard glyphs chapter that I am currently reviewing.
>
> One of them concerns the <charDesc> element.  This element contains a list
> of the characters or glyphs that need a special description.  However, the
> name of the element is modelled on the other *Desc elements in the header at
> various levels.  Now, as far as I can see, all of them are describing a
> *single* entity, like <sourceDesc>, <fileDesc>, <encodingDesc> etc. The
> content of <charDesc> however is a *list* of things, quite similar to
> <listBibl> and other list* elements in the TEI.
>
> To avoid confusion and for consistency with general TEI practice, I would
> therefore propose to have this element renamed to <listChar> and at the same
> time also to update its <desc>, which currently reads 'provides descriptive
> information about characters or glyphs.'  to 'contains a list of <char>
> and/or <glyph> elements that provide descriptive information about
> characters or glyphs' or something similar.
>
> Please give me your comments,
>
> Christian
>
>
>