Re: [sca-bindings] Issue 2: proposal v11

[Eric Johnson <eric@tibco.com>]

There's one point that I tripped on.  At the very end, with the example
using "WS-MakeConnection", you say:

"3) Callback request message (from the service to the reference) sent as
a “response” to MakeConnection" - Doesn't it need to be simply "callback
message (from the ..." - I don't see an opportunity for a
request/response exchange here."

Do we need to flag, at the first introduction of WS-MakeConnection, that
it can only be used for one-way operations on the callback interface?

-Eric.

Anish Karmarkar wrote:
> Thanks for the comments. Mostly agree with all of them.
>
> -Anish
> -- 
>
> Simon Nash wrote:
>> Anish,
>> My comments are inline in the attached document.
>>
>>   Simon
>>
>> Anish Karmarkar wrote:
>>> Attached.
>>>
>>> I accepted changes from v10 and made additional changes as I was
>>> tasked to do during the last call. This should address all the
>>> comments/issues so far except for one, which is the name of the
>>> WS-Policy assertion.
>>>
>>> I have changed it from sca:CallbackAssertion to sca:WSCallback. My
>>> rationale for this is:
>>> 1) 'Assertion' is redundunt, so removal just makes it shorter and
>>> shorter is better.
>>> 2) This is a callback mechanism that is defined for Web services.
>>> Other bidnings/technologies that are used in SCA may have a
>>> different mechanism for callback so the previx 'WS' makes sense.
>>> This constrains it to the realm of Web services.
>>>
>>> The other suggestion that was made by Mike was
>>> sca:CallbackAssertion_WSA. I prefer a WS (or WSA) prefix rather than
>>> a suffix and the underscore is unnecessary. So I suppose another
>>> alternative would be 'sca:WSACallback'.
>>>
>>> -Anish
>>> -- 
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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 
>>
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> 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 
>
> ---------------------------------------------------------------------
> 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