Accept-Post in draft-nottingham-link-hint about i-d HOT 7 CLOSED

@dret LDP needs to go and actually register that header field with IANA, not just put it in a document.

from i-d.

Hm. The use cases for this seem to be along the lines of "this resource accepts any format for PUT" or "this resource accept any image/* format for POST".

I'm not sure that this is the right place to indicate these semantics -- it feels like we're doing validation by media type. Much better would be to bake the semantics into the link relation type of that resource.

OTOH HTML does it in form uploads with accept.

I could see it working for AcceptPut; I have a harder time with it for AcceptPost and especially for AcceptPatch. Just not sure the added complexity is worth it.

from i-d.

FYI: the draft referenced above is no longer active. the W3C LDP group ended up registering Accept-Post directly in the LDP spec: https://www.w3.org/TR/ldp/#header-accept-post

from i-d.

as discussed in #192, maybe it's worth considering splitting home documents and the general concept of link descriptions/hints?

from i-d.

as discussed in #192, maybe it's worth considering splitting home documents and the general concept of link descriptions/hints?

I'd love a separate JSON-based HTTP hints spec. People keep wanting it in JSON Hyper-Schema, although my preference is also to look more towards link relations for this. But if we must have hints a shared JSON format for them would be useful.

from i-d.

from i-d.

from i-d.