LSB 5.0 specification reorg?

[Jeff Johnson]

This bug is created to track what changes are wanted in the LSB specification
for 5.0.

Bug 3510 describes database changes to implement moving around mod/submod.

Roughly, in lsbspec, there are subdirectories for modules and for submodules.
The submodule directories have the actual content, the module directories just
have material for "frontmatter" - the intro section, tables of referenced
specifications, etc. The submodule directories each have a matching intro
directory which is the frontmatter for a submodule book, and which is skipped
when gluing together a module book which has several submodules.

("Roughly" because it only works for stuff since LSB 3.1 - we have Desktop,
Languages, TUM at the module level; Graphics, Graphics-Ext, Multimedia, Perl,
Python, Toolkit_*, TrialUse and XML at the submodule level. Older stuff is
weird: LSB is core/base and C++ even though C++ was a separate submodule, and
has ELF and Packaging even though they were not separate submodules).

Do we need to reorganize/rename to match the mod/submod renaming?

Some issues to solve whether we move directories around or not were documented
in bug 3510, repeated here: makefiles in intro subdirectories, which intend to
build standard and library tables, do so by calling the script with a "module"
argument -m, although it's really submodules that are called out. These need
to change to reflect renamings.

We also need to check that scripts are aware of the new appeared/withdrawn
fields at the Module, SubModule and ModSMod levels, as well as SModCmd,
SModLib, SModStd, and hadle appropriately.

At the published book level - the booksets and books branches - booksets has
documents that are glued togethe from more than one directory in lsbspec, which
books has ones which are not. Again C++, Elf, Packaging are a little weird,
but roughly this works. books thus produces LSB-CXX-{generic,arch-specific}
and LSB-Printing plus unofficial submodule books for the rest; booksets
produces LSB-Core-{generic,arch-specific}, LSB-Desktop-{generic,arch-specific},
LSB-Languages, LSB-TrialUse. We have made the change where Printing is now a
submodule together with the new Scan entry, and a glued together LSB-Imaging
module - that change is clear. Do we want to make other changes? Build C++
inside the Core book?