I have indicated what needs to be changed. I have also put
these changes into the Protocol Appendix where this information
also resides.
So, most of you can wait until I release the next version of the
protocol document before studying all this detail.
Bob Herriot
> From hastings@cp10.es.xerox.com Wed Sep 24 09:50:37 1997
>
>
create operations (Print-Job) request:
Also for Validate-Job
> Operational Attributes:
> "job-name"
> "ipp-attribute-fidelity"
> Job Attributes:
> any Job Template attribute
> Document Content:
create operations (Create-Job and Validate-Job) request:
Operational Attributes:
"job-name"
"ipp-attribute-fidelity"
Job Attributes:
any Job Template attribute
create operations (Print-URI) request:
Operational Attributes:
"job-name"
"ipp-attribute-fidelity"
"document-URI"
Job Attributes:
any Job Template attribute
create operations response (Create-Job, Print-Job, Print-URI):
Operational Attributes:
"status-message"
> Job Attributes:
"job-Id"
"job-URI"
> "job-name"
(model issue: why is job-name returned)
> "job-state"
> "job-state-reasons"
> "job-state-message"
"number-of-intervening-jobs"
> Unsupported Attributes:
> any unsupported attributes and any unsupported attribute values
Note: Job Attributes are returned only if status-code is successful-ok
or successful-ok-or-substituted-attributes.
Validate operation response :
Operational Attributes:
"status-message"
Unsupported Attributes:
any unsupported attributes and any unsupported attribute values
>
Get-Attributes operation request (for a Printer):
> Operational Attributes:
> "requested-attributes"
"document-format"
Get-Attributes operation request (to a Printer-URI for a Job):
Operational Attributes:
"job-id"
"requested-attributes"
Get-Attributes operation request (to a Job-URI for a Job):
Operational Attributes:
"requested-attributes"
> Get-Attributes operation response for a Job:
Operation Attributes:
"status-message"
> Job Attributes:
> the requested attributes that are supported
> Get-Attributes operation response for a Printer:
Operation Attributes:
"status-message"
> Printer Attributes:
> the requested attributes that are supported
>
> Get-Jobs operation request:
> Operation Attributes:
> "limit"
> "requested-attributes"
"which-jobs"
> Get-Jobs operation response:
Operation Attributes:
"status-message"
> Job Attributes:
> job attributes grouped by job in any order
NOTE: one set of Job Attributes for each job in the response.
> NOTE - The requester must request "job-uri" or "job-identifier" in order to
> be able to reference any returned job in a subsequent operation. They are
> not returned as operational attributes.
>
Send-Document operation request (to Printer-URI):
> Operation Attributes:
"job-id"
> "last-document"
"document-name" (the document-name goes here now)
> Document Attributes: ISSUE: These are no longer present, correct?
> Document Content:
Send-Document operation request (to Job-URI):
Operation Attributes:
"last-document"
"document-name" (the document-name goes here now)
Document Content:
Send-URI operation request (to Printer-URI):
Operation Attributes:
"job-id"
"last-document"
"document-name" (the document-name goes here now)
"document-uri"
Document Attributes: ISSUE: These are no longer present, correct?
Send-Document operation request (to Job-URI):
Operation Attributes:
"last-document"
"document-name" (the document-name goes here now)
"document-uri"
Send-Document and Send-URI operation response:
That is the same as the response from Print-Job.
Operation attributes:
"status-message"
> Job attributes:
> "job-name"
(should job-name be deleted)
> "job-state"
> "job-state-reasons"
> "job-state-mesage"
"number-of-intervening-jobs"
> Unsupported attributes:
> any unsupported attributes and any unsupported attribute values
>
> Cancel-Job operation
> Operation attributes:
> "message"
Cancel-Job response
Operation attributes
"status-message"
>
> List of issues raised:
>
> 1. For the Cancel-Job response, the Model document says "optional Status
> Message". What attribute or attributes are these?
>
> 2. MAY a create operation store the "ipp-attribute-fidelity" attribute on
> the Job object so that it can be queried later (or printed on a start
> sheet). How can a user or a help desk explain what happened, if
> "ipp-attribute-fidelity" cannot be stored? How can a knowledgable user
> determine whether his desktop client submits jobs with
> "ipp-attribute-fidelity" set to TRUE or FALSE, if the client doesn't expose
> this to the user?
>
> 3. MAY a create (or Send-Document) opeation store the unsupported attributes
> on the Job object for later query? How?
>
> 4. If a create operation implementation did store some of the operational
> attributes in the Job object, they could be directly queried by name or
> included in the "all" group.
>
> NOTE - an exception is made for "job-name" which is part of the
> "job-description" group as well as being an operational attribute and is
> required to be stored.
>
> 5. If an implementation receives an operational attribute with an
> unsupported value or receives an operational attribute that is not
> supported, does the implementation ignore the attribute or reject the job?
>
> 6. If the answer is to reject the job, is that dependent on the value of the
> "ipp-attribute-fidelity" attribute or not?
>
> 7. If the Printer MAY ignore the value, then maybe it shouldn't be in the
> Operational Attributes section and should be moved to the Job Attributes
> section?
>
> 8. How about future extensions that add operational attributes? Which
> version number changes? What about backward compatibility?
>
>