attachment

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=blue> <div class=Section1> I would like to add this to the agenda as a discussion item during the IPP F2F session.  If the group decides, it should not be discussed, I will retract my request.<o:p></o:p> <o:p> </o:p> Thanks, Glen<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: Ira McDonald [mailto:blueroofmusic@gmail.com] Sent: Tuesday, February 01, 2011 9:17 AM To: Petrie, Glen; Ira McDonald Cc: Michael Sweet; ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted<o:p></o:p> </div> <o:p> </o:p> 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 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:   <st1:address w:st="on"><st1:Street w:st="on">579 Park Place</st1:Street>  <st1:City w:st="on">Saline</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">48176</st1:PostalCode></st1:address>   734-944-0094 May to Christmas:   <st1:address w:st="on"><st1:Street w:st="on">PO Box</st1:Street> 221</st1:address>  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State> <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place>   906-494-2434<o:p></o:p> <o:p></o:p> <div> 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:<o:p></o:p> <div link=blue vlink=purple> <div> I have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster"<o:p></o:p>  <o:p></o:p> 1.    It was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation<o:p></o:p> 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.<o:p></o:p> 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.<o:p></o:p> 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.  <o:p></o:p> 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.<o:p></o:p> 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.   <o:p></o:p>  <o:p></o:p> Glen<o:p></o:p> <div> <div>  <o:p></o:p>  <o:p></o:p>  <o:p></o:p> -----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<o:p></o:p>  <o:p></o:p> All,<o:p></o:p>  <o:p></o:p> I have posted a new version of the IPP Raster specification at:<o:p></o:p>  <o:p></o:p>     <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><o:p></o:p>     <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><o:p></o:p>     <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><o:p></o:p>  <o:p></o:p> This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP...<o:p></o:p>  <o:p></o:p> ________________________________________________________________________<o:p></o:p> Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p>  <o:p></o:p>  <o:p></o:p> -- <o:p></o:p> This message has been scanned for viruses and<o:p></o:p> dangerous content by MailScanner, and is<o:p></o:p> believed to be clean.<o:p></o:p>  <o:p></o:p> _______________________________________________<o:p></o:p> ipp mailing list<o:p></o:p> <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><o:p></o:p> <a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><o:p></o:p> </div> </div> </div> <div> <div> -- 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. <o:p></o:p> </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><o:p></o:p> </div> <o:p> </o:p> </div> -- 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. </body> </html>