Sarven Capadisli

A follow-up question is if we need to have special containers.. where one would signal the location of a created resource (201), and the other not (202). This is orthogonal...

Depends if the use case requires to know whether the request is fulfilled or not.. or why not eg. the status monitor location gives an opportunity for the requester to...

I agree in the most strict sense. As I said, the server doesn't need to publicise the URI and gets to point to a monitor.

I'm open to all of this. 201 would enable: "hey, did you process my request x?"

Yes, that works - the location of the inbox doesn't matter. I think the target resource with the inbox is more interesting because eventually discovery will start from there. So...

The first issue is a communication between https://github.com/solid/node-solid-server/ and https://github.com/linkeddata/mashlib . I think it'd be appropriate to move this issue there. The Web browser requests the resource ( https://jakub.solid.opendata.cz//public/papers/05d6cf84-6478-4f8d-a964-c6731077c630 )...

* schema.org: I agree with your view of and reasons for schema.org. Among other things, schema.org overlaps with (or borrows from) DC Terms, and that goes a long way to...

dokieli's request for HTTP COPY: https://github.com/linkeddata/dokieli/blob/master/scripts/do.js#L2198 . See also: https://github.com/linkeddata/gold/issues/63

@elf-pavlik Did you mean to create this issue here or perhaps under solid-spec? the 'SHOULD' feels a bit spec-y. Alternatively, did you want this feature supported in node-solid-server (may dependent...

If containers is to folders, is resources to papers? Sorry, a strong -1 from me for "folders". I can't think of a decent replacement for Container... Would "Set" convey the...