Final minutes for Feb 8th 2010

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

Folks,

Here are the final minutes:




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

---

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

Title: SCA-Policy - 2010-02-08

Hide Chat

- FINAL -

Oasis SCA-Policy Teleconference

08 FEB 2010

Attendees

Present

Eric Wells	Hitachi, Ltd.	Group Member
David Booz	IBM	Group Member
Simon Holdsworth	IBM	Group Member
Anish Karmarkar	Oracle Corporation	Group Member
Rich Levinson	Oracle Corporation	Group Member
Ashok Malhotra	Oracle Corporation	Group Member
Gilbert Pilz	Oracle Corporation	Group Member
Fabian Ritzmann	Sun Microsystems	Group Member
Murty Gurajada	TIBCO Software Inc.	Group Member
Pundalik Kudapkar	TIBCO Software Inc.	Group Member

Chairs

David Booz
Ashok Malhotra

Scribe

Eric Wells

Agenda:

Agenda SCA Policy Telecon - Feb 8 2010

Callin Number: See below

Chatroom: http://webconf.soaphub.org/conf/room/sca-policy-TC

1. Roll call

2. Confirm minute taker

3. Agenda bashing

4. Meeting Minutes
Vote to accept minutes from Feb 1 2010
- http://www.oasis-open.org/committees/download.php/36194/SCA%20Policy%20minutes%202010-02-01.pdf

5. TC Administrivia:
a. Recording issue status - 2 Open

6. PRD status update
a. 9 issues from PR 01 comment list that still need responses (Dave)

7. ACTION ITEMS:
a. 20100104-01: owner=editors status=pending Fix the name of the file in Appendix B1 to match the actual name of the file.

8. New Issues
None

9. Blocking Issue Discussion
None

10. Additional Issue Discussion
a. ISSUE 93: Allow external attachment for intents
http://www.osoa.org/jira/browse/POLICY-93
proposal: http://lists.oasis-open.org/archives/sca-policy/201001/msg00023.html
latest: http://lists.oasis-open.org/archives/sca-policy/201002/msg00011.html

b. ISSUE 116: Simplify policySet model?
http://www.osoa.org/jira/browse/POLICY-116
proposal: In JIRA

11. Testing
a. Test Status:
http://lists.oasis-open.org/archives/sca-policy/200911/msg00047.html

- Test Assertion Document:
DOC: http://www.oasis-open.org/committees/download.php/35139/SCA-Policy-1.1-Test-Assertions-WD-05.doc
PDF: http://www.oasis-open.org/committees/download.php/35138/SCA-Policy-1.1-Test-Assertions-WD-05.pdf

- Test Case Documents
ODT: http://www.oasis-open.org/committees/download.php/35141/sca-policy-1.1-testcases-wd02.odt
PDF: http://www.oasis-open.org/committees/download.php/35140/sca-policy-1.1-testcases-wd02.pdf

- Testcase code:
http://tools.oasis-open.org/version-control/svn/sca-policy/TestCases/

12. AOB
a. straggler roll

---

Contents

Topics

[1]  Opening

[2]  ActionItems

[3]  New Items

[4]  Open Items

[5]  AOB

Table of Resolutions

Table of Action Items

---

Action Items

---

Resolutions

• 2010-02-08-1: Minute of 2010-02-01 accepted w/o
• 2010-02-08-2: Defer further consideration of POLICY-116 until Policy Framework 1.2

---

Minutes

Scribe: Eric Wells

Opening

Roll - 10/14 = 71% Quorate

Agenda - no changes

Minutes of 2010-02-01: http://www.oasis-open.org/committees/download.php/36194/SCA%20Policy%20minutes%202010-02-01.pdf

No objections

Resolution: Minute of 2010-02-01 accepted w/o

ActionItems

As listed in agenda - no updates

20100104-01: owner=editors status=pending Fix the name of the file in Appendix B1 to match the actual name of the file.

New Items

None.

Open Items

POLICY-93

ISSUE 93: Allow external attachment for intents
http://www.osoa.org/jira/browse/POLICY-93
proposal: http://lists.oasis-open.org/archives/sca-policy/201001/msg00023.html
latest: http://lists.oasis-open.org/archives/sca-policy/201002/msg00011.html

Comments numbers refer to E-mails above.

Dave B:

Comment 1 remove Ashoks changes

Ashok M:

Agreed

Dave B:

Comment 2 - changes in Appendix

 

...don't like this as there's normative statements included and don't like this style

 

...didn't understand Ashoks proposal on how to handle this

Ashok M:

Used for both intent and policySet so doesn't belong in one section specifically

 

...thought it would be better taken out of general flow of document

Dave B:

That's what I didn't like!

 

...but understand the argument

 

...However need infoset to understand XPath stuff so would prefer it closely before that section.

Any other opinions?

Leave as appendix and see how that fits with rest of changed document - same as Ashoks proposal

Dave B:

How to deal with normative statement?

Ashok M:

pull out of appendix and put inline with text

Dave B:

In section 4

Dave B:

Comment 3

 

...On section 4.3 - formatting correction

<Ashok>

Move normative statement in Appendix to section 4.7

Agreed that there should be 3 (three) normative statements - fix as required

Dave B:

Comment 4

 

...also in section 4.3

Attach intents before policySets

Ashok M:

Normative statement - put in both places where it applies.

Dave B:

issues also come up in later comments - suggest considering with those

jumping to Comment 8

Dave B:

What happens when deploying new intents? Do we have to re-evaluate intents/policySet that are already deployed?

 

...what happens if the new intent causes and error (existing is already running)?

Ashok M:

Convinced about these issues - agrees that we will need a new section on deployment

Ashok will create a new section on deployment to deal with Comments 4, 8, 9

<Ashok>

This will go close to the Algorithm

Dave B:

Comment 5

Ashok will move 4.6.2 to appendix

Dave B:

Comment 6

Add text to disallow use of intent XPath in attchTo

Dave B:

Comment 7

 

...New normative statement added

 

...in section 4.9

 

...compared with algorithm for resolving intents implies opposite functionality

Dave B:

suggest removing new normative statement

Ashok will review and remove if contracdictory

Dave B:

Comment 10

 

...what happens if a newly deplyed intent is not satisfied?

 

...that should be an error, but would previously be detected at deployment - NOW could be at runtime

 

...that makes things really difficult

 

...Can we say that when an intent is deployed thate must also be a policySet that satisfies the intent?

Ashok M:

Agree but need to think about this further

Ashok will add consideration of runtime to new section on deployment

<Ashok>

Impact on running instances and deployed composites

No further discussion on POLICY-93

POLICY-116 - Simplify policySet model?

Proposal in JIRA: http://www.osoa.org/jira/browse/POLICY-116

Ashok M:

Reviews his proposal

 

...people like the idea, but think its too much work

Eric W:

Like the proposal but think it should be in next rev

Motion: m=Ashok s=EricW Defer further consideration of POLICY-116 until Policy Framework 1.2

No further discussion, no objections

Resolution: Defer further consideration of POLICY-116 until Policy Framework 1.2

AOB

Straggler role - none heard

Meeting adjourned 09:53 PST

<Dave Booz>

thx for scribing today Eric, I really appreciate it

N.P. What do you want to do about formatting and adding the role?

<Ashok>

I'll take care of the roll, Eric

OK Thanks Ashok

[End of Minutes]
Formatted on 2010-02-11 at 06:16:34 GMT-5

---

Minutes formatted by Schreiber, a collection of XSLT stylesheets by Bob Freund modeled after David Booth's scribe

=