attachment-0002
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Paul,<div><br><div><div>On Jul 3, 2013, at 5:22 PM, Paul Tykodi <<a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a>> wrote:</div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><font color="#000000" face="Consolas" size="2">...</font><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On the other hand, should we ultimately decide to remove the Copy Service from the model as part of publishing SM 2.0, I would imagine that vendors who have expended effort to become compliant with a PWG specification (Copy Service 1.0) that in a short time lost its relevance might wonder whether the effort they expended to conform with a PWG specification that disappeared so quickly was warranted. By extension, this could quickly become an investigation into whether conforming to any PWG standards was warranted.<o:p></o:p></span></p><p class="MsoNormal"></p></div></div></blockquote><div dir="auto"><br></div><div dir="auto"><div>Every standards organization has a history of introducing major changes that affect shipping and in-development products. Every vendor knows (or should know) that new technology or methods are developed on a daily basis, and it is up to every vendor to choose which new technologies or methods they will adopt. So to say that "if the PWG obsoletes recent specifications for SM 2.0 then vendors will jump ship and go elsewhere" is a specious argument - vendors will choose to adopt (or not) our standards for their own reasons, and we can't be ruled by fear that changing direction after putting out a standard is going to make people run away from the PWG.</div><div><br></div><div>Our job as a standards organization is to a) define the best standards we can and b) make changes as needed to solve existing and new problems for the printing/printer industry. If that means we need to change direction from time to time, so be it. We, as the collected "experts" in our field, should we able to define what is technically the correct solution for all of our members - that includes business requirements, not just the technical requirements we usually talk about.</div><div><br></div><div>In this case we have identified issues with the Copy service (works differently than all other Job-based services) and FaxOut/EmailOut (insufficient support for hardcopy documents) that we need to work through collectively. If, collectively, we decide that Copy service is or is not needed, then that reflects the will and desire of each of our members. Similarly, we will collectively decide what to do with hardcopy documents. This will produce a new standard that reflects our best understanding of the model and semantics of an imaging device as a whole. To do any less would mean we are not living up to our charter as a standards organization.</div><div><br></div><div>But in any case, nothing prevents a vendor from continuing to use SM 1.0 + Copy Service indefinitely - we don't (and can't) enforce use of the latest specs.</div></div></div><div><br></div><div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 11pt;">For this reason, I think that it was useful for Pete to bring this element into the discussion for further consideration as we continue with the SM 2.0 project.</span></p></div></div></blockquote><div><br></div>Absolutely, and I'll reiterate that *I* have only brought up the *question* of whether we need a separate Copy service and the *issue* that hardcopy document support needs to be fixed/normalized in SM 2.0. My goal is not to specifically kill the Copy Service but to unify the SM so that we support hardcopy documents the same way across the model and expose the "optimal" set of services needed. There are valid arguments on both sides and we need to work through the details to determine whether a Print Service w/AddHardcopyDocument operation or a separate Copy Service with Jobs and Documents is the "right" way to go long-term.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -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; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div><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><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>