I have a draft of IPP Enterprise Printing Extension (EPE) I'm chipping away at - here's what it has thus far:
Added:
job-password-length-supported (from Job Password Repertoire registration)
job-password-repertoire-configured/-supported (from Job Password Repertoire registration)
job-print-password/-default/-supported (to be debated)
job-storage/-default/-supported (to be debated)
Removed:
feed-orientation/-default/-supported
job-save-disposition/-etc (all related Job Template, Job Description and Printer Description attributes)
job-creation-attributes-supported
job-hold-until-time/-supported
job-ids/-supported (REQUIRED)
job-spooling-supported
media-col.media-tooth
media-col.media-grain
media-col.media-thickness
media-col-database
printer-detailed-status-messages
which-jobs-supported
Cancel-Jobs
Cancel-My-Jobs
Close-Job
Kept:
job-password
job-password-encryption
proof-print/-default/-supported
Additional keywords for "which-jobs" ('proof-print' and 'stored' defined locally, 'saved' to be deprecated)
I have a few questions too:
Questions:
job-cancel-after/-default/-supported --> Job Extensions v1.1? If not, why not?
job-delay-ouptut-until/-default/-supported --> Job Extensions v1.1? If not, why not?
job-delay-output-until-time/-supported --> Job Extensions v1.1? If not, why not?
job-phone-number/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...)
job-recipient-name/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...)
job-retain-until/-default/-supported --> Job Extensions v1.1? If not, why not?
job-retain-until-time/-default/-supported --> Job Extensions v1.1? If not, why not?
> On Feb 28, 2019, at 3:17 PM, Michael Sweet <msweet at apple.com> wrote:
>> These all have a clear focus on jobs and job submission/creation and are definitely not limited to the scope of Enterprise Printing. There is a slight process issue we need to discuss, however: the new Job Extensions will have conformance requirements for required operations and attributes that were not in v1.0 of Job Extensions but *were* in v1.0 of JPS2 - the errata process doesn't allow us to change conformance requirements without going through PWG Last Call and Formal Vote, but then we are kindof merging JOBEXT and JPS2 into a single errata update and publishing a new Enterprise Printing specification with updated JPS2 content. Fuzzy logic... :)
We should account for this in Process 4.0 somehow.
>> Anyways, since this constitutes all of the non-obsoleted/migrated content from JPS2, I'd prefer to update things in one shot rather than processing two documents.
+1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190306/2ec27f10/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190306/2ec27f10/attachment.sig>