AML Meeting June 2013 notes

From CIMI
Revision as of 02:08, 18 June 2013 by Admin (Talk | contribs) (Created page with "Have to say something about what an implementation needs to do * ADL round trip - ''ability'' to faithfully represent a designated subset of ADL * Q: Is there any necessary se...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Have to say something about what an implementation needs to do

  • ADL round trip - ability to faithfully represent a designated subset of ADL
  • Q: Is there any necessary serialization format? Should this be ADL?
    • AML Core Zero - ADL subset
      • Test is ability to represent and transfer between implementations / collaboratively define
      • Another test ability to prove that data compatible with models produced by one system is consumable / valid with models produced by another system.
    • AML Extension - superset, capabilities that go beyond ADL

Will provide a library of test artifacts - regression test suite from ADL compiler.

Tasks

  1. Need one ADL to XMI or related conversion to generate test cases
  2. Full compliance statement is target for the final submission
  • Metamodel defined
    • Format? UML?
    • Closeness to ADL/AOM?
    • Documentation?
  • UML Profile
    • UML to DITA transformation exists (partial)
    • Acceleo - MOF to Text generator
  • OCL

AML Metadata

  1. Should metadata be a fourth profile?
  2. Should metadata be included as part of initial submission?

Need to differentiate metadata that is considered part of the artifact from that is a part of a registry. openEHR is based on ISO 13606 and CEN TC 251. CIMI is working on more extended version, will follow the lead of CIMI.

Issue of original language, contributors, keywords, author, etc. Preliminary decision is that metadata section will be a low priority by August deliverable. 13606 will be part of requirements for first submission and will be done time permitting.