OK. Then you are saying that a scanner implementing PDF/Raster satisfies the IPP Scan requirement that “Scan Services MUST support generating Documents conforming to Document management — Portable document format — Part 1: PDF 1.7 [ISO32000] " ? In that case, one wonders why TWAIN /PDF would bother generating a new spec.
Sent from Mail for Windows 10
From: Michael Sweet
Sent: Tuesday, September 5, 2017 4:01 PM
To: wamwagner at comcast.net
Cc: Smith Kennedy; Paul Tykodi; ipp at pwg.org
Subject: Re: [IPP] PDF Raster and IPP Scan
But PDF Raster *IS* PDF, and meets the requirements of IPP Scan.
> On Sep 5, 2017, at 3:57 PM, wamwagner at comcast.net wrote:
> Understood that IPPScan requires PDF. My comment was that downgrading that requirement for scan services to PDF Raster would allow the lower end scanners that do not support full PDF (i.e. those devices for which PDF Raster is intended) to still implement and claim support for IPP Scan. Understood that it is unclear whether PDF Scan really allows for a significantly simpler scanner, it would appear that this TWAIN effort would enable a class of cloud-capable scanner that could not use IPP Scan. Indeed, it is unclear whether that would bother anyone.
>> Thanks, Bill Wagner
>> Sent from Mail for Windows 10
>> From: Michael Sweet
> Sent: Tuesday, September 5, 2017 8:12 AM
> To: William Wagner
> Cc: Smith Kennedy; Paul Tykodi; ipp at pwg.org> Subject: Re: [IPP] PDF Raster and IPP Scan
>> > On Sep 1, 2017, at 10:37 AM, wamwagner at comcast.net wrote:
> > By quick skim, PDF/Raster appears to be the raster capability the exists within PDF, with some additional restrictions. Not quite sure why it requires a separate specification, except for the comment that it is the file format required by “TWAIN Working Group’s new TWAIN Direct specification -- the first zero-footprint, cloud-based version of its royalty free open standard protocol that allows applications to talk directly to document scanners without the need for vendor specific drivers.” That us the rub and would suggest that IPP Everwhere/Scan would have some very serious competition, if we ever formalized it. The scanner industry has a long history using TWAIN and, as in other areas, it will tend to continue with what is familiar. Still, a common imaging protocol for MFDs may find some support.
> > The IPP Scan Service spec appears to require that Scan Services support PDF. Modifying that to allow lower end devices to support a PDF subset not be a major effort and might have some benefit in showing some degree of universality. Is there any product that uses IPP Scan?
>> I can't answer that specifically, but given that IPP Scan requires PDF support and this is a strict PDF subset, there would be no problems supporting it in an IPP Scan implementation. We could even register this spec using a pdf-versions-supported keyword value - no spec updates needed.
> Michael Sweet, Senior Printing System Engineer
Michael Sweet, Senior Printing System Engineer
-------------- next part --------------
An HTML attachment was scrubbed...