But which are our architectural elements you may ask? Services or resources? I posted my thoughts over at the W3C mailing list. For those who have been following what Jim and I have been saying about OGSI, WSRF (and to a lesser extent about WS-Transfer), this post is a short summary. Expect more when we finish our promised MEST paper (the long version).
Steve seems to think that I will be thrown out of W3C because of this :-).
Tim discusses the problems with the vendors’ lack of a shared understanding of the WS architecture (“When architectures collide”) and he links to my post as an example.
It seems to me that because of the lack of a shared vision of the WS architecture, the WS-* stack is becoming a set of technologies that will attempt to please everyone and enable everyone’s architectural visions. I have no doubt that this will be possible (resources, objects, services, etc.). It’s possible to build distributed-object-based applications using XML and SOAP as it is possible to build service-oriented applications using object-oriented toolsets (e.g. CORBA/DCOM/etc).
I was hoping that the WS-* stack would be a good set of focused tools for building interoperable service-oriented systems. Let’s see where the WS-Highway ends.
Last year, I released the "Graph Model" library for .NET as an open source project. It…
Today I'm pushing Spring Voyage out of the harbor. You can track its journey on…
In my last post, I wrote that "the typing of code was parallelized and delegated.…
In February, I wrote about the small team I'd stood up instead of hiring humans:…
Assembling a dream team without a single hire I've been making great progress on CVOYA's…
As 2025 is now behind us, I wanted to share a few reflections from my…