Looking at AssignmentScope and SpecificResource case the use of ResourceId makes me wonder how version in ResourceId could be omitted.
It makes sense to require version when we're concerned with RP API and/or resource representation, but from Identity, RBAC scope and pretty much any resource reference perspective the version is irrelevant.
Maybe there needs to be a way to construct ResourceId w/o version or an arbitrary AssignmentScope case?
I see there's also ResourceRef type as well, maybe that needs to be extended to allow opaque relative Uri and AssignmentScope case of ResourceRef offered?
Looking at
AssignmentScope
andSpecificResource
case the use ofResourceId
makes me wonder howversion
in ResourceId could be omitted.It makes sense to require version when we're concerned with RP API and/or resource representation, but from Identity, RBAC scope and pretty much any resource reference perspective the version is irrelevant.
Maybe there needs to be a way to construct ResourceId w/o version or an arbitrary AssignmentScope case?
I see there's also
ResourceRef
type as well, maybe that needs to be extended to allow opaque relative Uri andAssignmentScope
case ofResourceRef
offered?