For good extensibility and interoperability, you need both
manditory parameters ("reject this job if you don't understand
this parameter") and optional ones ("if you don't understand
this, just ignore it").
A recipient must be able to tell just by examining the
attribute which class it is in.
I thought this was part of the whole job/PDL parameter override
issue, but it looks like I must have missed something.