The classic (RFC 2911) approach would be that "requesting-user-name"
is only an operation and not Job object attribute. The modern (IPP/2.0 SE)
approach would be to also list the required/allowed operation attributes.
I prefer the modern approach.
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
mailto:blueroofmusic at gmail.com
Christmas through April:
579 Park Place Saline, MI 48176
May to Christmas:
PO Box 221 Grand Marais, MI 49839
On Wed, Jan 19, 2011 at 1:25 AM, Michael Sweet <msweet at apple.com> wrote:
>> In reviewing some implementation details of JPS2, I have a question about
> the contents of the job-creation-attributes-supported attribute.
> Specifically I am wondering about the requesting-user-name operation
> attribute - normally this gets mapped to the job-originating-user-name job
> description attribute, however based on the definition in section 10.1 it
> would seem that "requesting-user-name" attribute should not be listed since
> it is not (strictly speaking) a job attribute.
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...