[tei-council] more on internationalization
Laurent Romary
Laurent.Romary at loria.fr
Tue May 24 05:12:18 EDT 2005
You got it right, Sebastian. At least we should try to use the two
elements as consistantly as possible in future element description and
correct mismatches progressively as we see them (that could be part of
the chapter reviewing check list).
Laurent
Le 24 mai 05, à 10:09, Sebastian Rahtz a écrit :
> Laurent Romary wrote:
>
>> It is probably a good time to state their meaning more precisely.
>> Basically (and under Lou's control):
>> - <gloss> makes explicit the name that is encoded in the tag name
>> (respStmt -> responsability statement); in a sense it provides a term
>> (a noun phrase that can be used to designate the corresponding
>> concept)
>> - <desc> is the definitional field for the element. It is where a TEI
>> user should find the reference information for it.
>>
>
> so <gloss> should have been used relatively rarely? it seems to have
> been (ab)used to describe <valItem> entries, eg
>
> <attDef ident="unit" usage="req">
> <equiv/>
> <desc>indicates what kind of section is changing at this
> milestone.</desc>
>
>
> <datatype><rng:text
> xmlns:rng="http://relaxng.org/ns/structure/1.0"/></datatype>
> <valList type="semi">
> <valItem ident="page">
>
> <equiv/>
> <gloss>page breaks in the reference edition.</gloss>
> </valItem>
> <valItem ident="column">
>
>
> this should have been <desc>, right?
>
> It won't be hard to do an analysis of all this, but I think it
> may mean some global changes.
>
> --
> Sebastian Rahtz Information Manager, Oxford University Computing
> Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> OSS Watch: JISC Open Source Advisory Service
> http://www.oss-watch.ac.uk
>
>
More information about the tei-council
mailing list