SCS2: Current state, POST support

[Markus Demleitner]

Dear DAL community,

In my loose series of community polling on Stelios' comments on
SCS2[1], I think the current status is:

* VERB stays in pretty much as it is
* We're doing to do text-based error messages and hoping for DALI to
  define these.

If you disagree stronly enough to bother, please speak up now.

Stelios' next topic was:

> 5. POST support is not clearly required or optional
>
> The spec describes GET semantics in detail but there isn't any
> mention of POST.  Does this inherit the support from DALI 1.2 (SHOULD
> support POST)?  If so would it be better just to explicitly state
> whether POST (with application/x-www-form-urlencoded body) is MUST,
> SHOULD, or MAY to avoid readers having to cross-reference to another
> doc for this?

I'm rather sure SCS needs to special treatment here; it should do
what S-protocols in the VO have traditionally done, which is treat
GET and POST identically.  DALI 1.2 is now explicit on requiring
support for both urlencoded and multipart request bodies.

I would argue the question is conclusively settled in DALI 1.2's sect
2.2, where it says on sync endpoints:

  Synchronous requests can be made using either the HTTP GET or POST
  method.

I think the subtext is "and both should yield the same results for
the same parameters, at least in the successful case and disregarding
the possibility of intervening caches".

Am I missing something?

Thanks,

         Markus

[1] Still at
https://github.com/msdemlei/scs2-original-deleteme/issues/2 because
I'm unable to move it to the new repo.