attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Ira,<div><br><div><div>On Dec 9, 2013, at 3:04 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div>Hi Mike,<br><br></div>I like your clarifications as suggested.<br><br></div>Are you suggesting a *tiny* document that updates JPS3 and extends<br></div>Identify-Printer?<br></div></div></div></div></div></div></blockquote><div><br></div>No, I really don't want to open up that can of worms.</div><div><br><blockquote type="cite"><div dir="ltr"><div><div><div><div>It seems like it would be nice to handle this as a minor release update<br></div>to JPS3 (so that everyone sees it). I know, process...process. But this<br></div>seems like the cleaner fix to me.<br></div></div></div></blockquote><div><br></div></div><div>I know I don't have the cycles or the energy to update JPS3 right now. Given our recent move to start accepting value registrations on the mailing list (with the mailing list serving as the durable source of information), I was hoping we could simply treat these as new value registrations for existing attributes and do the registration. Both attributes are type2 and permit extension without full standards backing them...</div><div><br></div><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">_______________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div>
</div>
<br></div></body></html>