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

BrainExpanded – Copilot

Happy New Year everyone! I was planning for my next BrainExpanded post to be a…

3 weeks ago

BrainExpanded – The Timeline

See "BrainExpanded - Introduction" for context on this post. Notes and links Over the years,…

1 month ago

BrainExpanded – Introduction

This is the first post, in what I think is going to be a series,…

1 month ago

Digital twin follow up

Back in February, I shared the results of some initial experimentation with a digital twin.…

1 month ago

Digital Twin (my playground)

I am embarking on a side project that involves memory and multimodal understanding for an…

11 months ago

“This is exactly what LLMs are made for”

I was in Toronto, Canada. I'm on the flight back home now. The trip was…

1 year ago