TAPRegExt upload URIs

[Mark Taylor]

Hi DAL,

to anyone out there running TAP services which support upload:
the most recent draft of the TAPRegExt standard requires upload
methods to be declared using elements with IDs like this:

   <uploadMethod ivo-id="ivo://ivoa.net/std/TAPRegExt#upload-inline"/>
   <uploadMethod ivo-id="ivo://ivoa.net/std/TAPRegExt#upload-http"/>
   
(note the new "std/" in the URI).  The most recent versions of
TOPCAT (v3.8) and also taplint (STILTS v2.4), released today
look for these URIs.  That means that if your service uses one
of the older forms instead, newer TOPCAT versions will fail to 
recognise that it supports uploads.  TOPCAT looks for these
elements in the document emitted by the /capabilities endpoint;
the content of any registry record is not examined.
So, to enable TOPCAT users to perform uploads to your TAP service,
you are encouraged to update your capabilities declaration accordingly.

(TOPCAT version 3.8 looked for "ivo://ivoa.org/tap/uploadmethods#inline",
so if you want to maintain compatibility with older versions, you
could declare an upload method with that ID too.  Declaration of
such additional "custom" upload methods is permitted within TAPRegExt).

Mark

--
Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
m.b.taylor at bris.ac.uk +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/