Berin:
I read though your reply a couple of time and totally failed to locate anything that supported you claim that Merlin is divergent. About the only concrete statement was the following - and that left me somewhat confused ...
You get very defensive everytime I mention Merlin in light of Phoenix and Fortress. What's the deal? Last time I checked we were on the same team.
Fortress and Phoenix share a subset of meta-info descriptors
What is the subset of meta-info that Fortress and Phoenix share? It is my impression that Fortress and Phoenix have take divergent paths (I'm inspired by your own creative application of this word). Fortress keys of a @avalon.component whereas Phoenix keys of @phoenix.component for one variant of its meta-model and @phoenix.block for what it calls legacy support for the <blockinfo> style (neither of which have anything to do with Fortress or Merlin). If we dig into the actual descriptors the differences between Fortress and Phoenix are even more distinct and container specific relative to anything in Merlin. Given that the meta-info package we are separating out from Merlin includes fully support for the legacy Phoenix model, along with support for the declaration of Fortress context assumptions, and provides complete support for the Avalon context spec. - it would be really helpful if you could clarify for me what it is that prompts you to suggest that Merlin is divergent?
First:
Do not make statements that cast doubt on the intelligence of your peers. This does not help your position, but rather hurts it. (I am referring to your parenthetical statement in the second sentence of the above paragraph).
Second:
AMTAGS is in use with both Fortress and Phoenix. Because Phoenix was our first forray into the world of meta-info and context entries, it is our de facto standard. If the standard needs to be changed, we need to identify what and how.
As to how Merlin is divergent (hopefully you will get it this time):
* All your context entries use the full URN notation, which makes Merlin the only container to support this styling.
* Merlin suggests that there is much more in the avalon namespace than anyone has agreed to. AMTAGS is our current standard--it needs to be adjusted, but it is what we have. Merlin does not comply.
Can I should assume that your statement concerning "divergence" was perhaps just a touch off the mark? Perhaps you meant to say "open", "adaptive", "encompassing", or dare I say "all-embarrassing"?
Steve, this last comment is unnecessary. Please refrain from such comments as they do not help.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
