I have been thinking that it makes the most sense for us to agree on a document at this level of detail and provide a copy of it, plus more details on the wiki. Does that make sense to people? We also need to identify which spec each change appears in. Hal From: Erik Rissanen [mailto:erik@axiomatics.com] Sent: Tuesday, December 10, 2013 3:17 AM To: xacml@lists.oasis-open.org Subject: Re: [xacml] Proposed improvements to XACML 3.0 Appendix describing changes since XACML 2.0 All,
I read it and what it contains is correct, but there are lots of minor changes which are not listed. The should be the most important ones though. What is the expected level of detail?
Best regards, Erik
On 2013-12-09 14:06, Barbir, Abbie wrote: All Please review and then let me know the TC decision so we can pass it to the ITU before the next SG 17 meeting (Jan 15 2014) regards Note that changes in XACML 3.0 have previously been covered in different locations (OASIS webpage, wikipedia page for XACML...) We need to make sure we consistently update all locations. On Fri, Dec 6, 2013 at 9:02 AM, Hal Lockhart <hal.lockhart@oracle.com> wrote: As a part the review of XACML 3.0 by the ITU-T Korea has proposed an improved Appendix describing what has changed since XACML 2.0.
I just received this and have not reviewed it. I plan to add it to the agenda for next Thursday. Please review it before then. I will check into the details of what actions if any, we need to take at OASIS.
Hal
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
|