[tei-council] Supplying default namespace with TEI Tite

[Laurent Romary]

The point is that Tite is not only to be used by vendors, but is  
likely to be considered as a reference for many academic projects big  
or small having to proceed with digitization aspects. If there is such  
a hurdle as a double validation process, it is likely not to be  
misused or even rejected. I would follow David here: thinking the Tite  
principles over to simplify the core mechanisms would be a real  
benefit for all.

How much work (or thinking) would this require?

Le 7 juil. 09 à 03:23, David Sewell a écrit :

> On Mon, 6 Jul 2009, Sebastian Rahtz wrote:
>
>> It's all along been my assumption that Tite would be
>> used by people with a reasonably sophisticated
>> processing environment and understanding of XML, which
>> is why I at least have not been bothered by this.
>> If you're seeing that the assumption is false, and that
>> relatively naive folks will be using Tite, then
>> mayhap we have to think again about those convenience
>> elements.
>
> No, I think that's a valid assumption. Or at any rate, if Tite is  
> being
> used by conversion vendors, a prima facie requirement for the vendor
> should be the ability to create the proper environment for using it
> properly.
>
> It's just that in my experience, making things as simple as possible  
> for
> conversion vendors = reducing one's own headaches (because Murphy's  
> Law
> always applies).
>
>
> -- 
> 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