This post by Jean-Jacques over at ebpml.org suggests that SSDL couples a contract with Web Service endpoints. We’ve thought about this issue and this is the reason we’ve decided to make endpoints optional. A contract is still a contract even if there are no endpoints. The endpoints may be discovered out-of-band.
I also think that we are using the term ‘contract’ correctly. An SSDL contract describes a set of message interactions. For any two or more parties to meaningfully engage in conversations through message exchanges, they have to agree on the same contract. Whether the document is static and is forced upon others or it’s negotiated and used dynamically, it still needs to have a structure; that structure is what the SSDL specification defines.
SSDL in the news:
I am probably missing others.
I do hope that people will start commenting and giving us feedback; I know that it’s a lot of information to digest and people are busy. Let the discussions start. And remember… there is a dedicated mailing list too.
I am currently busy working on releasing the SSDL tool. I just finished the setup project (it was very easy with VS.NET 2005 🙂 but I need to do some work on how the plugins get discovered and receive command line arguments.
As part of the BrainExpanded project, I’m building an iOS app that lets users easily…
Artificial Intelligence (AI) has rapidly evolved over the past few decades, becoming an integral part…
Happy New Year everyone! I was planning for my next BrainExpanded post to be a…
See "BrainExpanded - Introduction" for context on this post. Notes and links Over the years,…
This is the first post, in what I think is going to be a series,…
Back in February, I shared the results of some initial experimentation with a digital twin.…