Sarven Capadisli

Is this issue duplicated by https://github.com/solid/solid-spec/issues/217 ? Note that I've transferred 217 to https://github.com/solid/specification/issues/166 so that it can be addressed by the ongoing work in solid/specification. Note: https://github.com/solid/specification/issues/166#issuecomment-617654827

If I'm not mistaken, the MIT license is generally intended for Solid project's assets going forward. FWIW, solid/specification uses the MIT license. I'd suggest to stick to MIT for the...

https://github.com/solid/node-solid-server/issues/1040 proposes to simplify the interface for container read/write and meta handling.

I think with the exception of NonRDFSource case, the notion of "meta" as a distinct resource can disappear.

I'm not sure if the headers is a good place for this. For navigational purposes, perhaps one can get away with `Link` perhaps.. and that the relation is strictly about...

> If /foo/bar/ is a container, then a PUT to /foo/bar should fail > If /foo/bar is not a container, then a PUT to /foo/bar/baz should fail They are constraints...

>I definitely think that a PUT to a / url should result in container creation. Why?

>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/ The containment update goes against LDP's recommendation https://www.w3.org/TR/ldp/#ldpc-put-mbrprops : >LDP...

I have considered those interpretations however I don't think the interpretation is exclusive to the interaction being directly on the container ie. however `PUT` causes containment triples to be updated....

AFAICT, there is no (implied) statement which expects `PUT` to do anything besides creating or replacing a target resource. An idempotent method. It is an implementation detail as to what...