Public Comments: XACML Next Generation (V4 and Beyond) #50
Description
📣 Call for Community Feedback on Evolving the XACML Specification 📣
The OASIS XACML Technical Committee is in the early stages of reworking core elements of the XACML specification. As reflected by the variety of open issues in this repository, the scope of these changes is substantial. We continue to believe that the core of the XACML model remains one of the most expressive and robust approaches to access control. However, we recognize opportunities to enhance its efficiency, flexibility, and alignment with modern development practices and use cases.
We are actively seeking community input to inform this work. In particular, we welcome your thoughts on:
- Missing functionality that you believe should be included
- Redundant or overly complex features that may warrant deprecation or simplification
- Areas where more (or less) structure or capability would be beneficial
- Developer experience improvements for integration, tooling, or implementation
Feel free to comment on specific issues or propose new ones. We value concrete, constructive feedback grounded in real-world applications and deployment scenarios.
🔒 Please Note: 🔒
This work is being conducted under the OASIS Feedback License, which ensures that the resulting specification, including all suggestions that any non-TC member may offer, will be freely available and unencumbered by intellectual property restrictions. By participating in this discussion, you agree that your contributions are made subject to that license.
We look forward to your insights and appreciate your help in shaping the future of access control policy standards.