<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div>unsubscribe</div><br><div style=""><div>On 3 Mar 2018, at 10:00 pm, <a href="mailto:registry-request@ivoa.net">registry-request@ivoa.net</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Send registry mailing list submissions to<br><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:registry@ivoa.net">registry@ivoa.net</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><span class="Apple-tab-span" style="white-space:pre"> </span>http://mail.ivoa.net/mailman/listinfo/registry<br>or, via email, send a message with subject or body 'help' to<br><span class="Apple-tab-span" style="white-space:pre"> </span>registry-request@ivoa.net<br><br>You can reach the person managing the list at<br><span class="Apple-tab-span" style="white-space:pre"> </span>registry-owner@ivoa.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of registry digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Home for the UWS Registry Extension? (Brian Major)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 2 Mar 2018 11:18:20 -0800<br>From: Brian Major <major.brian@gmail.com><br>To: Grid and Web Services WG <grid@ivoa.net>, registry@ivoa.net<br>Subject: Re: Home for the UWS Registry Extension?<br>Message-ID:<br><span class="Apple-tab-span" style="white-space:pre"> </span><CAKGJ5K-OTUhkMDs_-0sMCgPTu-nj4s+4brs-37mk6YguQ4GawA@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Markus,<br><br>On Mon, Feb 26, 2018 at 1:20 AM, Markus Demleitner <<br>msdemlei@ari.uni-heidelberg.de> wrote:<br><br><blockquote type="cite">Hi Brian,<br><br>On Thu, Feb 22, 2018 at 04:58:16PM -0800, Brian Major wrote:<br><blockquote type="cite">Hi Grid, Registry,<br><br>At the Santiago Interop we decided to identify the sync and async<br></blockquote>endpoints<br><blockquote type="cite">of a TAP 1.1 capability by setting the 'type' of the Interface element as<br>one of either<br><br> uws:Sync or<br> uws:Async<br><br>instead directly in the standardID of the capability like<br><br> ivo://ivoa.net/std/tap#sync-1.1 and<br> ivo://ivoa.net/std/tap#async-1.1<br><br>We have implemented this in our TAP (1.1) services using the XSD here:<br><br><br>https://github.com/opencadc/reg/blob/master/cadc-registry/<br></blockquote>src/main/resources/UWSRegExt-v0.1.xsd<br><blockquote type="cite"><br>And it is all working as expected, no issues.<br><br>Now I am wondering now where this XSD can be placed within the IVOA and<br></blockquote>how<br><blockquote type="cite">it can be documented to describe the intended use. This will need to go<br>somewhere official ahead of TAP 1.1. Any suggestions are welcome.<br></blockquote><br>While it is of course possible to just go ahead and specify this in<br>UWS 1.2, thus creating a new "official" IVOA schema, in the interest<br>of keeping the total number of schema files people need to deal with<br>(and also because at least sync arguably isn't really related to<br>UWS), I'd actually prefer to have these types in VODataService 1.2,<br>where there's already stuff like ParamHTTP, which in some sense is a<br>sibling of your uws:Sync.<br><br></blockquote><br>Well, I think it is certainly UWS related, but I agree that a UWS 1.2 is<br>too much.<br><br><br><blockquote type="cite"><br>Work on VODataService 1.2 has started with<br>http://ivoa.net/documents/Notes/Regstc, which already has a draft<br>schema with some updates.<br><br></blockquote><br>I'd say that adding it to VODataService is also too heavyweight for a<br>number of reasons. The extension may change to have content (rather than<br>just acting as a 'tag') in the near future. Having it described in this<br>upstream spec would make it that much harder to change. I'm in favour of<br>keeping it close it's source. That is, in GWS and associated with UWS.<br>So, how about a short UWS Registry Extension note so we can get it approved<br>relatively quickly ahead of TAP 1.1? I'd be willing to write that up.<br><br>Also, what about the version of the extension? We currently have it at 0.1.<br><br><br><blockquote type="cite"><br>So, here's what I can offer if people agree these two types should be<br>added as part of VODataService 1.2 (rather than a separate standard<br>or UWS 1.2): Create a repo for VODataService 1.2 in volute and put<br>the new features from Reg-STC and your UWS work into the schema.<br><br>That could happen within two weeks, say. After that, we could work<br>out some way to have the schema file as a beta in the schema repo and<br>(I've been lobbying for that already) possibly even in the RofR<br>validator.<br><br>Sure, it'll be more than a year until the thing reaches<br>recommendation status -- but frankly, I guess any other way to make<br>these things official won't be much quicker...<br><br> -- Markus<br><br></blockquote><br>Cheers,<br>Brian<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://mail.ivoa.net/pipermail/registry/attachments/20180302/fe1f480b/attachment-0001.html><br><br>------------------------------<br><br>_______________________________________________<br>registry mailing list<br>registry@ivoa.net<br>http://mail.ivoa.net/mailman/listinfo/registry<br><br>End of registry Digest, Vol 81, Issue 2<br>***************************************<br></blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>----</div><div>Jon Smillie<br>Virtual Laboratories<br>National Computational Infrastructure<br><a href="http://nci.org.au">nci.org.au</a></div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></body></html>