Auxillary Resources Hypermedia Idea

I would like to air some pretty loose ideas around auxillary resources with you all.

It seems to me that auxillary resources come along a small number of dimensions. Dimensions as in orthogonal axes :-)

These dimensions might be things like "Access Control applies", "append-only", "server managed", "life cycle tied to resource", "you need Control to make changes to it", "only owner can read it".

I'd like to entertain the thought of auxiliary resources being defined in terms of hypermedia RDF, i.e. you don't need a spec to define them, all you need is an RDF document that describes the auxiliary resource type in terms of the above dimensions. On the vocab and protocol level, we'd need to specify what these dimensions mean, and how to implement each of them, but not the actual auxiliary resource type. They could be something like

<resource-types/audit-log> a solid:AuxiliaryResourceType ;
  rdfs:label "This is the auxiliary resource type definition for Audit Logs" ;
  aux:typeDefinition aux:append_only, aux:server_managed, aux:owner_readable .

The hardest to make to fit in this scenario seems to be Memento, but perhaps that isn't such a big deal anyway, since that's already specified elsewhere.

This idea needs a lot more work, but I'd like to share it now, since auxiliary resources are high on the agenda.

The issue names no files, tests, or entry points. Start by reviewing its proposed auxiliary-resource dimensions and Turtle example, then compare them with the existing auxiliary-resource work and the separately specified Memento behavior. Done would require a resolved design for the dimensions, vocabulary, and implementation rules.