Re: Friendly amendment #2c [Re: Straw poll on "synchronous" definitions]

>I think that Arkin responded on this point. We call them MEPs or Message 
>Exchenge Patterns for a reason:-) I am fairly certain that the XMLP group 
>had oneway message exchanges in mind when it coined the "MEP" phrase since I >was there at the time:)

In which case, it's message "exchange" patterns.  Which is fine
once it's been explained, but may not be all that obvious to
people who weren't "there".  Especially when you're trying to
incorporate it into the definition of sync/async, a subject plagued
by scope issues IMO.

>> Can you elaborate on why the definitions should not be complementary? 

>Because as Roger has so eloquently pointed out, his Aunt Mary is not 
>synchronous, so she must be asynchronous by our definition? I think we can do 
>better.

I think this is an instance of the scope problem, mainly, not an
argument against complement.  When you say Aunt Mary is not synchronous,
you've already lost me.  Could we have an in-scope example to make
this point, please?

Also, is it now fairly well established that the sync/async definitions
being worked on for the glossary are bounded to qualifying MEPs?  If
so, I'd like to resurrect an earlier suggestion, which is to change the
definition headings to "Synchronous Message Exchange", etc.  The broader
the task, it seems, the harder to get some consensus.

Regards,
Walden