By "profiling attributes" I am referring to those attributes that you normally use to profile DocBook documents. There is an article on this at SourceForge: http://docbook.sourceforge.net/release/xsl/current/doc/tools/profiling.html
For example, in our documentation, we use the attribute "vendor" to specify which product we are documenting and then the attribute "arch" to specify what platform we are referring to. We then pass the document through an XSLT in our build process which ensures, via profiling, that only the relevant documentation is included for a particular product and platform combination. There are several other attributes which are commonly used for profiling, including "os", "conformance" and "userlevel". Damien
