[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] Comment on hierarchical Resource
That is exactly the problem with multiple resource-id attributes: it will break the notion of bag of same typed elements. Very, very bad idea in my opinion. Does not fit well with everything else. >As I wrote in my previous email, I would prefer to specify two resource-id >attribute with different data types in one request context in the case of >XML document. For example, if the user accesses of BoD element >(/md:record/md:patient/md:BoD) of XML document of >http://medico.com/medicalrec/Bert, the request context would have the >following two resource-id attributes: >resource-id of http://medico.com/medicalrec/Bert with datatype anyURI (optional) >resource-id of /md:record/md:patient/md:BoD with datatype xpath-expression
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]