While I agree that job-state-reasons has a natural interpretation
when there are no values, namely that there are no reasons associated
with the current job state (and the semantics say that no reasons is
valid), Carl-Uno and I think that it is simpler and more consisten to
always require a value for job, printer (and Job template) attributes.
So we prefer to add a "none" value to job-state-reasons and keep the
syntax as (1#type2Enub). Then every attribute that is a list, must
have at lease one member. Ok?
Tom (and Carl-Uno)