attachment

Hi Glen, I respectfully disagree with your whole premise. The PWG collaborated very successfully with Adobe to develop PWG PDF/is - a subset and a profile of Adobe�PDF. While PDF/1.7 later became the ISO 32000 standard, in 2004 the PWG was delighted to collaborate with our lead editor Rick Seeler from Adobe on PDF/is. I see no reason to treat PWG CUPS Raster any differently. Names of attributes (prefixes) are probably suitable discussion topics. But the idea that PWG should only specify a PWG raster format from scratch would set a bad precedent. Cheers, - Ira 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 <a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a> <a style="color: rgb(102, 0, 204);" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a> mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a> Christmas through April: � 579 Park Place� Saline, MI� 48176 � 734-944-0094 May to Christmas: � PO Box 221� Grand Marais, MI 49839 � 906-494-2434<div style="display: inline;"></div><div style="display: inline;"> </div><div style="display: inline;"></div> <div class="gmail_quote">On Tue, Feb 1, 2011 at 11:24 AM, Petrie, Glen <<a href="mailto:glen.petrie@eitc.epson.com">glen.petrie@eitc.epson.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div link="blue" vlink="purple" lang="EN-US"> <div> I have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster" � 1.�� It was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation a.�� Thus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-source or vendor product is not in line with PWG standards practices.� This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with ties to a specific open-source or vendor product.� Also, it should not use attribute names or variables that are identified with a specific open-source or vendor product. b.�� I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity. 2.�� The specific open-source or vendor product that is being discussed is CUPS.� So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL.� a.�� I have not heard or know that Apple has provided a Letter of Assurance on the use by others for the use a subset of CUPS definition.� While, I believe that Apple would provide LOA upon request. b.�� On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/is under GPL before Apple�s ownership; then there is the question if GPL license applies.� Major print vendors may be at risk of either having to release their source code that is associated with CUPS content or even being sued by GPL proponents.� � � Glen<div><div></div><div class="h5"> � � � -----Original Message----- From: <a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a> [mailto:<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>] On Behalf Of Michael Sweet Sent: Wednesday, January 26, 2011 11:10 PM To: <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a> Cc: <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a> Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted � All, � I have posted a new version of the IPP Raster specification at: � �� <a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx</a> �� <a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf</a> �� <a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf</a> � This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP... � ________________________________________________________________________ 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 <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a> <a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a> </div></div></div><div><div></div><div class="h5"> -- This message has been scanned for viruses and dangerous content by <a href="http://www.mailscanner.info/" target="_blank">MailScanner</a>, and is believed to be clean. </div></div></div> _______________________________________________ ipp mailing list <a href="mailto:ipp@pwg.org">ipp@pwg.org</a> <a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a> </blockquote></div> <div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup{position: absolute;z-index: 9999;padding: 0px 0px;margin-left: 0px;margin-top: 0px;overflow: hidden;word-wrap: break-word;color: black;font-size: 10px;text-align: left;line-height: 130%;}</style> -- This message has been scanned for viruses and dangerous content by <a href="http://www.mailscanner.info/">MailScanner</a>, and is believed to be clean.