TAP-1.1 Authenticated Endpoints

[Molinaro, Marco]

Dear DAL, GWS, Registry,

following the issues arisen during last summer about
the way to expose authenticated endpoint in the
VOSI capabilities document for TAP-1.1, a splinter
session discussion took place among interested
parties at the recent College Park Interop.

(I set up a wiki topic to summarize the chronology
that brought there; you can find it at this link:
http://wiki.ivoa.net/twiki/bin/view/IVOA/TAP11AuthEndHistory
and I also linked it into the TAP-1.1 RFC page
http://wiki.ivoa.net/twiki/bin/view/IVOA/TAP11RFC
that contains itself discussion on the topic.)

The outcome of the discussion was a decision to
revert the way authenticated endpoints are annotated
to the previous solution that saw specific standardId(s)
for the sync and async endpoints, namely

ivo://ivoa.net/std/tap#sync-1.1
ivo://ivoa.net/std/tap#async-1.1

This decision means also that we no longer need UWSRegExt
(which means this Note will therefore be abandoned).

This agreement, while not being perfect, is considered
to be the only feasible solution within the current scenario,
along the lines of other recommendations like VOSpace
and SODA.

A future solution will take into account the concerns
arisen during the discussions (email and face-to-face
ones), but it requires more thoughts and possibly a
major revision in VOResource and, subsequently, the
protocols.

Cheers,
    Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/grid/attachments/20181114/94bc9659/attachment.html>