[tei-council] Budget and Cost Saving for next year
bansp at o2.pl
Wed Nov 2 11:56:59 EDT 2011
On 02/11/11 16:46, Sebastian Rahtz wrote:
>> The functionality behind them *is* needed, and would have to be recast
>> as individual attributes (@from, @to, ... many, I'm afraid, and in need
>> of discussion and standardization).
> so if they are needed, but don't work anywhere, how do people manage
> today? I am tempted to say that if you have survived 10 years without
> an implementation, spending money on it now may be a luxury?
Yeah, this argument has crossed my mind, but I think I have an answer:
people use native XPointer (usually with special, non-native-XML
parsing) or proprietary formats, and in effect ignore the TEI because
they can't use what the TEI promises.
> I think it could actually be better to recast the stuff in pure TEI, actually,
> to avoid the impression that some software somewhere is going to implement it.
With a regret concerning the elegance of TEI XPointers, I agree.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4054 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20111102/28a64241/attachment.bin
More information about the tei-council