attachment
<html><head><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>There may be arguments about the definition of REST, but the RESTful semantics are not going away<div><br></div><div>The IETF is building their “internet of things” technology on RESTful semantics - they have yet to sell that outside the IETF, so we’ll see what wins. Further, Facebook, Google, and Twitter APIs are all RESTful.</div><div><br></div><div>R.</div><div><br></div><div><div><div>On Sep 17, 2014, at 3:15 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div><div>Hi,<br><br></div>I agree with all Mike's summary points below.<br><br></div>The selection of an available FaxInJobTicket is based on the Metrics<br></div>structure (which Pete worked out). I don't see any service configuration <br>issues (for a NON-Cloud binding).<br></div><br></div>With respect to bindings, there is no other game in town in the PWG<br></div>except IPP bindings. No printer vendor has ever publicly announced<br>the shipping of an Web Service binding that conforms to the PWG SM<br></div>schema.<br><br></div>Cheers,<br></div>- Ira<br><br><div class="gmail_extra"><div>PS - A note of caution about PWG developing so-called "RESTful"<br></div><div>bindings to anything. There's a religious war going on currently on<br>the IETF Apps Area WG mailing list about a simple request for a<br></div><div>concise definition of "REST" - one camp admits that there is *no*<br>simple definition and wants their idol left alone - the other camp is<br></div><div>getting tired of hearing about "REST" that nobody can define - it's<br></div><div>only a matter of time before this escalates to the IESG itself.<br></div>
<br><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 1:48 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Bill,<div><br></div><div>The Cloud Service Management Operations are directed to the Cloud service and only manage the Cloud service. We don't relay them through the Proxy to the Local service and have no way to do so in the current model - all out of scope for a long time. Similarly, there is no way to remotely manage the Proxy - out of scope.</div><div><br></div><div>All client-initiated job-based services that span between the Cloud and Local services are in scope for the Cloud Imaging Requirements and Model:</div><div><br></div><div>- FaxIn does not span and jobs are not client-initiated. It should be out of scope.</div><div><br></div><div>- FaxOut MAY span and has client-initiated jobs. Cloud-based FaxOut through a Local service should be in scope. Purely Cloud FaxOut (with the fax modem in the cloud too) is the same as SM FaxOut and should be out of scope. Similarly, FaxOut from the Local Device should be out of scope since either a) the Cloud isn't involved or b) it *is* involved in some way, but not using the interface in this document.</div><div><br></div><div>- Print spans and has client-initiated jobs. It should be in scope.</div><div><br></div><div>- Resource does not span and has no jobs. It should be out of scope.</div><div><br></div><div>- Scan spans and has client-initiated jobs. If should be in scope.</div><div><br></div><div>- Transform does not span. It should be out of scope.</div><div><div class="h5"><div><br></div><div><br></div><div><br><div><div>On Sep 17, 2014, at 1:23 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>> wrote:</div><br></div><br></div></div></div></div></blockquote></div><br></div></div>
_______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/cloud<br></blockquote></div><br></div></body></html>