Should NSS allow documentResource.meta and .meta.acl

[bourgeoa]

@csarven
I recently noticed that

• CSS allows .meta on document Resource, but not ACL on the documentResource.meta.
  With a somehow server specific implementation non existent .meta are displayable CommunitySolidServer/Recipes#34
• NSS do not allow any documentResource.meta

What is the current specification status ?

[csarven]

The Solid Protocol specifies how to discover the Description Resource: https://solidproject.org/ED/protocol#auxiliary-resources-description-resource . In essence, the server allocates the URI to the description resource, and manages its lifecycle in part, e.g., https://solidproject.org/ED/protocol#server-delete-remove-auxiliary-resource

At this time, there are no further constraints, e.g., providing a successful response to reading a description resource (200), or not if nothing was yet described (404). Servers are free to generate or update the description resource (at any time) if they so wish. As for access controls on auxiliary resources, and, again at this time, they can be specific to the type of auxiliary resource, e.g., description resource's authorization is same as that of subject resource (the resource that links to description resource). Aside: there is some interest / considerations involving separating authorization rules between the subject resource and the auxiliary resource, but we'll cross that bridge later.