attachment-0001
<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 12 (filtered medium)">
<base href="x-msg://311/">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Monaco;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ira has pointed out that Mike’s message did not make it to the
list, so I forward it below.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bill Wagner<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michael Sweet
[mailto:msweet@apple.com] <br>
<b>Sent:</b> Thursday, February 11, 2010 5:42 PM<br>
<b>To:</b> wamwagner@comcast.net<br>
<b>Cc:</b> PWG, WIMS<br>
<b>Subject:</b> Re: [Pwg-Announce] Registration of additional PDLs in IANA
PrtInterpreterLangFamilyTC<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Feb 10, 2010, at 5:31 PM, <a
href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a> wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'> Greetings:<o:p></o:p></span></p>
</div>
<p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Arial","sans-serif";
color:black'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>At
the February WIMS Face-to-face meeting, it was agreed that, in line with
the standization of the IEEE 1284 Device ID COMMAND SET entry, it would
be desirable to have standard terms to identify more of
the prevalent PDL types and versions. The most reasonable way to do this is to
add them to the PrtInterpreterLangFamilyTC in the IANA Printer MIB (<a
href="http://www.iana.org/assignments/ianaprinter-mib">http://www.iana.org/assignments/ianaprinter-mib</a>)<o:p></o:p></span></p>
</div>
<p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Arial","sans-serif";
color:black'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>It
was suggested that JDF, JMF and PPML be added.<o:p></o:p></span></p>
</div>
<p style='margin:0in;margin-bottom:.0001pt'><span style='font-family:"Arial","sans-serif";
color:black'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>It
was also suggested that new entrys be added to be able to distinguish between
significantly different versions of common PDLs. Suggestions were:<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>PS2,
PS3, PCL3, PCL5e, PCL6 and various versions of PDF ( ISO 19005 [PDF/a],
ISO32000 [PDF1.7], PDF1.3, PDF1.5 and PDF/is were mentioned).<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I am ambivalent about adding a whole list of variants - for
example, "PCL3" isn't enough since (for example) HP's current
products use something called "PCL3GUI" to support RGB bitmap
printing - a significant difference. Similarly, PDF 1.4 and 1.6 are much
more prevalent than PDF 1.7, and in fact ISO 32000 and PDF 1.7 are not quite
the same thing. Adobe has also added extensions to ISO 32000 since its
publication, yet it is all just "PDF 1.7"...<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>For PostScript, I'm not sure that there are any new products
(or old products that would be updated) that support anything other than PS3,
so I'm not sure it is necessary to register PS2. Even if we did register PS2
support, there are a number of optional PS2 features that would also need to be
advertised (TrueType and CID font support, in particular) to make the
information useful.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>An alternate approach would be to *not* include this
information in the command set but instead have separate keys for the major
PDLs (PCL, PDF, and PS), or make them first-class attributes for IPP (and the
corresponding semantic model - "pdf-versions-supported",
"pcl-versions-supported", etc...) so that we can track major versions
and extensions needed for a client to know what kind of data the printer can
accept.<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Monaco","serif";
color:black'>___________________________________________________<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Monaco","serif";
color:black'>Michael Sweet, Senior Printing System Engineer<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Monaco","serif";
color:black'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></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>