Dear all, a brief report on my work on correspDesc. (I’ll respond to Lou’s input separately) (I’m a little bit behind with documentation because my children passed their illnesses on to me …) So, I implemented correspDesc in revision 13129 and only needed three shots to make the Jenkins servers build the Guidelines (Yeah!). That said, I needed several tries locally before (which to my surprise worked almost flawlessly). I found it especially useful to run only the 'p5.xml‘ target which is quite quick and will create p5subset.xml along with p5.xml. This was helpful, because my naive assumption was that everything under P5/Source/Specs would automagically be included. It is not, you rather need a <specGrp> (in some Guidelines chapter?) with Xincludes of the files. * So, question 1: is this a bug or a feature? if it’s a feature (what I do think, because we do not implement elements without accompanying prose, do we?) it should probably be documented in TCW20 or did I missed it?! * question 2: how are the xml:ids (for <specGrp>s, <div>s etc) within the Guidelines chapters created? I just made them up … Best Peter