Re: [sca-bindings] Issue 2 proposal v14

[Simon Nash <oasis@cjnash.com>]

Eric Johnson wrote:
> The only thing that gets me is the passive voice in the last sentence. 
> The passive voice in the rest of the paragraph may be hard to avoid.
> 
> Anish Karmarkar wrote:
>> Attached.
>>
>> The changes I have made from v13 are:
>> 1) s/200712/200903/g to sync up with the assembly PR NS
>> 2) s/\/200812//g -- this is for the relationship URI. I don't think we
>> need a date component in here. This would avoid any confusion wrt the
>> NS URIs. In fact the recent trend is to not include the date in the NS
>> URIs either. See WS-Policy NS URI. I know OASIS has a NS guideline
>> which has YYYYMM in it, but this isn't a NS URI, so the policy doesn't
>> apply.
>> 3) I changed the wordings for the listener case (based on Mike's
>> suggestion). It reads as follows:
>>
>> "When a service that offers a bidirectional interface is invoked,
>> depending on the semantics and/or implementation of the service, it is
>> possible that the service might invoke the callback interface before
>> the forward operation ends. In such cases, it is necessary for the
>> binding on the reference-side to be listening for callback request(s)
>> from the service, before the forward operation request is sent on the
>> wire to the service, and continue listening as long as callback
>> requests are expected. It is possible that before the response to the
>> forward request is sent a response to one or more callback requests
>> are required by the service."
> 
> How about "As one possible example, a service could send one or more
> callback requests before determining and sending the response the
> original forward request."
 >
I don't like the original wording either.  As well as the passive
voice, there is singular/plural gramatical confusion in "....a response
to one or more....are required....".

However I think we have lost something in Eric's rewording, which is
that the service might need responses to its callback requests
before it can send its response to the callback request.  Eric's
words only talk about the service sending callback requests.
Here's my suggested rewording of Eric's version:

"As one possible example, a service might need responses from one or
more callback requests before determining and sending the response
to the original forward request."

   Simon

>> I'm hoping that we can close the issue on the call.
> Me too, which makes me add that I do not want to hold up the proposal
> either way, and equally makes me hesitant to even suggest this small
> change.  I'm very sorry I didn't suggest it sooner.
> 
> -Eric.
> 
> ---------------------------------------------------------------------
> 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 
> 
> 
>