Re: [sca-policy] ISSUE 46: How to configure policySets - Please review

[Mike Edwards <mike_edwards@uk.ibm.com>]

Dave,

Well done for producing this new draft.

Regarding Issue 46 - clearly the meat
of this change is actually destined for the Assembly TC since it is a change
to the main SCA
namespace XSD - and quite an extensive
set of changes too.  I'm happy to help draw up that updated XSD for
submission to the
Assembly TC.

However, here are some points I note
in the application of Issue 46 in the Policy Spec 09 draft:

1) Line 758 - the new child element
is called <policySetAttachment/>.  This is incorrect according
to both the original proposal and 
the meeting minutes which record the resolution.  It should be called
<policySet/>.  Of course, this affects a few other places later
in the updated spec too.

2) Line 778 - the proposal has the <policySet/>
element with two attributes-  @name and @select.  There is no
description of the
@select attribute here (or anywhere
else that I can see).  It would be a good idea to have pseudo-schema
for the <policySet/>
element

This affects the schema in lines 2676-2680
also.

3) Line 782 is unnecessary as a normative
statement.  Let me motivate why this is so.
Basically, the SCA specs should all
claim that ANY SCA runtime should honour a composite file (or other file
such as definitions) that
conforms to the SCA XSD(s).  Only
conformance points that cannot be captured in XSD need to be spelled out
separately as normative
statements.  
In this case, the XSD shows both a @policySets
attribute and a <policySet/> child element.  The XSD allows
both.  An extra normative
statement is only required if using
one prevented the use of the other - - which is not the case here.  The
only thing that needs to be said
is that any policySet(s) specified in
the @policySets attribute are added to the policySets(s) specified in the
<policySets/> child element.

I suggest the following is used to replace
782/783:

"Where an element has both a @policySets
attribute and a <policySets/> child element, the policySets declared
by both apply to the
element."



A suggestion that I would like to make
is that once these adjustments are made, we create a clean version of the
spec and call it CD-02
(call for a formal vote to declare it
a CD), given that this contains a whole series of significant updates from
the original CD-01.



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:	David Booz <booz@us.ibm.com>
To:	sca-policy@lists.oasis-open.org
Date:	17/10/2008 22:07
Subject:	[sca-policy] ISSUE 46: How to configure policySets - Please review

---

I've applied Issues 22, 42, 46, 52/55, 53, 56, and 58
and produced working draft 09.

I ran into one problem. The resolution for Issue 46 gave a direction, but
did not specify specifics, and the specifics turned out to be a little
complex. I took a shot at specific text in this working draft, but you
may not like what I did, so take a look. Each place modified for issue
46 is marked with a comment. Also, This resolution has an effect on the
assembly spec, so if this resolution is acceptable to the TC, then I will
open an issue in Assembly for the appropriate corresponding updates.

Issue 46 - How to configure policySets (http://www.osoa.org/jira/browse/POLICY-46)
Resolution - Add a new child element to the SCDL so that a policySet can
be attached in this way, in addition to being attached via an XML attribute.

WD09 is here:
http://www.oasis-open.org/committees/download.php/29695/sca-policy-1%5B1%5D.1-spec-wd-09.doc

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

---

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