When architectures collide: a great example

<p>
I know everyone is scared of Savas on the OGSA mail list at GGF, but I think the WS-Addressing mail list at w3c.org are about to fear him too. He doesnt come out and say, "I am Savas! Fear me, you unworthy purveyors of legacy object oriented thinking", but he does <a href="http://lists.w3.org/Archives/Public/public-ws-addressing/2004Dec/0006.html">
post mail implying that the emperor's clothes are bit inconsistent when it comes to WS-Addressing</a>
</p>
<p>
<p>
On the subject of EPR comparision, having two different EPRs cannot guarantee that the resources are different. Just like you can have two URLs point to the same thing. All you may be able to say is that equal EPRs imply equal objects, but then you need strict XML comparison rules; case insensitive URI comparison is inadequate. For CDDLM, our application EPRs (yes, I am now unworthy!), have an ID property (yes, a WS-ResourceProperty!) that is required to be strongly unique.
</p>
<p><a href="http://pluralsight.com/blogs/tewald/archive/2004/12/02/3735.aspx">via tim</a></p>

i've been enjoying your posts, and would be greatly appreciative of some minimalistic context when linking:
'this email presents a good example of resource v. service oriented in a rubber-meets-the-road bank account example'

Steve,

I actually picked this post without looking at who posted it. I don't know Savas and I was not trying to imply anything about him. I just thought his post was a good example of the conversations that were going on re: WS-Addressing.

Tim-

Myren,

You're right. That's one of the reasons I like to write longer posts. Too often, I find short blog posts don't tell me enough about what I'm being pointed toward. Here I am guilty of same myself. I'll try to be better about it. Thanks for the constructive criticism.

Tim-

Hey Tim,

Don't worry about what Steve said. He was just joking. We are good pals and have similar ideas about service-orientation. BTW... I am Savas :-)

.savas.