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

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…

3 days 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…

3 weeks ago

The Beginning of CVOYA

There’s a unique energy that comes with starting something new — a blend of excitement,…

3 months ago

Enhancements in Graph Model: Dynamic Entities & Full-Text Search

As I continued work on BrainExpanded and its MCP service, I came to realize that…

6 months ago

GraphModel: A .NET Abstraction for Graphs

Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…

7 months ago

Playing with graphs and neo4j

After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…

8 months ago