-
We're intending to make it possible to implement the next version of XACML exclusively using JSON (so without touching XML at all). However, anyone seeing "XACML 4.0" is likely to assume that it is st…
-
Study the feasibility of removing all XPath-related features from the core spec and move them to a new profile, e.g. _XPath Profile_.
Rationale:
1. Simplify the core spec, esp. for implementers …
-
#22 and #23 showed the need to add new XACML functions in order to simplify very common Apply expressions that _compose_ (math sense) two or more existing functions together.
For example, in #23 …
-
### Description of the bug
Code blocks are being removed in the current implementation of Mack, specifically code blocks nested in lists.
Here is an example of the current output:
![image](http…
-
I regularly need to test whether a bag of values (usually from an attribute designator) is empty or non-empty. With the current XACML functions that means comparing the bag size to zero.
```
…
-
The proposal is to add XACML functions to compute the minimum, maximum, sum or average of a bag of values. These functions could be added to both XACML 3.0 and XACML 4.0.
The sum and average functi…
-
I don't see a strong reason for the separation between Policy and PolicySet. A single structure that combines the features of both would simplify the XML Schema, the specification and implementations.…
-
This would allow to use XACML variables as inputs to any XPath function / expression, which would provider simpler alternatives to certain complex ApplyExpressions.
For example, say we declare a va…
-
In writing fine-grained access control policies for non-trivial systems I find that common expressions keep recurring across the collection of policies. These expressions are obvious candidates for va…
-
References to policies and policy sets (from within policies and policy sets) are instances of the following type:
```
…