Re: FW: Reliable Messaging Summary

Yes - thus the caveat.  I am still feeling out the uber-question within 
this group that faces all architectures - How do you add enough 
constraints to make the architecture effective without unnecessarily 
limiting the implementations?  If "receive and event" is too far into 
implementation,  then the alternative wording is fine with me.  I did 
note however,  that this group uses the term "Reference Architecture" 
which to me means more prescriptive.  "Able to determine" works.

Duane

David Orchard wrote:
> Personally, I think Duane's definition goes to far into design.  "receive an
> event" is design, whereas "able to determine" is a requirement.
> 
> Cheers,
> Dave

-- 
VP Strategic Relations,
Technologies Evangelist
XML Global Technologies
****************************
ebXML software downloads - http://www.xmlglobal.com/prod/