Hi Mike,
From: Michael Sweet <msweet at msweet.org>
Sent: Thursday, June 4, 2020 11:41 AM
To: Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy at hp.com>
Cc: Jeremy Leber <jeremy.leber at lexmark.com>; PWG IPP Workgroup <ipp at pwg.org>
Subject: Re: [IPP] Slides to discuss feature compatibility topics for IPP EPX
Smith,
> On Jun 4, 2020, at 12:16 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp at pwg.org<mailto:ipp at pwg.org>> wrote:
>> Hi Jeremy,
>> Good question! The way Proof Print had been defined in 5100.11, the “proof-print” Job Template attribute MUST be removed from the copy of the retained job that will conclude the Proof Print, with the intention that the Printer will not retain the Job copy since it lacks its own “proof-print” Job Template attribute. The goal is to not change this in EPX.
I believe the current semantics are if you send a Resubmit-Job operation, the new Job inherits all but the proof-print Job Template attribute, which means that a job-retain-until/-time/-interval attribute in the request (or the corresponding xxx-default value) will apply to the copy. Thus, the copy of the proof Job *could* also be retained, but only as a side-effect of the job-retain attributes.
[S.Kennedy] Yep that is true – if there are other attributes such as “job-retain-until”, then the Job copy will persist longer than a “normal” Job. But it will NOT be listed in a Get-Jobs (“which-jobs” = ‘proof-print’).
> Your question led me to wonder if there are “job accounting” attributes (Job Status attributes) that indicate that a Job is a copy of another Job to construct the audit trail?
Not at present, although I do remember having a discussion about adding a "parent-job-id" attribute at some point for this very reason. It doesn't look like it actually made it into JPS2, so that might be something to consider adding for EPX. (and then parent-job-id and parent-job-uuid for "fun")
[S.Kennedy] I’ll add “parent-job-id” and “parent-job-uuid” to EPX. Should the parent also have a Job Status attribute “copy-job-ids” and “copy-job-uuids”?
>> Smith
>>>>> From: Jeremy Leber <jeremy.leber at lexmark.com<mailto:jeremy.leber at lexmark.com>>
> Sent: Thursday, June 4, 2020 9:41 AM
> To: PWG IPP Workgroup <ipp at pwg.org<mailto:ipp at pwg.org>>; Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy at hp.com<mailto:smith.kennedy at hp.com>>
> Subject: Re: Slides to discuss feature compatibility topics for IPP EPX
>> Hi Smith,
>> This has probably already been discussed, but would proof print jobs remain in storage (to allow further attempts) after the second "completed" state, or are they removed from storage at that point?
>> Thanks,
> Jeremy
>> Jeremy Leber
> Area Owner, Network & Mobile Firmware Development
>> O +1 859 825-4505
>jeremy.leber at lexmark.com<mailto:jeremy.leber at lexmark.com>
>>> www.lexmark.com<http://www.lexmark.com>
> From: ipp <ipp-bounces at pwg.org<mailto:ipp-bounces at pwg.org>> on behalf of Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp at pwg.org<mailto:ipp at pwg.org>>
> Sent: Thursday, June 4, 2020 11:31 AM
> To: PWG IPP Workgroup <ipp at pwg.org<mailto:ipp at pwg.org>>
> Subject: [IPP] Slides to discuss feature compatibility topics for IPP EPX
>> Greetings,
>> I’m currently trying to author the IPP EPX section that describes compatibility between the Job Release, Job Storage and Proof Print features. I’ve posted some slides for a future discussion of IPP EPX features and their compatibility with one another. I’d like to review and discuss so that I make sure I’ve thought of all of the corner cases and issues. I know this is last minute – I’m not anticipating that we look at it today, but we can if time permits.
>>https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-epx-feature-compatibility-investigation-20200604.pdf<https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-epx-feature-compatibility-investigation-20200604.pdf>
>> Smith
>> /**
> Smith Kennedy
> HP Inc.
> */
>>>> _______________________________________________
> ipp mailing list
>ipp at pwg.org<mailto:ipp at pwg.org>
>https://www.pwg.org/mailman/listinfo/ipp<https://www.pwg.org/mailman/listinfo/ipp>
________________________
Michael Sweet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20200604/bce14cb8/attachment.html>