Kjetil Kjernsmo

> No. /pods/users/foo/ and /bar/baz are under different storages. What is that requires `/bar/baz` to be in a storage? Does that mean that I am not allowed to have a...

> > What is that requires /bar/baz to be in a storage? > > How was `/bar/baz` created? How was `/bar/` created? How was `/` created - that's given; root...

Yes, and therefore, if `/pods/users/foo/` and `/pods/users/bar/` are storages, then `/pods/users/` and `/pods/` can't be storages, and so, the discovery method breaks down.

Yes, but which? If you do not know anything about the structure of the pod, how do you get started?

No, I don't think that would help. Say that Solid lives in a Web ecosystem, where servers manage pods along with legacy systems, using the same origin. You may then...

So, testing out the algorithm: ```http GET /pods/users/ 200 OK Content-Type: text/html These are our users foobar GET /pods/ 200 OK Content-Type: text/html Yeah, we really love Solid! GET /...

> > The content admin may not have made that data available on the resource that you already have, not very accommodating that is, but you want to know. >...

> > Can't I just have a list of storages? > > I do not understand the use case motivating the feature that lists all storage locations on a Solid...

I have started to think about this differently: It is also about the authority of the URI space of the storage. There may/will be other APIs on a Solid server,...

I think that with the resolution of https://github.com/solid/conformance-test-harness/pull/119 it now makes sense to remove this from the milestone and return to it for 1.0. While I still think the current...