Wouter Termont

Thanks for the confirmation, @joachimvh! Re supporting more complex cases: (assuming that we do not want to support automated creation of storages on random paths) storage structure will always follow...

Coming back to this because of my [comment](https://github.com/solid/specification/issues/14#issuecomment-1712773516) on https://github.com/solid/specification/issues/14, which brings into focus again the preference for 403 as proposed by @humont, and 'solves' cases 1-7 of this issue.

Re cases 8-10 in particular, and this issue in general, I would like to add, however, that **I don't think there is really any problem**. Moreover, 'solving' it by changing...

@csarven, I propose to take this issue (and the related https://github.com/solid/specification/issues/347) up in the milestone for v0.11. As long as we specify Solid's handling of identifiers, there should be no...

I've been combing through some related issues, and feel that this one has a strong consensus that as a general rule **the Protocol can sparingly recommend specific status codes, or...

Can be closed in light of https://github.com/solid/process/issues/327 ?

@csarven, I might have been too eager here; my apologies. The intention of the PR, and the questions you raised in it, are indeed still valid. Only the concrete changes...

@csarven, I propose to take this issue (and the related https://github.com/solid/specification/issues/22) up in the milestone for v0.11. As long as we specify Solid's handling of identifiers, there should be no...

Quite a strong objection to the idea of separating hierarchical and non-hierarchical organizations as different storage types. - It would mean I cannot store resources organized in different ways on...

Since @csarven asked to post it here, I'll repeat our confirmation from https://github.com/solid/authorization-panel/issues/309#issuecomment-1285321304: we would definitely like to [continue to] contribute our findings about use cases we encounter(ed) in the...