<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Glad to read that "URL" still means . I interpreted "URI" across
the IVOA documents to mean "per
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc3986">https://tools.ietf.org/html/rfc3986</a>".<br>
</p>
<p>This is an area I have been hoping for some clarification -
though not related to this specific example:<br>
<br>
There is a case to be made for some kind of help in interpreting
XML when it is 'saved' and later used by something that<br>
is "not" a browser. How does one resolve the Base context of a
relative URL/I ?<br>
<br>
Section 5.1 of rfc3986 describes a few methods for estabishing a
"Base URI" via what i will describe as<br>
inheritance from the content and provenance of the URI. <br>
</p>
<div class="moz-cite-prefix">In cases where the provenance
(Retrieval URI) must be known, then the base can come from that.<br>
So for things like the present case, how to get to the result
when the process is done - the Base can<br>
be inferred. ok.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">But what of the URLs (say to Links or
other things) in the result XML? (VOTABLE).</div>
<div class="moz-cite-prefix">As far as I can tell IVOA tables (XML)
don't provide for <BASEURI href=""\> or other formulation.</div>
<div class="moz-cite-prefix">
</div>
<div class="moz-cite-prefix">So there's a bit of a gap there.</div>
<div class="moz-cite-prefix">Apparently some tools have gone to the
extent of rewriting relative URL with the base of the retrieved
file<br>
INTO the returned XML before writing it ... Yikes...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">IVOA should stay OUT of the business of
picking apart adopted standards, and
accepting/requiring/supporting<br>
only some part of them. <br>
</div>
<div class="moz-cite-prefix"><br>
URLs are not intended to be permanent, and they move, often, so
even an absolute URL in a VOTable won't help<br>
much. A URI from which a URL can be derived is more helpful,
at which point common prefixes can help reduce bloat of<br>
these files immensely. But, URI can only be helpful if there is
some way to resolve them into a URL: which is what I Thought<br>
the "Registry" was for many years ago. URLs can/could be
maintained through redirects to a new URL,<br>
but generally this fails because there's no funding, or people
simply move on to other things.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 11/1/19 2:48 PM, Brian Major wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKGJ5K-o=Zx-Yv0ZOnWOnCXLq_Lhz__8qnccLx4Z9LTa45Pc3g@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">Hi Christine,<br>
</div>
<div dir="ltr"><br>
</div>
<div>I don't see text in the spec that would indicate that
relative URLs are not allowed either, and they are
legitimate values for 'anyURI'.</div>
<div><br>
</div>
<div><a href="https://www.w3.org/TR/xmlschema11-2/#anyURI"
moz-do-not-send="true">https://www.w3.org/TR/xmlschema11-2/#anyURI</a><br>
</div>
<div><br>
</div>
<div>But since they're not mentioned in UWS I'd say the regular
rules determining the base of relative URLs should be applied
(<a href="https://www.w3.org/TR/WD-html40-970917/htmlweb.html"
moz-do-not-send="true">https://www.w3.org/TR/WD-html40-970917/htmlweb.html</a> section
5.1.2), in which case they would be relative to the
result-list endpoint. One would get the result that contains
the relative URL from:</div>
<div><br>
</div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">/{jobs}/{job-id}/results/{myresult}</span><br>
</div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">Which
would contain (for example) ./rel-url/to/result</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">And
resolve to</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">/{jobs}/{job-id}/results/rel-url/to/result</span><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">This
seems to agree with the sentence in section 2.2.2.3 of UWS "</span><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">A
sensible default for their URIs is to make them children of
/{jobs}/{job-id}/results, but this is not required.".</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">Cheers,</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px">Brian</span></div>
<div><span
style="color:rgb(0,0,0);font-family:sans-serif;font-size:13.3333px"><br>
</span></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Oct 31, 2019 at 1:09
PM Christine Banek <<a href="mailto:CBanek@lsst.org"
moz-do-not-send="true">CBanek@lsst.org</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"
style="font-size:12pt;color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi all,<br>
</p>
<p><br>
</p>
<p>I just got an interesting bug report on pyvo today and
after reading the UWS spec hoping for some clarity, I'm
at a loss if this is allowed. Here's the original
issue:<br>
</p>
<p><br>
</p>
<p><a href="https://github.com/astropy/pyvo/issues/191"
target="_blank" moz-do-not-send="true">https://github.com/astropy/pyvo/issues/191</a><br>
</p>
<p><br>
</p>
<p>Basically, the result URL field in a UWS async job is a
relative URL. Is this allowed / part of the spec? If
relative is allowed, is that URL considered relative to
the UWS Job URL? Since it seems to work with TOPCAT,
I've added Mark as well to get his feelings.<br>
</p>
<p><br>
</p>
<p>Thanks all,<br>
</p>
<p>Christine<br>
</p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Rick Ebert
Caltech/IPAC
Engineer, NASA/IPAC Extragalactic Database</pre>
</body>
</html>