For starters, we have the Domain, Class and a first stab at the Type (datatype) subsystems. The State Model subsystem is coming shortly (we've got a good first draft, but it's not quite ready yet). After that, the Action Model subsystem will follow and then some serious work on domain bridges. Object Population will emerge (we have a good initial draft, again not ready yet) somewhere along the way. There is a long road ahead of us, but hopefully this will keep you mildly entertained for a while.
On the right is a link to a Google spreadsheet detailing the current state of the metamodel API. There are two tabs at the bottom of this spreadsheet to categorize commands and queries. A Postgresql schema has been created for the metamodels along with plpgsql code to implement the API. Scroll down for a link to the schema and code and a more detailed description.
The state model Polymorphism Subsystem is ready for download. In a reflexive twist, much intricate generalization was required to crack this nut. This is the final portion of the state model metamodel. One step closer to action language!
Diagram PDF / Omnigraffle
Defines both normal (monomorphic) and polymorphic events as well as event and state signatures.
The first (of at least two) State Model Subsystem's is ready for your perusal.
Diagram PDF / Omnigraffle
Defines State Models, Events, Transitions, Assigners and other fundamental state model componenets. Does not address polymorphism, parameters and event signatures. These will be coming in the very next subsystem update.
Here is an overview showing how all the class metamodel subsystems are interconnected.
