attachment-0001
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:"Andale Mono";
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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Mike,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For this particular specification, I think we should consult information from the UP³I and potentially PODi organizations as well.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/Paul<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>--</span><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Paul Tykodi<br>Principal Consultant<br>TCS - Tykodi Consulting Services LLC<br><br>Tel/Fax: 603-343-1820<br>Mobile: 603-866-0712<br>E-mail: <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a></span><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>WWW: </span><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><a href="http://www.tykodi.com/" target="_blank"><span style='font-family:"Arial","sans-serif"'>http://www.tykodi.com</span></a></span><span style='font-size:11.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"'> ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] <b>On Behalf Of </b>Michael Sweet<br><b>Sent:</b> Tuesday, May 21, 2013 10:45 AM<br><b>To:</b> ipp@pwg.org<br><b>Subject:</b> [IPP] RFC: Proposed errata for PWG 5100.3 (Production Printing)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As discussed in last week's session, there is no easy migration from the finishings attribute (1setOf type2 enum) to the finishings-col attribute (1setOf collection).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The primary issue is that the finishing-template member attribute is defined as a name value and does not support well-known keyword values. I propose that we amend the definition of the finishing-template member attribute and finishing-template-supported Printer attribute to include type2 keywords, e.g.:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> "finishings-col (1setOf collection)"<o:p></o:p></p></div><div><p class=MsoNormal> "finishing-template (name(MAX) | type2 keyword)" <--- NEW<o:p></o:p></p></div><div><p class=MsoNormal> "stitching (collection)"<o:p></o:p></p></div><div><p class=MsoNormal> "stitching-locations (1setOf integer(0:MAX))"<o:p></o:p></p></div><div><p class=MsoNormal> "stitching-offset (integer(0:MAX))"<o:p></o:p></p></div><div><p class=MsoNormal> "stitching-reference-edge (type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> "finishing-template-supported (1setOf (name(MAX) | type2 keyword))" <--- NEW<o:p></o:p></p></div><div><p class=MsoNormal> "finishings-col-supported (1setOf type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal> "stitching-locations-supported (1setOf (integer(0:MAX) | rangeOfInteger(0:MAX)))"<o:p></o:p></p></div><div><p class=MsoNormal> "stitching-offset-supported (1setOf (integer(0:MAX) | rangeOfInteger(0:MAX)))"<o:p></o:p></p></div><div><p class=MsoNormal> "stitching-reference-edge-supported (1setOf type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The keyword values would correspond to the finishings enum names (staple, punch, bale, etc.).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Longer term we should also probably extend the finishings-col Job Template attribute to include fold, punch, and trim member attributes, which would make use of the same kinds of values as as the current "stitching" member attribute (which IIRC handles bind, edge stitch, and staple, although that too could be made explicit), for example:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> "finishings-col (1setOf collection)"<o:p></o:p></p></div><div><div><p class=MsoNormal> "fold (1setOf collection)" (list of folds)<o:p></o:p></p></div><div><p class=MsoNormal> "fold-direction (type2 keyword)" (in/out or up/down)<o:p></o:p></p></div><div><div><p class=MsoNormal> "fold-location (integer(0:MAX))"<o:p></o:p></p></div><div><p class=MsoNormal> "fold-reference-edge (type2 keyword)"<o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> "punch (collection)"<o:p></o:p></p></div><div><div><p class=MsoNormal> "punch-locations (1setOf integer(0:MAX))"<o:p></o:p></p></div><div><p class=MsoNormal> "punch-offset (integer(0:MAX))"<o:p></o:p></p></div><div><p class=MsoNormal> "punch-reference-edge (type2 keyword)"<o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> "trim (1setOf collection)" (list of cuts)<o:p></o:p></p></div><div><div><p class=MsoNormal> "trim-location (1setOf integer(0:MAX))"<o:p></o:p></p></div><div><p class=MsoNormal> "trim-reference-edge (type2 keyword)"<o:p></o:p></p></div></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> "fold-direction-supported (1setOf type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal> "fold-location-supported (1setOf (integer(0:MAX) | rangeOfInteger(0:MAX)))"<o:p></o:p></p></div><div><p class=MsoNormal> "fold-reference-edge-supported (1setOf type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> "punch-locations-supported (1setOf (integer(0:MAX) | rangeOfInteger(0:MAX)))"<o:p></o:p></p></div><div><p class=MsoNormal> "punch-offset-supported (1setOf (integer(0:MAX) | rangeOfInteger(0:MAX)))"<o:p></o:p></p></div><div><p class=MsoNormal> "punch-reference-edge-supported (1setOf type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> "trim-location-supported (1setOf (integer(0:MAX) | rangeOfInteger(0:MAX)))"<o:p></o:p></p></div><div><p class=MsoNormal> "trim-reference-edge-supported (1setOf type2 keyword)"<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That said, I think extending finishings-col needs to happen in a separate (small) spec, and we should look to other specs (e.g. JDF and MSPS) to make sure we aren't defining something completely out in left field.<o:p></o:p></p></div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thoughts?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Andale Mono","serif";color:black'>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><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. <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>