xacml — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [xacml] Summary of issues: WI#10. Parameters for Combining Algorithms
MHonArc v2.5.0b2 -->xacml message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xacml] Summary of issues: WI#10. Parameters for Combining Algorithms
- From: Michiharu Kudoh <[email protected]>
- To: seth proctor <[email protected]>
- Date: Mon, 5 Apr 2004 11:06:37 +0900
Hi, Seth
I have no problem with the schema you are suggesting.
The issue we are discussing seems to be formality v.s. practicality.
Best,
Michiharu
seth proctor
<Seth.Proctor@Sun
.COM> To
Sent by: Michiharu Kudoh/Japan/IBM@IBMJP
Seth.Proctor@Sun. cc
COM XACML TC
<[email protected]>
Subject
2004/04/04 14:54 Re: [xacml] Summary of issues:
WI#10. Parameters for Combining
Algorithms
Michiharu Kudoh wrote:
> [...]
> <Policy PolicyId="P1" algid="priority-rule-combo-algo">
> <CombinerParameters>
> <CombinerParameter ParameterName="creater">
> <AttributeValue DataType="string">Alice</AttributeValue>
> </CombinerParameter>
> </CombinerParameters>
If we're only using attribute values now, and not expressions (which I
think may be the direcion we're heading), I'd suggest that we cut down
on tags by saying:
<CombinerParameter ParamterName="creater"
DataType="...string">Alice</CombinerParameter>
In other words, make CombinerParameter an AttributeValue. This is how
AttributeAssignments look, and I think it makes sense here too. Just a
thought...
seth
To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.php
.
- References:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]