Speaking of Specs, I'd suggest something like "to be Avalon compatible your container must obey this semantics/rules". Having a hybrid can be too complex.
?!?!?!
Isn't this the core of what Aaron has proposed on a number of times?
(a) The community pull together and work in unity as one to establish these specifications that define the semantics/rules (framework+meta+whatever).
(b) Then the community work together in unity to build a single Avalon RI based on these semantics/rules.
(c) Then other containers/components (old and new) can be built or re-cast upon these same rules in order to (hopefully) usher in a new dawn of component/container interoperability?
Isn't this what Aaron's/Niclas' proposal of a TCK was all about -- a test to *certify* interoperability?
It appears, Hammett, that you not only understand this, but also agree with it. If so, what is all the fuss? In fact, I don't get most of what all this fuss is about?
I don't think anybody wants to abandon any user base of any product, but the thinking is to attempt to rally the entire community around a single purpose and goal so that everybody's efforts (container developers and component developers alike) can be re-used for the benefit of all.
Timothy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
