[tei-council] One Licence Does it all

[Lou Burnard]

That's all very well, but what is the point of our making changes in the 
canonical TEI Tite so long as Access TEI uses something else?


On 10/08/10 19:21, Laurent Romary wrote:
>
> Le 10 août 10 à 18:56, Sebastian Rahtz a écrit :
>
>>
>> On 10 Aug 2010, at 17:11, O'Donnell, Dan wrote:
>>
>>> The next issue is how to get Tite into a regular maintenance schedule
>>> and authority. In this case, my understanding is that the will is
>>> there,
>>> it just needs direction. We already treat it as a TEI
>>> customisation; the
>>> question is probably simply taking initiative.
>>
>>
>> if we agree that the thing is simply another component of the
>> guidelines,
>> then we simply follow Kevin's lead, and have bugs/requests entered
>> in Sourceforge, and acted upon by editorial team under council
>> instruction
>
>
> Exactly. Looks like a no-brainer activity (from an organisational
> point of view, I mean - let us expect Kevin has a few difficult cases
> for us).
> To answer Lou's question on another thread: things you've not seen
> implemented from your spring comments could be filed in as SF tickets,
> I think.
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council