Archetype Modeling Language Avatar
  1. OMG Specification

Archetype Modeling Language — Open Issues

  • Acronym: AML
  • Issues Count: 8
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Normative References incomplete

  • Key: AML_-8
  • Status: open  
  • Source: 88solutions ( Manfred Koethe)
  • Summary:

    The list of normative references in clause 3 of the AML Beta-1 document is incomplete. In particular a reference to MOF is missing.

  • Reported: AML 1.0b1 — Wed, 3 May 2017 17:14 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT

Conformance clause has insufficient information

  • Key: AML_-9
  • Status: open  
  • Source: 88solutions ( Manfred Koethe)
  • Summary:

    The Conformance clause (clause 2) in the AML Beta-1 document has insufficient information. It explains only the relationship between the three profiles, but does not make a statement what has to be implemented by a tool to be in conformance with the AML specification, or a controlled subset if it, if this is intended to be allowed.

  • Reported: AML 1.0b1 — Wed, 3 May 2017 17:18 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT

The description of SpecificationDocument.mdzip is not correct. It should list its dependencies

  • Key: AML_-3
  • Legacy Issue Number: 19804
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The description of SpecificationDocument.mdzip is not correct. It should list its dependencies

  • Reported: AML 1.0b1 — Mon, 15 Jun 2015 04:00 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT

MOF metamodel not provided as normative file

  • Key: AML_-4
  • Legacy Issue Number: 19803
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    P94 refers to a MOF metamodel “An AOM Model is an instance of an AOM 2.0 MOF Meta-model. “ but this is not provided as part of the normative files. Even the informative files contain only proprietary ecore metamodel. I believe Eclipse can make use of EMOF which is very close to ecore and is an OMG standard.

    Given that the QVT files are normative, there should be normative definitions for the source and target for the transformations

  • Reported: AML 1.0b1 — Wed, 1 Jul 2015 04:00 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT

non-normative instead of normative inventory entry

  • Key: AML_-5
  • Legacy Issue Number: 19802
  • Status: open  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    This entry in the inventory (health/15-05-02) should instead be a
    non-normative section in the specification pointing interested parties at
    the AOM Schemas on the OpenEHR site:

    Doc Number: Health/2015-05-01
    Filename: EclipseFiles.zip
    Description: Contains the AOM Schemas for rendering the AOM models in XML
    form, and the corresponding eclipse ecore and model generator models.
    Normative?: No
    URL: http://schemas.openehr.org/v1

  • Reported: AML 1.0b1 — Mon, 15 Jun 2015 04:00 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT

Informative clauses are not marked clearly as informative

  • Key: AML_-7
  • Status: open  
  • Source: 88solutions ( Manfred Koethe)
  • Summary:

    The specification document contains a substantial amount of informative background and explanatory material. Since those clauses tend to reference external standards and specifications, like CIME, those clauses must be marked "informative" to state the non-binding nature of the content and references.

  • Reported: AML 1.0b1 — Wed, 3 May 2017 17:10 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT

The “QVT” file health/2015-04-05 is actually an HTML file

  • Key: AML_-1
  • Legacy Issue Number: 19806
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The “QVT” file health/2015-04-05 is actually an HTML file. In fact it is a copy of HTML page from a github site. Unlike the other qvto files which are textual QVT files as I’d expect.

  • Reported: AML 1.0b1 — Mon, 15 Jun 2015 04:00 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT
  • Attachments:

specification is not related to so should not be dependent on NIEM

  • Key: AML_-2
  • Legacy Issue Number: 19805
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    This specification is not related to so should not be dependent on NIEM, merely because an old version of the latter happened to define some useful primitive types

  • Reported: AML 1.0b1 — Mon, 15 Jun 2015 04:00 GMT
  • Updated: Fri, 12 May 2017 00:01 GMT