UWS result URL - is relative URL okay?

[Brian Major]

Hi Christine,

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'.

https://www.w3.org/TR/xmlschema11-2/#anyURI

But since they're not mentioned in UWS I'd say the regular rules
determining the base of relative URLs should be applied (
https://www.w3.org/TR/WD-html40-970917/htmlweb.html 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:

/{jobs}/{job-id}/results/{myresult}

Which would contain (for example) ./rel-url/to/result

And resolve to

/{jobs}/{job-id}/results/rel-url/to/result

This seems to agree with the sentence in section 2.2.2.3 of UWS "A sensible
default for their URIs is to make them children of
/{jobs}/{job-id}/results, but this is not required.".

Cheers,
Brian


On Thu, Oct 31, 2019 at 1:09 PM Christine Banek <CBanek at lsst.org> wrote:

> Hi all,
>
>
> 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:
>
>
> https://github.com/astropy/pyvo/issues/191
>
>
> 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.
>
>
> Thanks all,
>
> Christine
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/grid/attachments/20191101/bac6b362/attachment.html>