Who may Contribute? Contributors to this repository are expected to be Members of the OASIS eXtensible Access Control Markup Language (XACML) TC, for any substantive contributions. Anyone wishing to participate in the TC's technical activity is invited to join as a TC Member. Member in this context means any TC role other than OASIS TC Observer, per TC Process.
Seeking Comments on XACML Evolution The TC currently is soliciting comments from the community on evolution and potential reworking of core elements of the XACML specification. As reflected by the variety of open issues in this repository, the scope of possible changes is substantial. The TC continues 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. The TC is 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
Non-TC members are invited to comment on specific issues or propose new ones here, subject to the OASIS Feedback License, as provided in the LICENSE file. We value concrete, constructive feedback grounded in real-world applications and deployment scenarios.
Persons who are not TC members also are invited to open issues and provide comments on other matters, using this repository's GitHub Issues tracking facility or using the TC's archived comment list. All such content created in GitHub Issues and/or posted by non TC-members here or there is governed by the terms of the OASIS Feedback License.
Use of Contributions. As with all OASIS Technical Committee assets, content placed into this GitHub repository is visible and publicly accessible. Subject to applicable licensing rules, the repository content may be re-used freely, including the creation and publication of derivative works.
Certain other issues of this repository may also have been designated to receive public comments on some of the TC's work, are subject only to our OASIS Feedback License, and contain a distinct LICENSE.md file imposing that license. Please check the LICENSE.md file for the relevant Issue, if a separate one is posted there, before using or contributing to that Issue.
Cloning and forking. May users clone and fork this repository? Yes. This GitHub repository may be forked or cloned for use by any party.
Please see the README for general description of this repository, and the LICENSE file for licensing.