Tim Ewald on MEST

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!

Recent Posts

BrainExpanded – The Timeline

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

3 days ago

BrainExpanded – Introduction

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

3 days ago

Digital twin follow up

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

2 weeks ago

Digital Twin (my playground)

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

10 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

AI is enhancing me

AI as an enhancer of human abilities.

1 year ago