InfoWorker Solutions

In a comment on the InfoQ article Contract Versioning, Compatibility and Composability about my definition of service forwards and backward...

A few weeks ago, I posted an illustration of the SOA service + schema versioning ripple effect for incompatible or sematic changes. Steppin...

The definitions for backwards compatible and forwards compatible contracts are straightforward: A new version of a contract that continues ...

An article about " Contract Versioning, Compatibility & Composability " in service-oriented solutions that I've written to...

In my SOA versioning, compatibility & composability session at NNUG this week, I stressed the importance of recognizing the ripple effec...

I'll be giving a session on service+schema compatibility & composability at NNUG Oslo on 25. November: details here . Among the top...

In a few weeks time I will be giving a session at NNUG on SOA service and schema versioning strategies and practices. A central topic will b...

As part of your SOA governance efforts, it is not sufficient to handle just the versioning of the services and the data schemas used by the...

As part of your SOA governance efforts, you should have a process for service lifecycle management. Many already use the policy that the thr...

The  business process information model (BPIM) is not intended for solving versioning issues for a specific service, that can be solved us...

This post is about service semantics and how to be “liberal in what you accept” in your service-oriented architecture implementation. Let me...