<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 style="margin: 0px;">Dear all,</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">I take the opportunity of holidays for writing some ideas I shared with Paul during the last Interop. </div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">In the actual UWS recommendation (paragraph 2.2) only a rest binding is described. It is however said that other bindings, as SOAP, may appear in further versions. </div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">If I remember correctly, a SOAP binding was provided in the earlier version (draft?) of the UWS document. However with time SOAP has gone out of fashion.</div><div style="margin: 0px;">Since Rest is not a protocol or a format, but is an architecture design based on resources, it should suffer less from the effects of fashion.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">I think that an alternate binding should be based on an alternate architecture (again, not on protocols or format): the architecture oriented/based on functions. </div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">We may define the functions for handling the job lifecycle (e.g. creating a job, getting its description, etc.) by specifying what are the information that the user has to provide to these functions, while remaining agnostic about the mechanism that developers will use for implementing those functionalities. They could use SOAP, XML-RPC, Servlets, etc.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">The mapping between the REST and the function-based architecture should be easy. We just need to reproduce with functions the features summarized in the table contained into the paragraph 2.2.1 of the UWS recommendation. </div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">I don’t know it is worthwhile to carry out this work for the next UWS-1.1 version, but I think this could be something to take into account for the future UWS 2.0 version. </div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">What do you think of this proposal?</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Regards,</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Carlo Maria.</div><div><font color="#0042aa"><br></font></div></body></html>