[tei-council] file names voting results
lou.burnard at computing-services.oxford.ac.uk
Mon Sep 4 19:40:50 EDT 2006
Sebastian Rahtz wrote:
> Conal Tuohy wrote:
>> AFAIK the point of the exercise is merely to help authors, editors,
>> translators, etc, to make reference to those files, by giving them a
>> human-language label as well as their unique code.
> Indeed. I can see some (rather small) point in it, which is why I
> voted for it.
> All other things being equal, I'd have made the identifiers match the
> file names (as those for *Spec do), but I can see that's too late.
The big difference is that the *Spec identifiers aren't used as cross
references spattered throughout the text!
>> Moreover, it's better to retain the short codes for
>> the output file names since they are likely to make more stable URLs
>> than the human-readable labels, which are subject to revision.
> ok, sure, I can see the argument there
Yes. Also the human readable labels are language specific. It wouldn't
be too hard to supply them as values for the @n attribute on <div1>s though.
More information about the tei-council