Proposal for Issue POLICY-94: Allow intents to be attached usingan element

[ashok malhotra <ashok.malhotra@oracle.com>]

At the Boston (Charlestown) f2f we decided to allow policySets to be 
attached to a SCDL element
using a child element in addition to being attached as the value of an 
attribute.

Specifically, policySets can be attached to a SCDL element as the value 
of the @policySets attribute or as a
child element, i.e. either as

<service> or <reference>…
<binding.binding-type policySets="listOfQNames">
</binding.binding-type>
…
</service> or </reference>

or as

<service> or <reference>…
<binding.binding-type>
<policySetAttachment name="sns:EnterprisePolicySet"> ...
</binding.binding-type>
…
</service> or </reference>

This issue requests that we make a similar extension for intents. That 
is, intents can be attached either as
the value of an attribute

<service> or <reference>…
<binding.binding-type requires="listOfQNames"
</binding.binding-type>
…
</service> or </reference>

or using a child element:

<service> or <reference>…
<binding.binding-type>
<intentAttachment name="sns:mySpecialIntent"> ...
</binding.binding-type>
…
</service> or </reference>

The advantage of allowing intents to be attached using a child element 
is that the intentAttachment element can
carry additional information in its attributes. This can be used to turn 
the intents on and off -- useful during testing -- and
also to provide information such as the repository from which the 
policySets should be selected to satisfy the intent.

Section 4.4.3 of the Policy Framework spec defines XPath functions that 
can be used to attach policySets to SCDL
elements based on features present in the SCDL. Section 4.4.3.2 defines 
Intent-based functions that can be used to
attach policySets to SCDL elements based on the presence of specific 
intents. These functions could be extended and
sharpened to take advantage of attributes on the intentAttachment element.

-- 
All the best, Ashok