[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] [Issue] How many resourceIds in request context?
Scoped request is only one kind of a request. Requiring to provide a special “dummy” value in the context to accommodate for that is a pretty ugly limitation in my opinion, especially as we do not define in any form what “hierarchical” really means – leaving the structure of resource outside of specification.
I think that for such requests what “resource” is should be inferred from the context (which may, or may not contain any specific attributes) and if any hierarchical relationship is declared in any form, they should be used.
I would think that a requirement for strict and unique identification of “resource” and unduly burdensome and shall not be needed. I will try to propose how it can be avoided.