Enhancement Requests to UWS 1.0This page is intended to summarize various suggestions that are made to enhance UWS to determine if they should be included in the next major version of the UWS standard. The discussion of individual topics will take place primarily on the grid wg mailing list. The current working draft of the next version UWS 1.1? is on volute See also the UWS section on TAPImplementationNotes -- can we merge the material? Only keep UWS2.0 material in here?Alternative bindings to RESTSOAP BindingA SOAP binding was removed from the original draft of the version 1.0 standard - This could be reintroduced for the next version - A possible WSDL file for this binding is contained within the volute googlecode projectOther bindingThere have been requests for other bindings that include the operations on the UWS objects directly as part of the XML message.Registering UWS implementations"Pure" UWS implementations - i.e. a UWS that is not part of another IVOA standard - have been created, and people would like to register these directly - This needs a specific VOResource extension. A start to this is being made with UWSRegExtMore Job Controls/Metadata
Parameters
| ||||||||
Added: | ||||||||
> > | Results
| |||||||
Authentication and Authorization
Call-back mechanismRather than having to poll job status it would be nice if there were a mechanism whereby a client could be notified when the job changes status (possibly easier to do in a non-REST binding).MiscellaneousThese are issues that are largely simple clarifications or enhancements of the current spec.
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<--
|