Currently, when you start a new document and want to enable profiling, you have to remember the following steps:

1. Use a profiling attribute in your DC file or DAPS command-line invocation.
2. Add a profiling attribute to the elements you want profiled.
3. Add the profiling PI to the beginning of your document.

Imo, step (1) and (2) are relatively obvious. However, step (3) is non-obvious and has been an issue for me on a couple of occasions.

There does not seem to be a real justification for (3) to exist either -- if the DAPS command-line/or DC includes a profiling command, it is clear that the user intention is to profile. To get the right profiling stylesheet (DB4 v/ DB5), you only need to look at the xmlns & version attributes (or the DOCTYPE for DB4) -- and DAPS already does that for validation.

So, I would suggest to do the following:

• enable profiling whenever there is a PROF* attribute either via command-line or DC file
• find out which profiling stylesheets to use via xmlns/version attributes and DOCTYPE
• remove recognition of profiling PIs, to simplfy the code (unless there is a good reason to keep this complication)