Processing instructions are more for the use of people who are NOT
document type designers. Let's say your XML-smart HTTP server has a
replacement function for doing server-side variable includes (e.g. time,
date, last modified). Obviously that function cannot be tied to any
particular document type, because they can't force one document type on
all of their users. So they could specify it as a processing instruction
instead. The PI is "invisible" to DTD validation and thus doesn't
interfere with the doctype.
That was why namespaces originally used processing instructions. They
weren't supposed to interfere with document types (beyond the problems
with the prefixes, etc.). That's also why XML's own declarations are often
processing instructions.
Paul Prescod - http://itrc.uwaterloo.ca/~papresco
How many of the Congresspeople who voted for the CDA do you suppose
also voted to release the report that reads like a borderline por-
nographic dime-store romance written by a Texas preacher's son?
- Keith Dawson, TBTF
http://www.tbtf.com/archive/09-14-98.html
http://www.tbtf.com/resource/hypocrites.html