Michiel de Jong

@dmitrizagidulin sure, go ahead! It will definitely be a useful checklist for things that the 1.0 spec should clarify unambiguously. Personally, I use https://github.com/inrupt/pod-server/issues/15 as the authoritative up to date...

+1 to converting the format +1 to fixing points where the text diverts from current practice +1 to fixing ambiguities -1 to "pull in curated parts" if by that you...

Related: seems that NSS never implemented it, so if that's true then there should be zero apps using it: https://github.com/solid/node-solid-server/issues/962 Our wac-ldp module currently implements is [using comunica](https://github.com/inrupt/wac-ldp/blob/master/src/lib/rdf/applyQuery.ts#L3).

I must admit I've never really understood .meta files, and I didn't (yet) implement then in IPS. I think they are used to support setting titles on containers. Maybe we...

a container with a .acl document in there is not an empty container. I mainly proposed this to track it as an option, I think the current behaviour is fine...

I don't see the point of removing this. > it is unclear what subset should be supported So to fix that, let's document it better! :) I'm not very familiar...

Looks like two members of the [query panel](https://github.com/solid/culture/blob/master/panels.md#query-panel) already agree on this so could be a quick decision :) cc @kjetilk @justinwb.

Also: After a PUT to `https://example.com/some/path/to/a/resource`, the newly created resource will be at that URL, and will be ldp-contained by `https://example.com/some/path/to/a/`, in general, remove the longest `/`-less suffix. Note that...

yeah, PUT and POST are definitely both supported, and `POST /foo/` with a `slug` header of 'bar' should have the same effect as `PUT /foo/bar`. Server implementers should be careful...

Great points @acoburn, indeed those things are all defined at the Solid level and not at the LDP level: > What container (if any) will now include the ldp:contains triples...