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)">
<base href="x-msg://195/">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>It does not really clear things up for me,
sorry. I guess I still see a PWG standard being based on an element (headers
and code) of vendor product that has origins as GPL code.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Alternatives: While I do not know of “vendor,
industry or group standard” with an acceptable job/”raster”
(really, job/image (really, job/content)) format that is similar to CUPS raster,
I would suggest something like the following.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Format: Job Ticket, <Page Overrides, Page
content (image or maybe something else) …….. n-number of pages><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Job Ticket content == JTAPI from OpenPrinting
(CPL License and completely available to all to use without GPL “hooks”
or concerns). <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> Note
JTAPI was derived to be consistent with IPP!!!<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Page
overrides == only those JTAPI elements that need
individual page override<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Page
content == Byte-wise Run-Length
compressed “sRGB” or other image/color-space data format(s).
In future, this is extensible to other data formats that could include vector,
jpeg, etc<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>This has the same objective as CUPS raster
but is based on public standards and code elements that have free licenses.
There already exist CPL based header file for JTAPI job elements and an approved
public standard. The standard provides compliance for mobile, <st1:place
w:st="on">SOHO</st1:place>, office and production printing domains/applications.
This approach could reduce the 1800 bytes / page overhead of CUPS Raster 2 to a
few bytes if no page override needed (the most likely use case) along with
alignment of other small details in CUPS raster.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Glen<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Michael Sweet
[mailto:msweet@apple.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, February 02, 2011
12:16 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Petrie, Glen<br>
<b><span style='font-weight:bold'>Cc:</span></b> ipp@pwg.org; cloud@pwg.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [IPP] New draft of
IPP Subset of CUPS Raster (IPP Raster)specification posted</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Glen,<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>In response to your concerns:<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>1. PWG Process 3.0 (<a
href="http://www.pwg.org/chair/membership_docs/pwg-process30.pdf">http://www.pwg.org/chair/membership_docs/pwg-process30.pdf</a>)
does not specify that a PWG standard must be an original creation of the PWG or
that it cannot be based on an existing vendor, industry, or group standard. In
fact, most PWG standards are necessarily based on existing standards from
different sources. That said, if you have an alternative existing format you
would like to propose as an alternative to CUPS Raster, please do so now.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>2. The reference implementation of CUPS Raster is provided under
version 2 of the GNU LGPL and nothing would prevent a vendor from doing an
independent implementation under alternative terms. Also, since CUPS Raster has
not been formally included in any PWG standard to date, Apple naturally has not
provided a LOA for that IP (yet).<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hope this clears things up!<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Feb 1, 2011, at 6:24 AM, Petrie, Glen wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><span
style='orphans: 2;widows: 2;-webkit-border-horizontal-spacing: 0px;-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;word-spacing:0px'>
<div link=blue vlink=purple>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>I have reviewed the new proposed standard and have
two concerns with respect to the "IPP Subset of CUPS Raster"<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div style='margin-left:.5in'>
<p class=MsoNormal style='text-indent:-.25in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>1.</span></font><font
size=1><span style='font-size:7.0pt'> <span
class=apple-converted-space> </span></span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>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></span></font></p>
<u1:p></u1:p></div>
<div style='margin-left:1.0in'>
<p class=MsoNormal style='text-indent:-.25in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>a.</span></font><font
size=1><span style='font-size:7.0pt'> <span
class=apple-converted-space> </span></span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>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></span></font></p>
<u1:p></u1:p></div>
<div style='margin-left:1.0in'>
<p class=MsoNormal style='text-indent:-.25in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>b.</span></font><font
size=1><span style='font-size:7.0pt'> <span
class=apple-converted-space> </span></span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>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></span></font></p>
<u1:p></u1:p></div>
<div style='margin-left:.5in'>
<p class=MsoNormal style='text-indent:-.25in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>2.</span></font><font
size=1><span style='font-size:7.0pt'> <span
class=apple-converted-space> </span></span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>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></span></font></p>
<u1:p></u1:p></div>
<div style='margin-left:1.0in'>
<p class=MsoNormal style='text-indent:-.25in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>a.</span></font><font
size=1><span style='font-size:7.0pt'> <span
class=apple-converted-space> </span></span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>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></span></font></p>
<u1:p></u1:p></div>
<div style='margin-left:1.0in'>
<p class=MsoNormal style='text-indent:-.25in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>b.</span></font><font
size=1><span style='font-size:7.0pt'> <span
class=apple-converted-space> </span></span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>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></span></font></p>
<u1:p></u1:p></div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Glen<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>-----Original Message-----<br>
From:<span class=apple-converted-space> </span><a
href="mailto:ipp-bounces@pwg.org">ipp-bounces@pwg.org</a><span
class=apple-converted-space> </span>[mailto:ipp-bounces@pwg.org] On Behalf
Of Michael Sweet<br>
Sent: Wednesday, January 26, 2011 11:10 PM<br>
To:<span class=apple-converted-space> </span><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
Cc:<span class=apple-converted-space> </span><a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>
Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification
posted<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>All,<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>I have posted a new version of the IPP Raster
specification at:<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'> <span class=apple-converted-space> </span><a
href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx</a><u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'> <span class=apple-converted-space> </span><a
href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf</a><u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'> <span class=apple-converted-space> </span><a
href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf</a><u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>This version incorporates all of the feedback from
the IPP telecon including the rename from PWG to IPP...<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>________________________________________________________________________<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Michael Sweet, Senior Printing System Engineer, PWG
Chair<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>--<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>This message has been scanned for viruses and<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>dangerous content by MailScanner, and is<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>believed to be clean.<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><u1:p> </u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>_______________________________________________<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>ipp mailing list<u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><u1:p></u1:p><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'><a href="https://www.pwg.org/mailman/listinfo/ipp">https://www.pwg.org/mailman/listinfo/ipp</a><u1:p></u1:p><o:p></o:p></span></font></p>
</div>
</div>
</blockquote>
</div>
</span>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div><span style='orphans: 2;text-align:auto;widows: 2;-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:
0px'>
<div>
<p class=MsoNormal><font size=4 color=black face=Helvetica><span
style='font-size:13.5pt;font-family:Helvetica;color:black'>________________________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></span><o:p> </o:p></span></font></p>
</div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>