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.
Few months ago, we bought a sculpture from a local art fair for our Palm…
There’s a unique energy that comes with starting something new — a blend of excitement,…
As I continued work on BrainExpanded and its MCP service, I came to realize that…
Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…
After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…
Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…