Tim has some comments on MEST. While I said that I am not going to try and describe MEST again until we have a paper written, I think I need to make a clarification (some more details can be found as a comment on Tim‘s post).
As I’ve said previously, MEST is not proposing something that we are not already doing. As Tim says, MEST is already omni-present. We were just trying to define the architectural style called “service-orientation” in terms of architectural elements (data, connectors, components) and then compare it with “resource-orientation” which is represented by REST.
I can’t emphasise enough that the last thing we have been suggesting is that there is only a single WSDL operation defined for every Web Service called ‘ProcessMessage’. Obviously it’s been our fault for not making this crystal clear! Sorry!
There’s a unique energy that comes with starting something new — a blend of excitement,…
As I continued work on BrainExpanded and its MCP service, I came to realize that…
Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…
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…