Storage itself to behave as a Container

[gibsonf1]

I think the Storage representation should also act as a container (the root container for the storage) which would then contain one or more root containers. Ideally a GET etc on the Storage URI should behave like any container/data resource as well. Storing data at the top level Storage URI should be identical to storing in any container.

This also simplifies permissions by enabling permissions at the top Storage URI that could allow access to everything in that Storage, all root containers/data resources at top level, etc.

Originally posted by @gibsonf1 in #117

[elf-pavlik]

I recall that decision on this topic was captured in

• Clarify storage description URI #58

[acoburn]

Related to what @elf-pavlik wrote, the note in section 6.1.2 specifically indicates that the URIs for a Storage, Storage Description, and Storage root container can all be the same or all be different (or any combination), provided that the various representations of each conform with the requirements of the LWS spec.

https://www.w3.org/TR/lws10-core/#storage-description-binding

There are (at present) no specific constraints on the representation for the storage resource. I suspect a common pattern will follow what is currently seen in Solid, where the Storage resource is the same as the Storage root and thus acts as a Container.

Please also see the related discussion at
#117