Sebastian Rahtz wrote:
> I think the politically correct view is that the TEI is in neither
> SGML nor XML, but in a higher-level form from which SGML and XML can be
> extracted equally well. Thats the "pizza" view, anyway. I know its not
> necessarily ideal, but it does the job, doesn't it? You do actually
> get the XML DTD you need?
Well this is an alternative.
1/ The risk is to be overloaded with a large set of different TEI
sub-DTD. When i am using SGML, i like to know what the base tagset i am
using and the different extension as well. I know it could be possible
to put some comments within the generated DTD but it is not sufficient
in my opinion.
2/ You have to distribute the alternative DTD with your documents. And
if we are dealing with a large set of different type ressources (this is
our case), it could become difficult to handle all those different DTD.
3/ In an editorial point of view, each time you want to modify your tag
set, you have to go on the pizza website and generate your brand new
Another solution, more XML oriented, could be to re-think the DTD and
its architecture. It is not simple, but maybe XML Namespaces associated
with XML Schemas could help. I will try when my phd will be finished ;-)
> > Is someone working on an XML Schema for TEI?
> that would be amusing :-}
Another remark concerns some XSL stylesheets to display TEI ressources
or fragments. I know you've done a great job with XSL but it is a huge
task to cover the whole TEI. I was wondering if it could be possible to
unify our efforts (i did quite the same for the CES some weeks ago) to
provide an XSL architecture for TEI. Who is using XSL with TEI
ressources? What are the requirements, the type of output? Do we need
This type of initiative should also be launched and why not supported by
the TEI consortium that seems to be ... rather asleep at the moment.
Even if it is not the same context, i am always amazed to see the
dynamic Apache community and their different working groups.
Could/Should be an inspiration for all of us...