[tei-council] file names voting results
wittern at kanji.zinbun.kyoto-u.ac.jp
Wed Sep 6 20:17:26 EDT 2006
Sebastian Rahtz <sebastian.rahtz at oucs.ox.ac.uk> writes:
> Lou's Laptop wrote:
>>> 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!
> not per se; but that's because we use a more sophisticated cross-ref
> to talk about the things in *Spec.
>> 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.
> I am not sure I see a point in that. after all, that is what <head>
> is for. We wouldn't
> want to abuse @n with free text now would we.....
Well, I would say the filenames as we have them now are more like
tokens than free text. I think it would make sense to use them as
values for @xml:id since you then would immediately understand where
the reference is going, whereas at the moment, there is only a coded
value that leaves the reader clueless. However, they should be
considered tokens, and not translated, at least in my opinion. If you
allow them to be translated, you would have to expect weird things
like Kanji in filenames and some such which would be a great mess. We
would be served much better if we leave the filenames as ASCII only as
they are now.
All the best,
Institute for Research in Humanities, Kyoto University
47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN
More information about the tei-council