TAPRegExt PR: per-mode limits

[Markus Demleitner]

Dear DAL, dear Apps,

Remember two weeks ago?

On Mon, Sep 15, 2025 at 10:08:20AM +0200, Markus Demleitner via dal wrote:
> In pyVO bug #685 <https://github.com/astropy/pyvo/issues/685>, we
> figured it's finally time to be a bit less cavalier about the limits
> that TAP services report to their clients (e.g., how long can you
> take?  How large can your uploads be? etc).
>
> In TAPRegExt PR #8, <https://github.com/ivoa-std/TAPRegExt/pull/8>, I
> am proposing such a mechanism.  I'd be grateful for a review, both
> technically and content-wise.

Quite a bit of extra discussion has been happening in the meantime in
PR #8, and I am almost convinced that the original proposal with

  <executionDuration>...
  <limits mode="async">
    <executionDuration ...

was indeed not optimal.  Against that, there is now
<https://github.com/ivoa-std/TAPRegExt/pull/10>; this now defines a
mode attribute on several elements (including outputFormat, for which
a use case has been brought up).  Would you have a look at that, too?

If nobody champions the limit element from PR #8, I'll close that PR,
and I'd propose we go on with #10.

Thanks,

             Markus