This is rather subtle. You're saying "if the client mistakenly
said 'German' but ACTUALLY supplied the CLIENT-SUPPLIED attributes
in 'Danish', should the the client be able to subsequently CORRECT
the value of 'attributes-natural-language' on the job?" (I think).
I'm not so sure this is simple. Would we want the client also to
be able to change 'attributes-natural-language' on the Job after
submission and then change the VALUES of the CLIENT-SUPPLIED text
attributes? Changing the 'attributes-natural-language' will change
the output of speech synthesis software (for users of hand-helds,
cell-phones, or accessibility-enhanced PCs).
I see your point, but I think the ramifications are not so simple.
- Ira McDonald (consulting architect at Sharp Labs America)
High North Inc
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com]
Sent: Tuesday, January 11, 2000 4:13 PM
Subject: IPP> OPS - Should "attributes-natural-language" be allowed to
be setta ble?
Section 9.2.1 includes "attributes-natural-language" in the list of Job
attributes that MUST NOT be settable. However, it seems useful and not hard
to implement, if a user's client sets the wrong natural language, that the
user could change it after job submission, so that messages would come in
the proper (supported) language).
ISSUE 12 - Ok to remove "attributes-natural-language from the list of Job
attributes that MUST be READ-ONLY?