<div dir="ltr">Hi DAL, Registry and Grid,<div><br></div><div>Sorry for the wide distribution but this touches all three working groups.</div><div><br></div><div>An initial note for the UWS Registry Extension has been written and can be viewed here:<br><br> <a href="http://wiki.ivoa.net/internal/IVOA/IvoaGridAndWebServices/UWSRegExt.pdf">http://wiki.ivoa.net/internal/IVOA/IvoaGridAndWebServices/UWSRegExt.pdf</a></div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Brian</div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Feb 22, 2018 at 4:58 PM Brian Major <<a href="mailto:major.brian@gmail.com">major.brian@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Grid, Registry,<div><br></div><div>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<br><br> uws:Sync or</div><div> uws:Async</div><div><br></div><div>instead directly in the standardID of the capability like</div><div><br></div><div> ivo://<a href="http://ivoa.net/std/tap#sync-1.1" target="_blank">ivoa.net/std/tap#sync-1.1</a> and</div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"> ivo://<a href="http://ivoa.net/std/tap#async-1.1" target="_blank">ivoa.net/std/tap#async-1.1</a></span><br></div><div><br></div><div>We have implemented this in our TAP (1.1) services using the XSD here:<br><br> <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><a href="https://github.com/opencadc/reg/blob/master/cadc-registry/src/main/resources/UWSRegExt-v0.1.xsd" target="_blank">https://github.com/opencadc/reg/blob/master/cadc-registry/src/main/resources/UWSRegExt-v0.1.xsd</a><br><br>And it is all working as expected, no issues.<br><br>Now I</span> 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.</div><div><br></div><div>Thanks,</div><div>Brian<br><div><br></div><div><br></div><div><br></div></div></div>
</blockquote></div></div></div>