However, I have not thought a lot about this yet. The editor should be able to store and load domain models from persistent repositories of various kinds. But at first simple filestore save and load will be supported. There will be an inova-plan.xml to go along with this that adds objectives, evaluations, preferences and plans. Their core structure will be the same.
Plans are likely to have as many expansion levels as are in the plan structure.
An example attribute value editor that can be driven from the grammar and lexicon available was created on the TBPM project. A variables field is not needed, it should be assumed that in this view all variables mentioned are declared and made available behind the scenes. This is off by default. If turned on it would bring up an advanced button in the constraints area of the display.