Thanks for your quick response, Mike. It might be worthwhile to articulate the rationale as to why these are required in the spec. I didn't pick up on all that during my read through.
From: Michael Sweet [mailto:msweet at apple.com]
Sent: Friday, September 6, 2013 7:00 AM
To: Justin Hutchings
Cc: ipp at pwg.org; Ira McDonald; Paul Tykodi
Subject: Re: [IPP] Microsoft has reviewed the IPP Transaction-Based Printing Extensions specification and has comments
Thank you for your feedback! Quick comments inline...
On Sep 5, 2013, at 6:06 PM, Justin Hutchings <justhu at microsoft.com<mailto:justhu at microsoft.com>> wrote:
- OpenXPS has a MIME type of application/oxps, not application/OpenXPS (http://www.iana.org/assignments/media-types/application/oxps)
Oops, will fix.
- This spec appears to have a bunch of content which is completely unrelated to the transaction based printing. Why are we throwing these into what would otherwise be a very straightforward, to-the-point spec?
These have particular application to commercial print services and service discovery.
These provide control over the final imposition/scaling of the document data on the output media - important particularly for commercial print services.
This is used for service discovery; we need to have a way to configure the service name.
This is used for service selection/filtering - again, if you are looking for a print service that supports the kind of document you are printing, you need this information.
(this is also part of the DNS-SD TXT record, but DNS-SD is not the only way to do discovery)
These are used to inform the Client of limits for direct photo and PDF printing - having dealt with a lot of commercial print shops over the years, it is VERY important for the Client to be able to know whether they support a particular flavor of PDF or have limits in the maximum size/dimensions of print files.
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
An HTML attachment was scrubbed...