[tei-council] Tite and conformance (long)

[Laurent Romary]

I think Davis is providing here a good strategic vision that may keep  
Tite match its specific use case and not go beyong (remember Lite been  
seen as the default TEI schema).
Laurent

Le 10 juil. 09 à 03:42, David Sewell a écrit :

> Just one comment on the TEI Header issue. Given a strong enough
> statement to the effect that a TEI Tite document is intended for  
> initial
> keyboard capture and is in a non-archival, nonconformant TEI format
> where post-processing is expected, I don't think it is horrible that
> <text> is permitted as a root element.
>
> If <teiHeader> is required, nothing will stop users of Tite from
> supplying the barest minimum header necessary for validation at the
> keyboarding stage. (I plead guilty to having done this myself when
> sending material out for keyboarding.)
>
> There is little to choose between a document with no TEI Header and  
> one
> with a valid but incomplete <teiHeader> element. Both need to be
> expanded to be useful for archival and interchange purposes. So I am  
> not
> inclined to revisit the decision about the header in Tite.
>
> -- 
> David Sewell, Editorial and Technical Manager
> ROTUNDA, The University of Virginia Press
> PO Box 801079, Charlottesville, VA 22904-4318 USA
> Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
> Email: dsewell at virginia.edu   Tel: +1 434 924 9973
> Web: http://rotunda.upress.virginia.edu/
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council