On Mon, 2003-02-24 at 14:10, Anne Mahoney wrote:
> Isn't this a normal way of using the parameterized TEI files? We've
> been doing it here (at Perseus) for years: never occurred to me that it
> wasn't idiomatic.
yes, I suppose it is. I think I was being dense there.
> Unfortunately, I can't control the "whatever" part of that URL. I
> realize this would work just fine if I could.
you don't have *any* stable web server where you can stick a DTD? this
seems a bit hard.
> I'm not deeply in love with xalan either, but the project wants to run
> under Cocoon -- precisely "a Java servlet context," and Xalan is the
> parser that comes with the package. I realize I could use a different
> one instead but I thought, perhaps naively, that it would be easier to
> use the pieces that had been tested together.
I am sure you are right; if you want to use Cocoon, you are best
off stick with the X*** stuff. Plugging in Saxon would probably
not make life any easier.
> ~~~ More important, the other application that will be using
> these files was originally designed for SGML, for a project that has
> several gigabytes of SGML data from before this newfangled XML stuff was
> ever invented. That application uses the SP tools (among other things),
> so the files have to work with SP.
> I'm still surprised that catalogs aren't automatically supported, and
> that system identifiers seem to take precedence over public ones unless
> you specifically say they shouldn't. Just one more thing we've lost
> from the golden Saturnian age of SGML, I guess.
I think I'd prefer to see SGML as the Bronze Age following the Stone Age
of troff and TeX, and we are now in the Iron Age of XML. Yes, bronze was
cute, and iron is dirty, but it's strong stuff.
Sebastian Rahtz OUCS Information Manager
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431