Web Services Choreography Description Language (WS-CDL)

WS-CDL is in my opinion an example of premature standardization. WS-CDL provides multiple layers of abstraction, an enormous set of features and a simulation based design. Personally I think a purely declarative approach with little or no abstraction that focuses on making it easy to describe basic stuff would have been better. I don't know which position, mine or WS-CDL's, or which mid-point between the positions is right but I'm pretty sure that no one else does either. We just don't have enough industry experience to standardize choreography descriptions. Unfortunately the potential standardization of WS-CDL can do real harm as it will likely freeze the experimentation and learning that the industry so badly needs.

Continue reading Web Services Choreography Description Language (WS-CDL)

Software Development Tools – Declaring Maturity

My job requires me to figure out road maps for software technologies. One of the key heuristics I use in figuring out where a software technology is likely to go is mapping out that technologies transition from a procedural to a declarative design environment. This technique is proving a big help for my work on utility computing.

Continue reading Software Development Tools – Declaring Maturity

Ode to Apple – The iMac Rocks!

Atoning for my mistake of buying my wife a Dell laptop running XP that has more or less been a constant nightmare over the years we've owned it I decided to give her a birthday present a bit early – a new iMac. My wife is no technophobe but similarly she is not a technophile. To her a computer is a way to get things done. But her attitude changed when I get her the iMac.

Continue reading Ode to Apple – The iMac Rocks!

Utility Computing – It's management, stupid.

All this talk of computing as a fungible utility is very nifty but it wouldn't be the first 'sounds great, adds nothing' technology to come down the pike (repeat after me – "I mostly just need XML and HTTP."). So as I embark on my new job of helping to figure out BEA's utility computing strategy I want to make sure that there is some value in "them thar hills". Which means that before I worry about what utility computing is or what it should do I want to first know what the problem is.

Continue reading Utility Computing – It's management, stupid.

What I do for a living

I'm a technical director and individual contributor who focuses on issues such as:

  • Corporate technical strategy (e.g. what technologies should we be investing in and when?),
  • Cross company technical coordination (building consensus on the direction for our technical architecture and then herding the cats to make it happen),
  • Standards strategy (which standards do we create/adopt/oppose and when?) and
  • OSS strategy (how to best contribute to and take advantage of the resources on offer).

Rights Not Exercised are Lost – Tibco, BPEL & Rendezvous

Our rights only exist to the extent that we defend them in our daily lives. The right to free speech, for example, would quickly drain away if we didn't frequently exercise it and by so doing kept the knowledge of the rights importance and the mechanisms to protect it alive and well. But too often people believe that the need to defend our rights doesn't apply to them because they are just a single individual. Who cares what a single person does? But when each individual believes their actions don't matter then they significantly reduce the work required by those who would take our rights away.

Continue reading Rights Not Exercised are Lost – Tibco, BPEL &
Rendezvous

Host Routing Multicast Engine (HRME)

I liked university. It gave me time to think about things. It gave me interesting people to talk to. But then I had an idea. It was called the Host Routing Multicast Engine (HRME). The idea was to get computers above the TCP/IP layer (e.g. not IP based multicast, see here for the problems with IP multicast) to join up in a spanning tree and distribute information down the tree. By each machine volunteering to redistribute content to every other machine one could very efficiently distribute large amounts of data. I'm sure this all sounds very familiar but these thoughts occurred to me back in 1994. 56Kb modems were state of the art, e-mail was still mostly 7 bit text, the Internet bubble was just getting started and I smelled money in them 'dar' hills.

Continue reading Host Routing Multicast Engine (HRME)

BPEL, TIBCO and trademarking the English language

Issue 202 in the BPEL TC is a demand from Tibco that the BPEL TC change the word 'rendezvous' that is used as the value of an attribute in the BPEL programming language because Tibco has trademarked the word 'rendezvous'. To be clear, trademarks do not apply to 'descriptive' uses and that is exactly how BPEL uses the term 'rendezvous'. So legally speaking Tibco most likely doesn't have a leg to stand on. I do have sympathy for Tibco because one is required to 'vigorously' enforce a trademark in order to keep it. So to protect their trademark they need to be seen to be defending it, hence issue 202. But now people in the group are scared that Tibco will sue them (or their employer) if we don't change the term. Hopefully the group will stand up for the freedom to use the English language and reject issue 202 on next week's call. An even better outcome would be a change in the law that would make it illegal to get a Trademark on a common English word. The fact that Tibco could trademark the word 'rendezvous' and then try to banish its use from technical efforts is insane.