I assume something will be done to correct the state transition descriptions for the Document spec and the PWG Semantic Model…
Peter Zehler
Xerox Corp.
Global Development Group
800 Phillips Rd, 111-04A
Webster NY, 14580-9701
Email: Peter.Zehler at Xerox.com<mailto:Peter.Zehler at Xerox.com>
Office: +1 (585) 265-8755<tel:%2B1%20%28585%29%20265-8755>
Fax: +1 (585) 422-0238<tel:%2B1%20%28585%29%20265-8755>
Mobile: +1 (585) 329-9508<tel:%2B1%20%28585%29%20329-9508>
From: Michael Sweet [mailto:msweet at apple.com]
Sent: Thursday, April 30, 2015 11:57 PM
To: Zehler, Peter
Cc: Manchala, Daniel; ipp at pwg.org
Subject: Re: [IPP] Multi-document job questions...
One additional note: IPP INFRA adds the document-state 'processing-stopped'.
On Apr 23, 2015, at 4:41 AM, Zehler, Peter <Peter.Zehler at xerox.com<mailto:Peter.Zehler at xerox.com>> wrote:
The specification “PWG 5100.5-2003 Standard for IPP Document Object” covers the Document and associated semantics. Additional comments below.
Peter Zehler
Xerox Corp.
Global Development Group
800 Phillips Rd, 111-04A
Webster NY, 14580-9701
Email: Peter.Zehler at Xerox.com<mailto:Peter.Zehler at Xerox.com>
Office: +1 (585) 265-8755<tel:%2B1%20%28585%29%20265-8755>
Fax: +1 (585) 422-0238<tel:%2B1%20%28585%29%20265-8755>
Mobile: +1 (585) 329-9508<tel:%2B1%20%28585%29%20329-9508>
From: ipp-bounces at pwg.org<mailto:ipp-bounces at pwg.org> [mailto:ipp-bounces at pwg.org] On Behalf Of Manchala, Daniel
Sent: Wednesday, April 22, 2015 3:32 PM
To: 'ipp at pwg.org<mailto:ipp at pwg.org>'
Subject: [IPP] Multi-document job questions...
RFC 2911 describes a multi-document job:
1. The Send-Document Request operation used for multi-document jobs has a laundry list of Operation Attributes (requesting-user-name, document-name, compression, document-format, etc). Does the IPP submission application ever query the printer to view these document attributes? Or is the IPP submission application restricted to querying the job attributes (of the job that contains the said documents)?
<PZ>The “Get-Document-Attributes” is available to the submission application.</PZ>
2. Is there any status related to Documents? (Other than the Send-Document Response associated with the Send-Document Request?)
<PZ>Similar to a Job the Document object has state. The Document object contains “document-state” and “document-state-reasons” elements to represent the object’s state. See “PWG 5108.01-2011 MFD Model and Common Semantics” section 7.2.3 for the detail on Document States and State Transitions.</PZ>
3. Is there any state related to Documents?
<PZ>Document states are simpler than the Job states. The two non-terminating states are ‘Pending’ and ‘Processing’. The terminating states are ‘Aborted’, ‘Canceled’ and ‘Completed’.</PZ>
4. Would a human operator expect to see Documents contained within multi-document jobs as individual entities at the printer? Or is that left as a detail of the printer implementation?
<PZ>UI design is the purview of the implementer. However it should be noted that a Document is a passive object whereas a Job is an active object. In the IPP model it is Jobs that are scheduled and run. Documents only exist within the Job and can only be processed within a processing Job. Documents can be managed (e.g., cancelled, modified) individually.</PZ>
_______________________________________________
ipp mailing list
ipp at pwg.org<mailto:ipp at pwg.org>
https://www.pwg.org/mailman/listinfo/ipp
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20150501/ed53db14/attachment.html>