[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: How to configure policySets
TARGET: SCA Policy Framework DESCRIPTION : The current SCA Policy Framework supports the specification of intents and policySets on SCDL elements using attributes. For example: <service> or <reference> <binding name = "xs:string" policySet="xs:QName"? requires="="listOfQNames"? /> </service> or </reference> There are a couple of problems with this approach. 1. Attributes are not extensible. If the intents and policySets were specified as child elements, this would permit extensibility. In the f2f meeting last week the argument was made that some extensibility was required to allow runtime extension of policies with information like the location of the key store or the type of certificate required. 2. If the 'requires' attribute is used in conjunction with a policySet attribute it's not clear what the semantics are. At one time the intents in the 'requires' list were used to configure the policySets but that meaning seems to have been lost. PROPOSAL: For the reasons cited above, I suggest that policySets and intents be associated with SCDL elements using child elements. For example: <service> or <reference> <binding name = "xs:string" <policySet name="xs:QName" select="xs:string"*> * <requires name ="xs:QName"/> * </service> or </reference> Each "policySet" element would name a single policySet. The "select" attribute could contain a list of xs:strings which would name qualified intents and customize the use of the policySet by selecting specific options from the intentMaps within the policySet. For symmetry, the "requires" element also names a single intent but this is not necessary. It could be changed to take a list of intent names as long as there was no need to customize the intents. -- All the best, Ashok
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]