OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-policy message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: NEW ISSUE: Should WS-Policy be subset for inclusion in policySets?


TARGET: SCA Policy Framework

TITLE : Should WS-Policy be subset for inclusion in policySets?

DESCRIPTION:

As you know, WS-Policies can be included directly in policySets either 
by reference or by inclusion. Consider, now, a WS-Policy that includes the

ExactlyOne operator. For example:

<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<!—Authorization assertion -->
<!-- rm_1_0 assertion ->
</wsp:All>
<wsp:All>
<!-- Authorization assertion -->
</wsp:All>
</wsp:ExactlyOne>

If this was wrapped in a policySet that had @provides = ‘authorization’ 
what would you get? Authorization, or authorization plus 
ReliableMessaging. The answer is unclear in the SCA Policy Framework 
specification. Thus, we recommend subsetting WS-Policy so that only 
simple policies without alternatives are included within policySets.

PROPOSAL:

WS-Policy based policies that are written to be directly included in 
policySets must have the following structure. The ExactlyOne operator in 
WS-Policy is disallowed The ‘ignorable’ and ‘optional’ attributes are 
also disallowed

<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<!-- assertion -->

<!-- assertion -->

…

<!-- assertion -->
</wsp:All>
</wsp:ExactlyOne>



-- 
All the best, Ashok


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]