[tei-council] Supplying default namespace with TEI Tite

[James Cummings]

Daniel Paul O'Donnell wrote:
>> convenience elements) if they did not do this.  If anyone (other than 
>> digitisers) is using Tite in a production system then I think we are 
>> failing in our duty to educate.  If we don't have a publicly availabl 
>> TEI Tite -> pure TEI stylesheet out there, I'm happy to write one.
>>   
> Actually James, that would be absolutely superb. The point behind Tite 
> is that it is a temporary workflow stage that can then be converted 
> directly to TEI. It's non-conformancy is a pure artefact of the intended 
> use case (keyboarders paid by the character). Tite is not namespaced for 
> purely economic reasons: there is no intellectual objection to <t:i>; 
> the economic objection is that it increases the cost of the tag by 60%.
> 
> I also think the rest of your observation is excellent here: Tite is an 
> opportunity to show how you can customise things and ought to be a 
> teaching moment in terms of explaining to people why they should see it 
> only as a stage in a workflow rather than an archival format. A sheet 
> converting to TEI would really help emphasise that and we could edit the 
> documentation to really emphasis this. Of course I believe the Monk 
> project is using it as their internal language.
> 
> If you wanted to do a stylesheet, I could write up some even more 
> explicit language for the narrative.

Didn't sebastian say it was already in existence?  In fact a quick look 
shows http://www.tei-c.org/release/xml/tei/custom/odd/tite-acdc.xsl 
(presumably automatically generated from its <equiv> statements with 
http://www.tei-c.org/release/xml/tei/custom/odd/make-acdc.xsl

If you want to write up some documentation on how Tite can be used as 
part of a workflow, then go for it!

Also, I believe you are wrong about the Monk project.  The schema which 
it advertises use of at least (last link at 
http://www.monkproject.org/downloads/ )is their own TEI Analytics.  I 
had several conversations with them about this whilst we were both 
individually writing stylesheets to transform EEBO texts.

If you look at the RNG they define a tei_sub and tei_sup  (in the TEI 
namespace I believe) but do not define b, i, ul, smcap, cols, and ornament.

Best,
-James
-- 
Dr James Cummings, Research Technologies Service, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk