DO> I'd say the answer for *right now* depends on how far along you
DO> are in your project. ...
I think Daniel is exactly on target with this advice, here. There is
also the issue of how much you want to be on the cutting edge vs. how
much you dislike being a guinea pig.
DO> questions[s] ... [not] answered for P5 yet, both because there is
DO> less experience and because the documentation isn't there yet.
JF> ...and also, if I'm not mistaken, because changes are still being
JF> made, so the tagset itself is something of a moving target. The
JF> editors will perhaps have more to say on this, but it seems to me
JF> that people starting to work with P5 should be very much aware
JF> that it is still in development.
I think you said it pretty well.
DO> In other words, I'm a big believer in being second.
I am to; but in this case, there are already a bunch of us going
DO> P.S. In terms of modifying the dtd: why? I generally find it
DO> useful to try and work within the dtd... and rarely have found
DO> something that couldn't be done.
Hmmm... I half agree. I generally find it useful to try to work
within the "vanilla" TEI schema, but often find something that can't
be done, at least not properly, without extending it. The TEI schemas
are both designed for, and intended for, extension. (And it's a *lot*
better and easier in P5.)
JC> You can certainly get [element reference pages] (and the
JC> guidelines in their current variable state) for P5.
JC> [... CVS instructions snipped ...]
You can also download a "snapshot" of the P5 Guidelines in HTML
(rather than build the very newest yourself from the CVS source tree
using the instructions James provided) by downloading the newest
release (currently 1.1.2) from