[tei-council] Fwd: suggestions for TEI Tite documentation on AccesTEI portal

[O'Donnell, Dan]

I just spoke to them about this. As I suggested, this is just a standard 
header that slipped in rather than an attempt to claim IP (or assert 
that a web-circulated document is actually private. Peggy Glahn, who 
runs the programme with us, will get somebody to drop the top header and 
add the TEI logo to the bottom.

I also told Peggy that the numbering would have to be aligned with the 
TEI's official numbering once we've got that set up and that we are 
adding Tite to the ticketing system at Source Forge. Also, as one might 
suspect, nothing they have problems with or are anything less than 
enthusiastic about.

-dan

On 10-08-10 12:28 PM, Laurent Romary wrote:
> Very good, Kevin. Again, we need to secure this on the basis of our
> contractual link with them. But the lead should be on us.
>
> Le 10 août 10 à 20:20, Kevin Hawkins a écrit :
>
>    
>> Regarding "proprietary and confidential", I sent this to Apex a few
>> days
>> ago but haven't heard back since then.
>>
>> -------- Original Message --------
>> Subject: suggestions for TEI Tite documentation on AccesTEI portal
>> Date: Sun, 08 Aug 2010 14:32:42 -0400
>> From: Kevin Hawkins<kevin.s.hawkins at ultraslavonic.info>
>> To: Ed Moore<emoore at apexcovantage.com>
>>
>> Hi Ed,
>>
>> Regarding
>> http://accesstei.apexcovantage.com/Content/documents/TEI-Tite_guidelines__1.1.pdf
>>
>> :
>>
>> 1. The title page says "Apex TEI-TITE Guidelines For TEI Access
>> Project".  I think you'll want to change that to something like
>> "Guidelines for Encoding Documents for AccessTEI".
>>
>> 2. The running headers say the document is proprietary and
>> confidential,
>> but I think you'll want to remove the confidential statement since
>> it's
>> publicly available.  It would be good to clarify the copyright on the
>> document.  I've asked the TEI Council to clarify the copyright on TEI
>> Tite itself.  It seems the TEI Consortium will release it under GNU
>> GPL
>> 2, meaning derivations such as this one would also need to be released
>> under that.
>>
>> 2. You refer to the schema you're using as "TEI TITE" and "TITE", but
>> the version on which yours is based is called "Tite".  It would be
>> good
>> if your introduction clarified that the version of Tite you're using
>> is
>> derived from the version created and maintained by the TEI Consortium.
>>
>> Please let know if you have any questions,
>>
>> 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
>
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>    

-- 
Daniel Paul O'Donnell
Professor of English
University of Lethbridge

Chair and CEO, Text Encoding Initiative (http://www.tei-c.org/)
Co-Chair, Digital Initiatives Advisory Board, Medieval Academy of America
President-elect (English), Society for Digital Humanities/Société pour l'étude des médias interactifs (http://sdh-semi.org/)
Founding Director (2003-2009), Digital Medievalist Project (http://www.digitalmedievalist.org/)

Vox: +1 403 329-2377
Fax: +1 403 382-7191 (non-confidential)
Home Page: http://people.uleth.ca/~daniel.odonnell/