[tei-council] draft message to TEI-L on removing elements and attribute from Tite (was Re: update from the TEI Tite task force)

[Laurent Romary]

Thanks a lot Kevin. Your wording may also provide us with the  
opportunity of getting a picture on who is actually using Tite.
Wait until the end of the day (your time) to let council members react  
and if none shouts loud, you can issue the message.
Laurent

Le 14 déc. 10 à 23:52, Kevin Hawkins a écrit :

> On 12/14/2010 10:04 AM, Laurent Romary wrote:
>> @Kevin: would you want top ask the TEI-L for feedback on some of the
>> tickets?
>
> Before I sent to TEI-L, please make sure I've got the message correct.
>
> ###
>
> Colleagues,
>
> A working group commissioned by the TEI Council is proposing revisions
> to the TEI Tite specification in order to reconcile the derived  
> version
> used by Apex CoVantage as part of the AccessTEI program and the
> canonical version on the TEI-C website.  We are also investigating  
> bugs
> and feature requests detected by users (so far, just me) which are  
> being
> collected in SourceForge so that these can be considered by Council  
> as well.
>
> This work involves going through some notes on Tite provided to us by
> Apex as they established AccessTEI, as well as some notes on  
> oversights
> detected by Perry Trolard and Lou Burnard since version 1.0 of Tite  
> was
> published on the TEI-C website.
>
> There are a number of elements and attributes not referenced in the
> prose documentation which were accidentally included in the TEI Tite
> schema.  Since we believe none of these are used by AccessTEI, we are
> considering removing them from the canonical Tite schema.  However, it
> has been pointed out that doing so risks breaking backwards
> compatibility for anyone using Tite (or a derived schema) outside of
> AccessTEI.
>
> *If you use Tite outside of AccessTEI*, please check over the list of
> elements and attributes at:
>
> http://sourceforge.net/tracker/?func=detail&aid=3136934&group_id=106328&atid=644062
>
> and comment on the ticket if you use any of these.  This will help
> Council determine which elements and attributes to "save from the
> chopping block".  Context is most helpful: does a vendor uses these
> elements or attributes when encoding for you?  Do you use Tite as the
> basis for an in-house schema of some sort?  Do you have another
> situation not described by one of these two scenarios?
>
> Thank you in advance,
>
> Kevin
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council

Laurent Romary
INRIA & HUB-IDSL
laurent.romary at inria.fr