Re: [apps-discuss] Accept-Post HTTP header field

[Julian Reschke <[e-mail]>]

On 2014-05-07 02:14, Erik Wilde wrote:
> hello.
>
> http://www.w3.org/TR/ldp/#header-accept-post (the "Linked Data
> Platform") is a current W3C document in last call WD status, and it
> introduces/uses the Accept-Post header field proposed in a current draft:
>
> http://tools.ietf.org/html/draft-wilde-accept-post
>
> we have publicized this proposed header field on this list, and the
> latest draft also includes a list of known implementations of this
> header field:
>
> http://tools.ietf.org/html/draft-wilde-accept-post-02#section-6
>
> after making the specification available for a while, and listing known
> implementations, we are wondering about next steps. what it would take
> to get this draft moving towards an experimental RFC (apart from some
> references that will need to be updated).
>
> thanks a lot and kind regards,
>
> dret.

Editorial question:

    The app:accept element is similar to the HTTP Accept request header
    field [RFC2616].  Media type parameters are allowed within Accept-
    Post, but Accept-Post has no notion of preference - "accept-params"
    or "q" arguments, as specified in Section 14.1 of [RFC2616], are not
    significant.

What is "app:accept"?

Furthermore: the fact that we'd have both Accept-Patch and Accept-Post 
kind of implies that maybe something more generic is needed.

Wouldn't it make more sense to allow "Accept" as a response header field?

Best regards, Julian