Re: More info in the result of a POST?

Hi Henry,

My understanding in general (not from the LDP spec) is that you should
return all the headers that you would on a successful GET on a successful
POST, and with a 201 status.

I don't think there's a way to specify all of the possible media types in
which you can get a representation of the resource.  That would be a huge
list with JSON-LD profiles and frames.

HTH

Rob

On Sun, May 3, 2015 at 3:30 AM, henry.story@bblfish.net <
henry.story@bblfish.net> wrote:

>
> > On 3 May 2015, at 12:04, henry.story@bblfish.net wrote:
> >
> > Hi,
> >
> >  the result of a POST is currently according to the spec § 5.2.3.1
> >
> >>      LDP clients should create member resources by submitting a
> representation as the entity body of the HTTP POST to a known LDPC. If the
> resource was created successfully, LDP servers must respond with status
> code 201 (Created) and the Location header set to the new resource’s URL.
> Clients shall not expect any representation in the response entity body on
> a 201 (Created) response.
> >
> > I was wondering if it would make sense for the client to also send back
> > all the headers as well, such as
> >
> > Access-Control-Allow-Origin: *
> > Allow: OPTIONS, GET, HEAD, POST, SEARCH, PATCH, PIT
> > Accept-Patch: application/sparql-update
> > ETag: "1417390950000|Success(922)"
> > Last-Modified: Sun, 1 April 2015 23:42:30 GMT
> > This would allow the client to immediately know what further operations
> it could do on the newly created resource.
>
> It would be good if one could also in the result specify which mime types
> were allowed on a GET on the created resource.
>
> Henryt
>
> >
> >
> >
> > Henry
> >
> > Social Web Architect
> > http://bblfish.net/
> >
>
> Social Web Architect
> http://bblfish.net/
>
>
>


-- 
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305