OASIS Members:
The OASIS eXtensible Access Control Markup Language (XACML) TC members [1] have approved submitting the following Candidate OASIS Standards to the OASIS Membership in a call for consent for OASIS Standards:
XACML REST Profile Version 1.1
Candidate OASIS Standard 01
28 March 2019
JSON Profile of XACML 3.0 Version 1.1
Candidate OASIS Standard 01
28 March 2019
XACML is an OASIS Standard which describes both a policy language and an access control decision request/response language (both defined in XML). XACML v3.0 is an international standard (ITU-T X.1144), approved by the International Telecommunications Union - Telecommunication Standardization Sector (ITU-T).
The REST Profile specification defines a profile for the use of XACML in a RESTful architecture.
The JSON Profile proposes a standardized interface between a policy enforcement point and a policy decision point using JSON, leveraging the decision request and response structure specified in the core XACML standard.
XACML REST Profile Version 1.1 received 3 Statements of Use from ViewDS Identity Solutions, Axiomatics AB, and Siemens AG [2].
JSON Profile of XACML 3.0 Version 1.1 received 3 Statements of Use from ViewDS Identity Solutions, Axiomatics AB, and Siemens AG [3].
This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [4]. All requirements of the OASIS TC Process having been met [5] [6], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.
This Call for Consent is taking place under the revised TC Process rules effective 01 July 2017 [2]. This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection [3]. To register an objection, you must:
1. Indicate your objection on this ballot, and
2. Provide a reason for your objection and/or a proposed remedy to the TC.
You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC's mailing list. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.