W3C home > Mailing lists > Public > public-ws-semann@w3.org > July 2006

Fw: SAWSDL Issue: Clarification of documentation on Categorization information on WSDL interfaces

From: Rama Akkiraju <akkiraju@us.ibm.com>
Date: Tue, 25 Jul 2006 11:13:49 -0400
To: SAWSDL public list <public-ws-semann@w3.org>
Message-ID: <OF659A80EB.C971BC41-ON852571B6.00533915-852571B6.0053AA04@us.ibm.com>


I would like to suggest that the following text be added to the SAWSDL spec
in section '2.1.1 Annotating Interfaces With Model Reference' to address
the categorization issue that I had raised earlier.

Text Suggestion follows:

The categorization on an interface that is specified using a modelReference
applies to all operations in its scope. If one would like to specify a
different categorization (again via modelReference) for the operations than
the categorization of their parent interface, then we suggest the following
precedence rule. The categorization information specified on an operation
takes precedence over the one specified on its parent interface.

Rama Akkiraju

----- Forwarded by Rama Akkiraju/Watson/IBM on 07/25/2006 11:09 AM -----
             BM                                                         To 
                                       SAWSDL public list                  
             07/13/2006 05:13          <public-ws-semann@w3.org>           
             PM                                                         cc 
                                       SAWSDL Issue: Clarification of      
                                       documentation on Categorization     
                                       information on WSDL interfaces      


First, in the SAWSDL spec, we have currently mentioned that interfaces can
have modelReferences and these modelReferences can be used to specify
categorization information that could be used to categorize a service in a
registry. A WSDL interface can have multiple operations. If we specify
categorization information at a WSDL interface level does that mean that
all the operations under that interface have to be published to the same
category? That would be a reasonable thing to do but that is not explicitly
stated in the spec. We may want to add something to clarify this.

Second, what if someone wants to classify the operations within an
interface under different categories in a registry. That should be possible
with the current mechanisms. Basically, a user would then use the same
'modelReference' mechanism at the level of an operation to specify
categorization information. But in the spec we specifically mention about
adding categorization information only at the interface level but not at
the operation level. We may want to clarify this and add some documentation
that talks about the fact that categorization can be specified at the level
of an operation as well.

Finally, if categorization information is specified both at operation level
and interface level, we have to add precedence rules. I think the
categorization information at the operation level should have higher

Rama Akkiraju
Received on Tuesday, 25 July 2006 15:41:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:14 UTC