NEW ISSUE: Clarify the handling of Intents

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

Raiser:   Mike Edwards

Target:    Policy Specification

Description:

The publication of the resolution of
Issue 38 has resulted in some re-examination of the function relating to
Intents and a
series of questions have arisen that
require the text to be clarified and updated.  The following are the
questions that 
need to be answered:

- Issue 38 introduced 2 rules.  Which
order are they meant to be applied - 1 first or 2 first?
the specification needs to be explicit
about this

- Issue 38 text tends to talk about
elements down to services and references and does not deal with binding
elements
(or other lower level elements).  The
text needs clarification and extension to discuss what happens to those
other
elements, especially where they "inherit"
intents from other elements.

- Issue 38 is not clear enough on what
cases will cause mutual exclusive errors when inheriting intents from 
component implementations - in particular
where say a component <service.../> element has an intent that
is in conflict with an intent in the
componentType<service.../> element - and how this differs when compared

with intents on the <component.../>
element. 


Proposal:

None at this time.



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