chapter on classes; @n (was "Re: [tei-council] tei release 0.4 coming soon")

[Syd Bauman]

> > issues, including phrase-level encoding, at some time, too. But
> > that's not the question I raised, which was should the reference
> > documentation on classes occupy 1 chapter or 2.

> I'm thinking that I'd prefer it if you waited a month to do so :-}

No problem. I will change the chapter heading to "Classes", then.


> > 3. While I don't like the idea of changing chapter numbers now[1], I
> >    do not think there is really much choice -- we will be. Thus, this
> >    should not be a consideration in our decision about whether
> >    classes should be described in one reference chapter or two.
> >   
> ok, sure. I think you're right

Check.


> those @n attributes you mention - why not just kill them outright?

I don't know why they're there. While I can think of several uses,
and I do not feel strongly about it, I don't really think it's a good
idea to have them.