Re: [sca-policy] Suggested wording to resolve issue 88

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

Folks,

While we're at it, let's fix another
little problem which is dragged up by Ashok's text below.

Note the presence of "WSDL Interface
elements (WSDL 2.0)" in the paragraph before the insertion
that Ashok proposes.  

WSDL 2.0 support was removed from Assembly
some time ago, so I suggest that we remove it from the
Policy spec too.  I note that this
is the ONLY occurrence of WSDL 2.0 in the Policy spec...

So, extend Ashok's proposal to the following:

Replace the entire 1st paragraph of
section 4.1 with the following:

Intents can be attached to any SCA element
used in the definition of components and composites since an intent 
specifies an abstract requirement. The
attachment is specified by using the @requires attribute. This attribute
takes 
as its value a list of intent names.
 Intents can also be applied to interface definitions. For WSDL portType
elements 
(WSDL 1.1) the @requires attribute can
be applied that holds a list of intent names that are needed by the interface.
 
Other interface languages can define
their own mechanism for specifying a list of intents.  Any
intents attached to an interface
definition artifact, such
as a WSDL portType, MUST be added to the intents defined in the @requires
list of the service 
or reference to which the
interface definition applies. If the @requires list of the service or reference
is empty then the intents 
attached to the interface
definition artifact become the only contents of the relevant @requires
list. [POL40027]


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:	ashok malhotra <ashok.malhotra@oracle.com>
To:	OASIS Policy <sca-policy@lists.oasis-open.org>
Date:	04/08/2009 21:04
Subject:	[sca-policy] Suggested wording to resolve issue 88

---

Here is suggested wording to resolve issue 88 
http://www.osoa.org/jira/browse/POLICY-88

Section 4.1 Attachment Rules - Intents says

“… Intents can also be applied to interface definitions. For WSDL Port
Type elements (WSDL 1.1) and for WSDL Interface elements (WSDL 2.0), the
@requires attribute can be applied that holds a list of intent names 
that are needed by the interface.”

Following this, add: “Any intents attached to a WSDL interface MUST be
added to the intents defined in the @requires list of the service or 
reference to which the interface applies. If the @requires list of the
service or reference is empty then the intents attached to the WSDL 
interface will become the only contents of the relevant @requires list.”

Since this wording includes a MUST, this should be added as a new 
conformance assertion and the TA document modified appropriately.
-- 
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

---

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