[IPP] Potential errata/update for PWG Raster Format and/or IPP Everywhere specs

[IPP] Potential errata/update for PWG Raster Format and/or IPP Everywhere specs

[IPP] Potential errata/update for PWG Raster Format and/or IPP Everywhere specs

Ira McDonald blueroofmusic at gmail.com
Fri May 23 15:21:44 UTC 2014

Hi Smith,

Actually, the Printer doesn't have to bind values to "xxx-actual" until the

This reply is not about 'guaranteed'.

This reply is about the usability of 'attempted'.

An IPP Client could use Validate-Job with "document-format" and
"pdl-override" and,
when it receives the response that says ignored or substituted, examine the
of "preferred-attributes" (from JPS3, PWG 5100.13-2012) to find out the
extent to
which the Printer *could* and *could not* successfully 'attempt' to do the

The IPP Client wants to know if the particular PDL interpreter is
instrumented to
support overrides, not that any particular (unsent) document data actually
for example, "number-up" (which the client can't know if it didn't generate
document data).

Mike - I think this is a useful idea - WDYT?

- 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
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434

On Wed, May 21, 2014 at 4:33 PM, Kennedy, Smith (Wireless Architect) <
smith.kennedy at hp.com> wrote:

> On 2014-05-21, at 2:23 PM, Michael Sweet <msweet at apple.com> wrote:
> On May 21, 2014, at 3:23 PM, Ira McDonald <blueroofmusic at gmail.com> wrote:
> ...
> Although one could do tricks with Client submitting a Job on hold and
> Printer sending "successful-ok-ignored-or-substituted-attributes" (so
> that the client could tell that the override was partial and WHERE it
> wasn't performed).
> ... and in cases where job hold/release is not supported, the xxx-actual
> attributes can be used to track things as well - I think Smith already says
> something about this in the 'guide.  Of course, that presumes that the IPP
> Printer has access to the values used by the PDL for a given job - probably
> more likely than being able to do PDL override from my experience, but
> still not 'guaranteed' (there's that word again...)
> And as we have discussed, since the Printer doesn’t bind values to
> xxx-actual until processing time or perhaps slightly earlier in some cases,
> this is basically “after the fact”.  This may tell the Client whether
> something was used or not, but doesn’t allow the Client to try to do
> something about it or have a sense before processing of what will happen at
> processing time.
> Smith
> _______________________________________________
> ipp mailing list
> ipp at pwg.org
> https://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140523/17baa9b8/attachment.html>

More information about the ipp mailing list