You get very defensive everytime I mention Merlin in light of Phoenix
and Fortress. What's the deal?
I think your assertions on thread have been missleading.
That statement seems to insinuate that I am intentionally being misleading. I am not, furthermore, I do not see where I am being misleading. Disagreement does not equal misleading.
First:
Do not make statements that cast doubt on the intelligence of your peers.
I'm not casting doubt on your intelligence - I'm actually complementing you on your creativity.
That's like saying "Your pretty smart, for an inbreed." Keep your backhanded compliments to yourself please. They are not appreciated.
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.
Please take a closer look at what I said above and the prior discussions concerning AMTAGS. I also suggest you take a closer look at Phoenix, tag usage and meta-model before presenting the Phoenix/Fortress commonality as a case supporting your position. Also, it would be perhaps wise if we stay away from assertions such as "first" == "de facto standard". Standards are built either through consensus or convergence based on needs. Consensus is a result of collaboration whereas convergence is more typically a result of adoption in order to gain some tangible benefit. In the case of AMTAGS it is neither - it is simply a starting point in the process of potentially establishing a standard.
That will be the subject of another thread. However DO realize that Phoenix is a released container, and as such has more credibility as to how components are defined and used than Merlin at this stage. Therefore, it would be wise to retain as much of that usage as possible so as not to force our users to rewrite their components or change source code every time we release something. I get the impression that you fail to realize this.
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.
How is this divergent? It actually reflects discussions on this list. It addresses on of the interoperability stumbling points that constantly reappears - namely assumptions by containers about context. The usage of URN style naming in no way inhibits the application of Merlin nor forces any constraint on component authors. I simply do not see how this is any shape of form supports you divergence theory.
Those discussions were never adopted as the official way we were going to do things. In fact, where it was last left, there was still some disagreement as to whether we should use URNs or not. I see that as divergent from community consensus.
* 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.
This has already been addressed under another thread. Merlin does not comply for some very good reason. The AMTAGS proposal as it stands today is woefully insufficient - clearly insufficient to meet Merlin needs - and keep in mind that Merlin "needs" translate directly to component management without container lock-in. Beyond that, you are aware of the actions I've been taking to address AMTAGS and arrive at something workable. If this is the source of divergence that your so keen on pressing home - then I suggest to that there are perhaps better and more constructive approaches to raising this.
I haven't seen anything concrete to support your position, and this subject deserves its own thread. I would encourage you to start a thread and detail exactly what is insufficient in the AMTAGS proposal.
Steve, this last comment is unnecessary. Please refrain from such comments
as they do not help.
Berin - this entire thread is unnecessary!
;-)
Apparently it is, as you seem not to be learning anything. Your smiley does not counteract the slap in the face that your last comment is. Please learn how to express your oppinions without attacking the person you disagree with.
--
"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]
