RE: Sample getter/setter take 3

Roberto,

Thank you for sending this. Please, see a comment bellow.

[snip]

>      <ws:operation
>           name="get_XXX"
>           style="http://www.w3.org/@@@@/@@/wsdl/style/get-attribute"
>           pattern="http://www.w3.org/@@@@/@@/wsdl/in-out">
>        <ws:input name="in" body="wrappers:get_XXX"/>
>        <ws:output name="out" body="wrappers:get_XXXResponse"/>
>      </ws:operation>
> 
>      <ws:operation
>           name="set_XXX"
>           style="http://www.w3.org/@@@@/@@/wsdl/style/set-attribute"
>           pattern="http://www.w3.org/@@@@/@@/wsdl/in-out">
>        <ws:input name="in" body="wrappers:set_XXX"/>
>        <ws:output name="out" body="wrappers:set_XXX"/>
>      </ws:operation>
> 

What is the difference between the two operations above and the ones
bellow?

<ws:operation name="get_XXX"
              pattern="http://www.w3.org/@@@@/@@/wsdl/in-out">
   <ws:input name="in" body="wrappers:get_XXX"/>
   <ws:output name="out" body="wrappers:get_XXXResponse"/>
</ws:operation>

<ws:operation name="set_XXX"
              pattern="http://www.w3.org/@@@@/@@/wsdl/in-out">
   <ws:input name="in" body="wrappers:set_XXX"/>
   <ws:output name="out" body="wrappers:set_XXX"/>
</ws:operation>

In other words, what would the accompanying language be for the specific
@style URI? What does such a URI suggest? Is it the case that a
<blabla>/{get|set}-attribute URI is going to be just a hint to tooling?

I still don't see the need for this but I guess an optional @style URI,
with no suggested semantics for a Web Service, is a reasonable
compromise.

Regards,
.savas.