I absolutely agree…

… with Steve‘s comments about how the W3C TAG shouldn’t mandate a direct correlation between the wsa:To property and the underlying transport/application protocol-specific address. This would be similar to saying that every time I want to pay with my credit card by giving my credit card number, I have to tell the service provider how to communicate with my credit card company. I see SOAP messages travelling over arbitrary transport/application protocols (perhaps even as part of a single message exchange).

I want to build applications using SOAP without having to care about the semantics of what’s underneath. I perhaps care about the quality of service that the underlying protocols provide me (e.g. UDP vs TCP vs HTTP etc). However, such decisions may not have to be made until after I have developed my application.

Recent Posts

The boat is in the water: Spring Voyage is open source

Today I'm pushing Spring Voyage out of the harbor. You can track its journey on…

5 days ago

My Coding Agent Needed Its Own GitHub Identity

In my last post, I wrote that "the typing of code was parallelized and delegated.…

1 month ago

Rebuilding My AI Team in Twelve Days — And Why

In February, I wrote about the small team I'd stood up instead of hiring humans:…

2 months ago

How I Built My Own Team of AI Developers

Assembling a dream team without a single hire I've been making great progress on CVOYA's…

3 months ago

Reflecting on 2025: Building CVOYA’s Future with AI Coding Agents

As 2025 is now behind us, I wanted to share a few reflections from my…

5 months ago

DIY smart home accessory – It all started with a question to ChatGPT

Few months ago, we bought a sculpture from a local art fair for our Palm…

6 months ago