[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] XACML Core Spec
Polar - Yes. Currently, PolicyIdRef and RuleIdRef are strings and PolicyId and RuleId are URIs. I think you are suggesting changing PolicyIdRef to a URI and RuleId to a string. I won't make any changes for the time being, as nothing is actually broken. But, let's resolve this at the face-to-face. All the best. Tim. -----Original Message----- From: Polar Humenn [mailto:polar@syr.edu] Sent: Friday, April 23, 2004 11:59 AM To: Tim Moses Cc: 'XACML' Subject: RE: [xacml] XACML Core Spec On Fri, 23 Apr 2004, Tim Moses wrote: > Polar - We have RuleIdRef defined as a string and RuleId defined as a > URI. Is this intentional? All the best. Tim. You mean in the RuleCombinerParameter? This must be historical. RuleId's were URI's right? I think this approach just comes from the PolicyId or PolicySetIds being URIs. But they are URIS because they can be externally referenced in a PolicySet (god only knows how). We don't have RuleReferences, (and we shouldn't), so a rule really didn't even need a RuleId other than having a descriptive name. Now a RuleCombinerParameter can reference it from only within the Policy, much like how VariableDefintions are referenced.. Therefore, the RuleID really shouldn't be more than a string. I would like to see the RuleId be a string, so that less complicated string-equality can be used to deal with these RuleCombinerParameters. We wouldn't be loosing anything, since there was nothing you would do with a RuleId as a URI in the first place. Cheers, -Polar > -----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 > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]