Re: [xacml-comment] Actions taken on XACML Comments,11/21/02 and 11/25/02

[Anne Anderson <Anne.Anderson@Sun.com>]

Two of the comments in the summary list I posted earlier today
indicated a STATUS: that was incorrect.  Here are the
corrections.  I apologize for any inconvenience.

Anne Anderson
-- 
Anne H. Anderson             Email: Anne.Anderson@Sun.COM
Sun Microsystems Laboratories
1 Network Drive,UBUR02-311     Tel: 781/442-0928
Burlington, MA 01803-0902 USA  Fax: 781/442-1692

============================================================================
0036. http://lists.oasis-open.org/archives/xacml-comment/200211/msg00064.html
Subject: Primitive type identifiers in B.4.
From: Satoshi Hada <SATOSHIH@jp.ibm.com>
Date: Thu, 21 Nov 2002 12:49:14 +0900

CATEGORY: Incomplete.
STATUS: Resolved 11/25/02.
RESPONSE: Define the two XQuery-related identifiers in XACML
Specification. 
ACTIONS: In Appendix B.4, Change "The following data type
identifiers are defined by XML Schema and XQuery" to "The following data type
identifiers are defined by XML Schema.

[follow this with the list of datatypes from #string to
#base64Binary].

The following data type identifiers correspond to the
dayTimeDuration and yearMonthDuration data types defined in the
XQuery specification [XQO Sections 8.2.2 and 8.2.1,
respectively].

http://www.w3.org/2002/08/xquery-function#dayTimeDuration
http://www.w3.org/2002/08/xquery-function#yearMonthDuration
============================================================================
0047. http://lists.oasis-open.org/archives/xacml-comment/200211/msg00085.html
Subject: policy and rule ordering
From: Paul Andrews <paandrew@cisco.com>
Date: Fri, 22 Nov 2002 10:09:29 -0500

CATEGORY: Incorrect.
STATUS: Resolved 11/25/02.
RESPONSE: This is as intended.  There is a trade-off between
consistency of obligations and efficiency of handling distributed
policies.  For example, you may have cached the 5th policy in the
PolicySet, so it is faster to evaluate than the 2nd policy.  An
application that wishes to specify the order of evaluation is
free to define a new combining algorithm using the XACML
extensibility mechanisms.
ACTIONS: No change.