OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-policy message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-policy] Discussion re Issue 79


I'm going to disagree on point 1, and maybe we can improve the spec language as a result.

The phrase "... and the set of policySets that apply to the element." is not talking about direct attachment, it is talking about all policySets that are applicable (apply not attach) to a given element. That is, all the policySets that are attached (directly or indirectly) to the element or it's parent element. I get the feeling that you'd rather spell out all the cases, something like this:

All intents in the required intent set for an element MUST be provided by the directly provided intents set and the set of policySets that are directly or externally attached to the element or one of its parent elements.

It's much more wordy but perhaps that's the precision you're looking for?

However, having said that, the main question you asked in issue 79 is this: "even if you support only External Attachment, you still must include all the intent definitions in the domain. Does this make sense?" My answer is simply, yes, it makes sense to me because the spec has defined XPath functions so that one can use the intents in the XPath attachment expression. I think we can close 79 with no action based on this.

But, by reading your text below, it seems like you're trying to morph the issue into something subtlely different. Your second point below is really asking; "Can a conformant runtime support intents SOLELY for the purpose of using them as a way to identify the attachment points of externally attached policySets?" What's the motivation for allowing that?

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

Inactive hide details for ashok malhotra ---08/17/2009 02:28:22 PM---The current spec says All intents in the required intent sashok malhotra ---08/17/2009 02:28:22 PM---The current spec says All intents in the required intent set for an element MUST be provided


From:

ashok malhotra <ashok.malhotra@oracle.com>

To:

OASIS Policy <sca-policy@lists.oasis-open.org>

Date:

08/17/2009 02:28 PM

Subject:

[sca-policy] Discussion re Issue 79





The current spec says
All intents in the required intent set for an element MUST be provided
by the directly provided intents set and the set of policySets that
apply to the element./ /[POL40018 <#POL40018>]

First, I think this should read
All intents in the required intent set for an element MUST be provided
by the directly provided policySets that apply to the element./
/[POL40018 <#POL40018>]

Second, this addresses  only the direct attachment case.  I think we
need some words for the External
Attachment case.  For this case, I think we need to say:
a. Intents MUST be recognized by a runtime that supports External
Attachment.
b. The presence of intents can be used in XPath functions that make up
the value of the @attachTo
attribute for Externally Attached policySets.
c. Intents may be satisfied by bindings or policySets.
d. All intents need not be satisfied.
--
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 





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]