Open duglin opened 2 months ago
allow location=resource for administrative extensions (xref impls) to add, but not end-users since that would require code changes
Given the recent changes, I think we can reduce this down to:
location=resource|version
where the default value is version
to be clear, id
and self
will be version
because they appear on both.
Going with location=resource|version|both
I think this might be related to @deissnerk's discomfort with our model...
isdefault
and Resource'sdefaultversionid
are examples.xxxRequired
fields totrue
since depending on whether the client asks for a Resource or a Version the required-ness aspect will change.I think we need to continue to have just Groups and Resources as part of the model definition itself. I think that 2-layer model is important to keep things simple and splitting Resources and Versions in the model will not only add to the perceived complexity but will require more work for people due to duplication of attribute definitions. However, I think we may need to be a bit more clear for client-side tooling.
Proposal:
location
, values =resource
,version
,both
(appears on both but might not be the same value). Default value isversion
so that user-defined extensions don't need to specify anything extralocation
value ofversion
exportrequired
Need to think about how this relates to other model attributes, like "serverRequired" or "readonly"
Then when we talk about "export" we can say:
location
value ofboth
orresource
will appear on the Resourcelocation
value ofboth
orversion
will appear on the VersionBasically, we skip
version
attributes when exporting a Resource (i.e. don't show default Version attributes).Are there other type of attributes I'm missing?