[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: Re: [sca-policy] Preliminary proposal for Issue 93]
Mike: Our developers would like a complete separation between policy information and the other parts of the SCDL. That is the thinking behind this issue. Ashok -------- Original Message -------- Subject: Re: [sca-policy] Preliminary proposal for Issue 93 Date: Thu, 5 Nov 2009 10:08:53 +0000 From: Mike Edwards <mike_edwards@uk.ibm.com> To: OASIS Policy <sca-policy@lists.oasis-open.org> References: <4AF233BC.5020801@oracle.com> Ashok, I have doubts about the value of doing this. In the SCA design, the main purpose of intents is to mark requirements that implementation artifacts have, that must be satisfied when they are deployed. Real policy is defined by bindings and policySets. It is possible to attach policySets to any place, either explicitly or by means of the external attachment mechanism. Since it is possible to do this, what purpose is served by attaching intents to any place? It will still be necessary to attach policySet(s) to the same places that the intents would be attached, so why not put all the effort into attaching the policySets in the right places? Yours, Mike. Strategist - Emerging Technologies, SCA & SDO. Co Chair OASIS SCA Assembly TC. IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain. Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431 Email: mike_edwards@uk.ibm.com From: ashok malhotra <ashok.malhotra@oracle.com> To: OASIS Policy <sca-policy@lists.oasis-open.org> Date: 05/11/2009 02:14 Subject: [sca-policy] Preliminary proposal for Issue 93 ------------------------------------------------------------------------ http://www.osoa.org/jira/browse/POLICY-93 Allow external attachment for intents I thought I would outline the proposal so that if we have time we can have a brief discussion on Monday. If there is positive sentiment I will draft a more complete wording proposal for the next telcon The motivation behind this issue is the separation of policy and executable code. This is what made us go in the direction of allowing external attachment for policySets. We argue that policy artifacts should be stored and managed separately from code and should have their own lifecycle and management. Probably managed by different departments. It should be possible to change intents and policySets anytime during the application lifecycle -- even after the application starts to run. And in some cases, of course, the SCDL cannot or may not be changed. So, it should be possible to add or change abstract policy requirements independent of the SCDL. The proposal requires 2 steps: 1. Add an @attachTo attribute to the intent element. The value of the @attachTo attribute is an XPath expression over the Domain Composite Infoset and it is evaluated in a manner analogous to the @attachTo attribute on policySets to indicate the SCDL element where the intent is to be attached. An alternate design is to introduce a new element, say <intentAttachment> which has 2 attributes. The @intent attribute takes a QName as its value and identifies an intent and an @attachTo attribute that takes a XPath expression as its value and identifies the SCDL element that the intent is to be attached. 2. Add a processing rule to the External Attachment section that says: attach the intents before attaching the policySets. -- 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 ------------------------------------------------------------------------ / / /Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU/ -- All the best, Ashok
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]