Re: [sca-policy] TA 30008

[David Booz <booz@us.ibm.com>]

Assuming you meant @provides on policySet, then I agree. +1


Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

ashok malhotra ---04/06/2009 02:26:17 PM---The @requires attribute for policySets can contain a list of qualified and unqualified intents.

From:	ashok malhotra <ashok.malhotra@oracle.com>
To:	OASIS Policy <sca-policy@lists.oasis-open.org>
Date:	04/06/2009 02:26 PM
Subject:	[sca-policy] TA 30008

---

The @requires attribute for policySets can contain a list of qualified 
and unqualified intents.
For each unqualified intent the policySet can contain an intentMap that 
lists the policy for each qualifier for that
intent.  

The question in my mind was "Can there be intentMap corresponding to a 
qualified intent in the @requires of a policySet?"

Conformance statements 3008 and 30010 make it clear that intentMaps can 
only appear for unqualified intents in the
@requires of a policySet.  See below:

When a policySet element contains a set of intentMap children, the value 
of the @provides attribute of each intentMap MUST correspond to an 
unqualified intent that is listed within the @provides attribute value 
of the parent policySet element. [POL30008 <#POL30008>]

For each qualifiable intent listed as a member of the @provides 
attribute list of a policySet element, there MUST be no more than one 
corresponding intentMap element that declares the unqualified form of 
that intent in its @provides attribute. In other words, each intentMap 
within a given policySet uniquely provides for a specific intent. 
[POL30010 <#POL30010>]

Thus, the predicate of TA 30008 which says "The value of the @provides" 
attribute of each child <intentMap> corresponds to an unqualified intent 
listed in the @provides attribute of the parent policySet"
is correct and no change is required.

-- 
All the best, Ashok

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php