RE: [xacml] XACML Core Spec

[Polar Humenn <polar@syr.edu>]

On Wed, 7 Apr 2004, Tim Moses wrote:

> Polar - In Section 7.9 (Condition evaluation) you have the text ...
>
> 1. "The condition value SHALL be "True" if the <Condition> element is
> absent, or if it evaluates to "True.  Its value is "False" if the
> <Condition> element evaluates to "False"."
>
> In Table 1, (Rule truth table), we list a value for Condition of
> "Indeterminate".
>
> Why doesn't your text explain how a Condition value of "Indeterminate" might
> arise?

Good point. We should probably say something about that.

 The condition value SHALL be "Indeterminate", if the expression contained
 in the <Condtion> element evaluates to "Indeterminate."

Is that good enough?

> 2. The plan is to substitute a proper schema location reference once the
> final v2.0 schema has a permanent location on the OASIS site.
>
> 3. Excluding the <xs:string> tags around the <AttributeValue> contents is
> invalid.  I'm not sure why.  Seth is looking into it.

Really? That seems odd. I haven't run into that problem. (I think).

Cheers,
-Polar




> All the best.  Tim.
>
> -----Original Message-----
> From: Polar Humenn [mailto:polar@syr.edu]
> Sent: Tuesday, April 06, 2004 12:31 PM
> To: XACML
> Subject: [xacml] XACML Core Spec
>
>
>
> Hi,
>
> Sorry I didn't get to it by yesterday's deadline, my dad ended up in
> emergency surgery over the weekend. (He's okay, but it will bring up a point
> with obligations later).
>
> Attached are the editorial changes to the spec.
>
> Also, since it was prudent to have the CombinerParameter proposal finished
> by yesterday's dead line, I took the liberty to include it in this document,
> of what Michiharu and I seemed to agree about. They include:
>
>     <CombinerParameters>
>     <RuleCombinerParameters>
>     <PolicyCombinerParameters>
>     <PolciySetCombinerParametrs>
>
> and the changes and definitions throughout the spec.
>
> I left change tracking on, so if MS Word has any way to search for these.
> They appear in blue.
>
> Man, I cannot stand MS Word! It is the most difficult program to work with
> than I have ever. At one point I was chasing the screen around. It kept
> kicking like a Mexican jumping bean. What's up with that? And I really wish
> it would stop assuming what I'm trying to do.
>
> Back to my OMG specs and Framemaker. Whew!
>
> Cheers,
> -Polar
>
>