We can just tag what is there now and call that Release 1, as a baselin; this involves a) some technical aspects and b) doing the appropriate things on Jira to leave the correct 'paper trail'
10min
AM: I propose to have ADL / AOM finally ready for 2.x release in the next 2 weeks
there is a need for a redefined node to replace its parent node without the parent still being available. I spent a couple of weeks looking at this and determined that we probably need a new keyword or marker that means 'replace' for a C_OBJECT node, which prevents the parent node from still being available.
there is an ongoing discussion about the 'rules' part of the archetype, as per the recent wiki page. I have decided it is better to just complete the specification in the original form - re-using the new 'rules' BASE spec we agreed in Stockholm (you have seen the draft). I don't think this is the final answer, but at least it is based on separated rules; if no-one uses it - good, it gives us the time to design a new approach for representing cross-dependency and get it added via proper PRs/CRs
I don't think this needs much discussion now - probably just SEC agreement in principle that we go ahead with the rules bit, declare Release-2.0.x (I think it will be 6)
10min
CDS: The GDL spec needs a bit of rewriting not in spirit, but in form, as agreed in Stockholm
replace existing UML with UML model of BASE rules (by inclusion)Â extra when/then rules as per GDL. This should be done in MagicDraw so that we take advantage of the same extraction approach as with the other specs.
There are some formatting and heading numbering anomalies that I think need to be addressed.
currently the syntax is inlined, but with Asciidoctor, we can actually do an include of the real syntax (where is it?) - I can show how to do this.
I am happy to work on this with Rong, or do most of it, or help someone else do most of it (i.e. just help with MagicDraw and Asciidoctor specifics) - up to the SEC to decide.