SCE 1.0b2 FTF Avatar
  1. OMG Issue

SCE — Some SCE Elements are concrete instead of abstract

  • Key: SCE-103
  • Status: closed  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    During resolutions of SCE-7 and SCE-96, the three elements RootElement, KindSet, and Kind have been accidentally set as concrete but should have been abstract. In general, all SCE elements should be abstract and then specialized by concrete elements defined by the languages that are based on SCE. Some exceptions to this include concrete DI elements and the Model Artifacts (e.g., Group), which can be directly used by other languages without specializations. But that is not the case for the three classes mentioned before.

    In addition, the XSD complex types tModelArtifact, tBaseElement, tElementType, tTypedElement, and tAnnotation are not abstract although their corresponding element definitions and metamodel classes are abstract.

  • Reported: SDMN 1.0b1 — Mon, 29 Jan 2024 20:43 GMT
  • Disposition: Resolved — SCE 1.0b2
  • Disposition Summary:

    Mark abstract elements as such

    During some of the other issue resolutions, three elements, RootElement, KindSet, and Kind are set as concrete and should be abstract. In general, all SCE elements should be abstract and then specialized by concrete elements defined by the languages that are based on SCE. Some exceptions to this include concrete DI elements and the Model Artifacts (e.g., Group), which can be directly used by other languages without specializations.

    In addition, the XSD complex types tModelArtifact, tBaseElement, tElementType, tTypedElement, and tAnnotation are made abstract in correspondence to their already abstract element definitions and metamodel classes.

    sce:tModel and scedi:diagramElement are annotated with explanations why their complex types are not abstract or completely absent.

  • Updated: Mon, 16 Sep 2024 14:12 GMT
  • Attachments: