[tei-council] Tite maintenance (was Re: One Licence Does it all)

[Lou Burnard]

I think "depressing" is a bit of an understatement. What is the point of 
the TEI Council taking on maintenance of a TEI customisation which has 
already been forked? We can call it "canonical" if we like, but since 
the whole point of the TEI tite exercise is to define what Apex will 
undertake to deliver as part of the accessTEI scheme, what is the reason 
for having a "canonical" schema distinct from what Apex wish to specify 
in any case?


On 10/08/10 18:19, Sebastian Rahtz wrote:
>
> On 10 Aug 2010, at 18:07, Kevin Hawkins wrote:
>
>> SourceForge.  But we also want to make sure there is ongoing
>> communication between this canonical version and Apex's fork (which they
>> call Tite 1.1:
>> http://accesstei.apexcovantage.com/Content/documents/TEI-Tite_guidelines__1.1.pdf
>> ).
>>
>
> It really is quite depressing to see this come out without
> any chance to comment. oh well.
>
> --
> Sebastian Rahtz
> Information Manager, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> Sólo le pido a Dios
> que el futuro no me sea indiferente
>
>
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council