<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; ">All,<div><br></div><div>I have just posted a clarifying policy document for PWG Prototyping to:</div><div><br></div><div><div> <a href="ftp://ftp.pwg.org/pub/pwg/general/process/pwg-prototype-policy-20121029.txt">ftp://ftp.pwg.org/pub/pwg/general/process/pwg-prototype-policy-20121029.txt</a></div></div><div><br></div><div><div>Historically the PWG has relied upon implementers to post a message to the corresponding working group list, present slides at a PWG face-to-face meeting, or post a public implementation of some sort to document the existence of a prototype. However, since many companies are hesitant to publicly announce this information, we may not be seeing the full breadth of prototyping that happens for PWG standards, and in some cases the lack of prototype disclosures has caused delays for standards in development.</div></div><div><br></div><div>This policy formalizes our previous informal notification policy for prototypes of our standards and adds a new process that allows interested (but shy) implementers to report their prototyping to the PWG anonymously.</div><div><br></div><div>This policy was generated and reviewed by the PWG steering committee.</div><div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; border-spacing: 0px; "><div>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
<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.