… 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.
After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…
Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…
As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…
Imagine a world where your memory is enhanced by a team of intelligent agents, working…
As part of the BrainExpanded project, I’m building an iOS app that lets users easily…
Artificial Intelligence (AI) has rapidly evolved over the past few decades, becoming an integral part…