Re: [sca-policy] Wording for Issue 87

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

Hi Raymond:
You seem to be reading some words that were deleted in the proposal.  
Here is how that paragraph should read.

With this design principle in mind, an XPath expression that is the 
value of an @appliesTo attribute designates what a policySet applies to. 
Note that the XPath expression will always be evaluated against the 
Domain Composite Infoset as described in Appendix Awithin the context of 
an attachment considering elements where binding instances or 
implementations are allowed to be present. The expression is evaluated 
against /the parent element of any binding or implementation element/. 
The policySet will apply to any child binding or implementation elements 
returned from the expression. So, for example, appliesTo=”//binding.ws” 
will match any web service binding. If 
appliesTo=”//binding.ws[@impl=’axis’]” then the policySet would apply 
only to web service bindings that have an @impl attribute with a value 
of ‘axis’.

If your mail reader is giving you the deleted words here is the net.

With this design principle in mind, an XPath expression that is the 
value of an @appliesTo attribute designates what a policySet applies to. 
Note that the XPath expression will always be evaluated against the 
Domain Composite Infoset as described in Appendix A//. The policySet 
will apply to any child binding or implementation elements returned from 
the expression. So, for example, appliesTo=”//binding.ws” will match any 
web service binding. If appliesTo=”//binding.ws[@impl=’axis’]” then the 
policySet would apply only to web service bindings that have an @impl 
attribute with a value of ‘axis’.



All the best, Ashok


Raymond Feng wrote:
> Hi,
>
> I like the proposal. I have a question on the following statement from 
> the draft:
>
> With this design principle in mind, an XPath expression that is the 
> value of an @appliesTo attribute designates what a policySet applies 
> to. Note that the XPath expression will always be evaluated against 
> the Domain Composite Infoset as described in Appendix Awithin the 
> context of an attachment considering elements where binding instances 
> or implementations are allowed to be present. The expression is 
> evaluated against /the parent element of any binding or implementation 
> element/. The policySet will apply to any child binding or 
> implementation elements returned from the expression. So, for example, 
> appliesTo=”//binding.ws” will match any web service binding. If 
> appliesTo=”//binding.ws[@impl=’axis’]” then the policySet would apply 
> only to web service bindings that have an @impl attribute with a value 
> of ‘axis’.
>
> Would the policySet apply to the ancestor elements of the selected 
> binding/implementation elements?
>
> Thanks,
> Raymond
> ------------------------------------------------------------------------
> *Raymond Feng*
> Senior Software Engineer, Apache Tuscany PMC Member & Committer
> /IBM Bay Area Lab, 1001 E Hillsdale Blvd, Suite 400, Foster City, CA 
> 94404, USA*
> E-mail*//: //_rfeng@us.ibm.com_/ <mailto:rfeng@us.ibm.com>/, 
> *Notes*//: Raymond Feng/Burlingame/IBM, *Tel*//: 650-645-8117, 
> *T/L*//: 367-8117*
> Apache Tuscany*//: //_http://tuscany.apache.org_/ 
> <http://tuscany.apache.org/>/
> Co-author of Tuscany In Action: //_http://www.manning.com/laws_// /
> ------------------------------------------------------------------------
>
>
> ashok malhotra <ashok.malhotra@oracle.com> wrote on 09/29/2009 
> 02:13:46 PM:
>
> > From:
> >
> > ashok malhotra <ashok.malhotra@oracle.com>
> >
> > To:
> >
> > OASIS Policy <sca-policy@lists.oasis-open.org>
> >
> > Date:
> >
> > 09/29/2009 02:16 PM
> >
> > Subject:
> >
> > [sca-policy] Wording for Issue 87
> >
> > The discussion on Issue 87 on the last telcon moved to consider the
> > suggestion that the XPath value
> > of the @appliesTo attribute of policySets be evaluated against the
> > Domain Composite Infoset.
> > It was argued that this was simpler than resetting the context item to
> > the parent of the binding/implementation
> > everytime the XPath needed to be evaluated.
> >
> > Accordingly, I have prepared wording that incorporates this change.  In
> > doing this I have assumed that
> > the resolution to issue 107 will result in an Appendix that spells out
> > how the Infoset is constructed.
> >
> > The suggested changes are attached.
> > --
> > All the best, Ashok
> > [attachment "Issue 87 Wording.doc" deleted by Raymond Feng/
> > Burlingame/IBM]
> > ---------------------------------------------------------------------
> > 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