|
|
|
|
|
|
by parasubvert
3492 days ago
|
|
|
I tend to agree with you on this, my focus has been on the application of declarative Hierarchical FSMs, Behaviour Trees, and/or Hierarchical Task Networks (using automated planning) as a way of describing FSMs declaratively and yet handling the state explosion problem. The intent is to enabling better integration and interoperability on the Web - basically, getting rid of Twitter, Facebook, etc. centralized monopolies of "write" functionality on the Web. ("Read" functionality, i.e. web crawling / HTTP GET / Google is also monopolized but that's less due to architectural problems and more economic) I have given a couple of keynotes on this topic at the W3C and RESTfest over the years, but just haven't done a lot of the grunt work since I have a day job. See - http://www.slideshare.net/StuC/ill-see-you-on-the-write-side... Also - http://www.slideshare.net/StuC/linking-data-and-actions-on-t... And per your point about how you need serialized data notation + FSMs, see
http://web.archive.org/web/20160410102032/http://www.stuchar... I have felt this train of thought could be useful for a general purpose approach to software engineering beyond distributed systems interop. Unfortunately this has been a hobby horse of mine for about 10 years that I don't have a lot of time to dedicate to.... |
|
|
> I have felt this train of thought could be useful for a general purpose approach to software engineering beyond distributed systems interop
One of the best articles I've read in recent years on the topic is 'On the Industrial Adoption of Model Driven Engineering. Is your company ready for MDE?': http://www.uajournals.com/ijisebc/journal/1/4.pdf
> Unfortunately this has been a hobby horse of mine for about 10 years that I don't have a lot of time to dedicate to....
It's a fun horse to ride if not a bit of a wild and tiring.