ASSEMBLY-189: Allow intents to be associated with WSDL using a childelement

Folks,

If the idea is then to replace @requires
attribute with a <requires/> subelement, then I question

what the <requires/> subelement
is bringing to the table.  @requires attribute is simple and

straightforward, <requires/> subelement
is more complex and harder to use.  Given that @requires

merely contains a set of strings, why
do we need a subelement?

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:  

From:
Anish Karmarkar <>

To:
Mike Edwards/UK/IBM@IBMGB

Cc:
OASIS Assembly <>

Date:
10/11/2009 18:10

Subject:
Re: [sca-assembly] NEW ISSUE:  Allow
intents to be associated with WSDL using a child element

If we are going to allow the <requires> element
on portTypes and 

portType/operations then I don't see a need for the @requires attribute

on those same WSDL elements. We should pick one syntactic way of 

specifying intents in WSDL, allowing both doesn't make a lot of sense to

me. So if we go down the road of <requires> element in WSDL, I would

suggest that we use that to *replace* the existing @requires attribute

in WSDL.

-Anish

--

On 11/10/2009 12:32 AM, Mike Edwards wrote:

> 

> Logged as: _http://www.osoa.org/jira/browse/ASSEMBLY-189_

> 

> 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:  

> 

> 

> From:                
 ashok malhotra <>

> To:                
 OASIS Assembly <>

> Date:                
 09/11/2009 22:12

> Subject:              
   [sca-assembly] NEW ISSUE:  Allow intents to be
associated with 

> WSDL using a child element

> 

> 

> ------------------------------------------------------------------------

> 

> 

> 

> Section 7.5 describes how policy intents can be associated with WSDL

> portType and operation elements.

> The mechanism uses a @requires attribute on portType and operation

> definitions taking advantage of WSDL attribute

> extensibility.

> 

> The SCA Policy TC is close to resolving Issue 94 which allows intents
to

> be associated with SCDL elements

> using a <requires> child element.

> http://www.osoa.org/jira/browse/POLICY-94.

> This is an alternate mechanism to using the @requires attribute.

> To align the two specifications we need to add wording to the Assembly

> spec to allow intents to be attached to

> WSDL portType and operation elements using a <requires> child
element.

> 

> RELATED COMMENT:

> I'm looking at Assembly 1.1 cd03-Rev03 which still speaks abaout

> "portType and operation ..."

> I thought we had removed policies on operations.

> -- 

> 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/

> 

> 

> 

> 

> 

> 

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