TAPRegExt fine grained differences between tables

[Walter Landry]

Markus Demleitner <msdemlei at ari.uni-heidelberg.de> wrote:
> Hi Walter,
> 
> On Tue, Jun 09, 2015 at 04:53:51PM -0700, Walter Landry wrote:
>> We have a variety of tables with different backends all served
>> through a single TAP endpoint.  Because the backends are different,
>> they support different optional components of TAP.  Reading the
>> TAPRegExt standard, is it correct to say that there is no way to
>> express these kind of fine-grained differences between the tables?
> 
> This concerns what user-defined functions are available on them?
> Things like upload limits/formats?  These, yes, are declared globally
> per capability.  I'd recommend per table examples (for now, as per
> the TAP Implementation Note, if I may say so myself) to document
> where the system behaves in ways surprising to users.

Ok, though this feels vaguely unsatisfying.

> Your system sounds fairly funky.  I wonder if we could spare five
> minutes in the "Progress on TAP and  ADQL" session and you feel like
> describing what you're doing and why -- fringe cases often help
> identify where we get it wrong.

I would be happy to speak.  I think the funkyness arises from the
multiple backends we have.

Cheers,
Walter Landry