There is of course nothing wrong with having two roots -- one as a
specification and one as a user guide. The specification should be
more formal and use the correct terminology without apology, the
burden of understanding being on the reader. The user guide must
start with the vocabulary expected of the new reader, and introduce
things in an "easy" order. The onus of explanation is on the writer
of the guide in this case, as we WANT people to write/output HTML.
Ideally of couse one would rewrite the whole thing but we haven't
time, so the details about each element had best be represented just
once.
I think we need a version of www which runs off RFCxxx-conforming
RFCs, unless someone can do it with TeX. Then we can feed it a
stream of concatenated HTML. We will need it for HTTP2 too.
Tim