attachment-0002
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>Exactly…that was my thinking as well.<div><br></div><div>When we move a print service from a "local" network to "The Cloud", it really becomes a network transport and AAA problem, which seems a separate realm from the PWG semantic model.</div><div><br></div><div>I would think there would be no impact on a "job ticket"</div><div><br></div><div>I think this may be the case that Bill W. mentioned in a previous email….for a lack of another group to take up the job ticket work, this work was relegated to the cloud group -- I think I remember something about it, but from a schedule perspective, I'm assuming that the two efforts (cloud and job ticket) are separate, and that it's possible to advance one without the other.</div><div><br></div><div>Randy</div><div><br></div><div><br><div><div>On Sep 24, 2012, at 6:31 PM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Randy,<div><br><div><div>On 2012-09-24, at 6:26 PM, Randy Turner <<a href="mailto:rturner@amalfisystems.com">rturner@amalfisystems.com</a>> wrote:</div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font>...</font></div><div>Regarding your earlier email statement (above), I was under the impression that there was nothing that needed to be "adapted". Meaning, we would like a Cloud printer to behave pretty much the same way we would any other print service (like on an internal enterprise network). This was based on a discussion at the last face-to-face meeting ( I believe ).</div></div></blockquote><div><br></div>From the Client perspective, this remains to be the case. Client prints to Cloud service and that service looks just like a printer.</div><div><br></div><div>However, the Cloud to Printer interface is different than we've supported before, mainly because we want a firewall/router-friendly interface and not something that needs to be "punched" through to allow for communications.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></div></div></blockquote></div><br></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>