Home for the UWS Registry Extension?

[Brian Major]

Hi DAL, Registry and Grid,

Sorry for the wide distribution but this touches all three working groups.

An initial note for the UWS Registry Extension has been written and can be
viewed here:

    http://wiki.ivoa.net/internal/IVOA/IvoaGridAndWebServices/UWSRegExt.pdf

It is very simple: the essence of the note is to allow registry interface
entries to 'tag' interfaces as being UWS synchronous or asynchronous
endpoints.  This is to allow implementers of UWS services (TAP is the
working example) the freedom of having separate URLs for interfaces with
various security methods (supported authentication) and to have custom URLs
for sync and async endpoints.

Comments are welcome.  There is still uncertainty about how the information
in this note should be brought in as a document for reference by TAP 1.1,
so comments on that are welcome too.

Brian


On Thu, Feb 22, 2018 at 4:58 PM Brian Major <major.brian at gmail.com> wrote:

> Hi Grid, Registry,
>
> At the Santiago Interop we decided to identify the sync and async
> endpoints of a TAP 1.1 capability by setting the 'type' of the Interface
> element as one of either
>
>     uws:Sync or
>     uws:Async
>
> instead directly in the standardID of the capability like
>
>     ivo://ivoa.net/std/tap#sync-1.1 and
>     ivo://ivoa.net/std/tap#async-1.1
>
> We have implemented this in our TAP (1.1) services using the XSD here:
>
>
> https://github.com/opencadc/reg/blob/master/cadc-registry/src/main/resources/UWSRegExt-v0.1.xsd
>
> And it is all working as expected, no issues.
>
> Now I am wondering now where this XSD can be placed within the IVOA and
> how it can be documented to describe the intended use.  This will need to
> go somewhere official ahead of TAP 1.1.  Any suggestions are welcome.
>
> Thanks,
> Brian
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20180529/7e1ec87d/attachment.html>