Hi,
As far as I see, we can only push the categorized reference sections (phpdoc/RFC/manual.xml.in) forward, if we do handle the matter in livedocs. Since there are no people who would like to volunteer to implement the enhanced TOC stuff in DSSSL (online and downloadable versions) and XSLT (extended CHM) I know of, we should keep the current manual.xml.in file for these versions, and move the RFC/manual.xml.in file to something like phpdoc/php-manual.xml.in (or some other shiny name, which is future compatible :) This new file would be used by livedocs, and the old file would be used by the DSSSL and XSLT builds. Both files would need to be updated, when new extension docs, etc. are added (until DSSSL and XSLT rendering stuff gets completely abandoned).
If this is fine, then the tagging should be decided on. Seems like we need to modify docbook anyway we choose, since there is no option we can choose to not modify docbook and introduce some section levels there. Hartmut's proposal does not fit the multilevel sections proposed in the RFC, this is why I suggested using <section> tags. This might however have some meaning in livedocs, so since we need to modify docbook anyway, we can identically choose to introduce a new tag, like <refgroup> or something like this. That should be integrated to the livedocs TOC generator process then, and the output should be adjusted as such. Having a new tag would also help people who incidentally volunteer to fix the DSSSL and/or XSLT sheets to support this grouping, since they wont need to be afraid of existing code matcing the <section> tag. Then we would not overload that tag.
If this path is choosen, accepted and implemented, the refgroup section titles should be made entities, the RFC manual.xml.in need to be moved, renamed, updated to contain all the current manual.xml.in stuff, livedocs need to get updated, and everyone needs to go and party!
Goba
