[IPP] Outline of IPP Resource Object for System Service Spec

[IPP] Outline of IPP Resource Object for System Service Spec

[IPP] Outline of IPP Resource Object for System Service Spec

Ira McDonald blueroofmusic at gmail.com
Fri Sep 9 17:54:21 UTC 2016

Hi Mike,

Thanks for both replies.  I got stalled on editing for a few days, but
I did get a lot of this latest thinking in on Monday and Tuesday and
will return to editing this weekend.

I agree with all of your comments.

Pedantic DPA background stuff:

ISO-10175 Part 3 defines the Create operation on pages 10 to 15,
which normally results (for a Printer object) in a Printer with initial
state of 'unknown' (not an out-of-band value).

ISO-10175 Part 1 defines "printer-state" on pages 185 to 186 with
a long list of values (most of which were moved CORRECTLY to
"printer-state-reasons" in IPP) including the indeterminate state
of 'unknown'.

ISO-10175 Part 1 defines "current-job-state" on pages 125 to 126,
also including 'unknown'.

In DPA implementations at a printer vendor where I once consulted,
'unknown' was used as the initial state result of a Create operation
for either a Printer or a Job, because they wanted Create to return

- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
mailto: blueroofmusic at gmail.com
Jan-April: 579 Park Place  Saline, MI  48176  734-944-0094
May-Dec: PO Box 221  Grand Marais, MI 49839  906-494-2434

On Fri, Sep 9, 2016 at 12:00 PM, Michael Sweet <msweet at apple.com> wrote:

> Ira,
> > On Sep 6, 2016, at 8:25 PM, Ira McDonald <blueroofmusic at gmail.com>
> wrote:
> >
> > Hi Mike,
> >
> > Further thoughts about "resource-printer-id" and "resource-job-id".
> >
> > Delete them.  Several Printers and/or Jobs could need a Resource
> > (and would have a pointer to indicate that), but the Resource should
> > NOT have pointers.  That is, all Resources are (as we agreed) of
> > System scope and can only be managed (or state affected) by the
> > System Service.
> That makes sense for Jobs.  I'm not sure for Printers, where ICC profiles,
> icons, etc. might very well be Printer-specific.
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20160909/cae26965/attachment.html>

More information about the ipp mailing list