Specification Common Elements Avatar
  1. OMG Specification

Specification Common Elements — Open Issues

  • Acronym: SCE
  • Issues Count: 19
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Issues Descriptions

Remove current vocabulary mechanisms from SCE

  • Key: SCE-37
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    As part of finalizing an minimum viable product for SCE, remove the vocabulary mechanism. There has been much discussion about the topic and the necessity for the capability has been questioned.
    In any case, the current mechanism doesn't work, especially which the proposed change to Semantic Reference.
    We may need to include some sort of extendible enumeration capability at some point. This will be handled in conjunction with review of BKPMN, PPMN, PMN, and SDMN enumeration requirements.

  • Reported: SCE 1.0b1 — Sat, 28 Jan 2023 00:12 GMT
  • Updated: Sat, 28 Jan 2023 00:12 GMT

Update the description of Import in the Spec

  • Key: SCE-36
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    The Import section has some inaccuracies and should be refactored to be a very general mechanism as a foundation for the specs that use SCE. Further import constraints will have to be defined for each language.

  • Reported: SCE 1.0b1 — Fri, 27 Jan 2023 23:57 GMT
  • Updated: Fri, 27 Jan 2023 23:57 GMT

Refactor SCE XSDs based updated method of translating from UML Metamodel Diagrams

  • Key: SCE-35
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    The current SCE XSDs were developed with a faulty translation of UML class relationships to the XSD elements.
    To resolve this issue we need to specify the XSD patterns that correspond to the UML class relationships and then update the XSDs.

  • Reported: SCE 1.0a1 — Tue, 17 Jan 2023 22:55 GMT
  • Updated: Tue, 24 Jan 2023 20:49 GMT

Refactor SDMN XSDs based updated method of translating from UML Metamodel Diagrams

  • Key: SDMN-43
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    The current SDMN XSDs were developed with a faulty translation of UML class relationships to the XSD elements.
    To resolve this issue we need to specify the XSD patterns that correspond to the UML class relationships and then update the XSDs.

  • Reported: SCE 1.0b1 — Tue, 17 Jan 2023 22:56 GMT
  • Updated: Tue, 17 Jan 2023 22:56 GMT

Add Labels for all SDMN Metamodel Relationships

  • Key: SCE-4
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    to be MOF compliance

  • Reported: SCE 1.0b1 — Mon, 18 Jul 2022 19:47 GMT
  • Updated: Tue, 17 Jan 2023 20:15 GMT

Change RelationshipKinds from a Vocabulary to a UML Enumeration

  • Key: SCE-25
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    RelationshipKinds should be well-known set of kinds. These kinds have semantic meaning and have notational impacts. Thus, they should be part of the normative spec through a standard enumeration (or perhaps sub-classes).

  • Reported: SCE 1.0b1 — Tue, 6 Sep 2022 15:37 GMT
  • Updated: Mon, 9 Jan 2023 20:56 GMT

wrong type of element in XSD for ModelArtifact -- should be a ref

  • Key: SCE-34
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    if this is to be the target of using substitutionGroup, then

    <xsd:element name="modelArtifact" type="sce:tModelArtifact" minOccurs="0" maxOccurs="unbounded">

    should be:

    <xsd:element ref="sce:ModelArtifact" minOccurs="0" maxOccurs="unbounded"/>

    the wrong type of element in XSD for ModelArtifact – should be a ref

  • Reported: SCE 1.0b1 — Thu, 29 Dec 2022 03:47 GMT
  • Updated: Thu, 29 Dec 2022 03:47 GMT

suggest KnownColor be renamed tKnownColor

  • Key: SCE-33
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    all types should start with 't'

  • Reported: SCE 1.0b1 — Thu, 29 Dec 2022 03:39 GMT
  • Updated: Thu, 29 Dec 2022 03:39 GMT

suggest AlignmentKind be renamed 'tAlignmentKind'

  • Key: SCE-32
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    all types should start with 't'

  • Reported: SCE 1.0b1 — Thu, 29 Dec 2022 03:36 GMT
  • Updated: Thu, 29 Dec 2022 03:36 GMT

Consider renaming rgb to tRGB

  • Key: SCE-31
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    I would suggest all acronyms be capitalized. All types start with 't'.

  • Reported: SCE 1.0b1 — Thu, 29 Dec 2022 03:33 GMT
  • Updated: Thu, 29 Dec 2022 03:33 GMT

Replace Incorrect Metamodel Figures

  • Key: SCE-28
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    Any metamodel figures that are incorrect, usually because they were placed and then the metamodel changed, should be replaced.
    One example is Figure 11 Annotations, which shows the older version of SCEElement.

  • Reported: SCE 1.0b1 — Fri, 7 Oct 2022 17:25 GMT
  • Updated: Fri, 7 Oct 2022 17:25 GMT

Fix Typos in Spec

  • Key: SCE-27
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    Fix all identified typos in the beta Spec, if they have not been identified in other issues

  • Reported: SCE 1.0b1 — Tue, 4 Oct 2022 18:59 GMT
  • Updated: Tue, 4 Oct 2022 19:00 GMT

Add Notations for Relationship Kinds in SCE

  • Key: SCE-6
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    This will ensure that all downstream languages will use the same notation if they have connectors based on the RelationshipKinds.

  • Reported: SCE 1.0b1 — Wed, 27 Jul 2022 22:27 GMT
  • Updated: Tue, 6 Sep 2022 15:38 GMT

SCE Relationship Kinds Should Cover All BPM+ Relationships

  • Key: SCE-22
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    Basically all lines between model elements in all the BPM+ models (BPMN, CMMN, DMN, SDMN, BKPMN, Parties, and PPMN) should be (theoretically maybe) derived from one of the SCE Relationship Kinds.
    And if we define the basic notation for each of these relationships, then all subsequent models will provide consistent relationship notations.

  • Reported: SCE 1.0b1 — Mon, 8 Aug 2022 20:20 GMT
  • Updated: Tue, 6 Sep 2022 15:38 GMT

Add Mapping of SCE Term functions to MVF in Spec

  • Key: SCE-23
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    The changes to the current SCEVocabulary models should be mapped to MVF.

  • Reported: SCE 1.0b1 — Tue, 30 Aug 2022 20:13 GMT
  • Updated: Tue, 30 Aug 2022 20:13 GMT

Modify the Semantic Reference Capability in SCE

  • Key: SCE-7
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    More details to follow

  • Reported: SCE 1.0b1 — Wed, 25 May 2022 23:33 GMT
  • Updated: Thu, 28 Jul 2022 21:14 GMT

Add Labels for all SCE Metamodel Relationships

  • Key: SCE-3
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    to be MOF compliant

  • Reported: SCE 1.0b1 — Mon, 18 Jul 2022 19:46 GMT
  • Updated: Mon, 18 Jul 2022 19:46 GMT

Move the default expression and default type properties from SDMN to SCE

  • Key: SCE-2
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    They are optional properties and can be used by multiple languages, including the original BPM+ languages.

  • Reported: SCE 1.0b1 — Tue, 5 Jul 2022 21:45 GMT
  • Updated: Tue, 5 Jul 2022 21:45 GMT

Adjust the structural elements of SCE such that they are backwards compatible with BPMN, CMMN, and DMN.

  • Key: SCE-1
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    This will probably affect the packaging structures more than anything.
    If done properly, it may be possible for current BPM+ vendors to overlay those models on top of SCE.
    Falko Menge has already done some testing of the BPMN schema utilizing SCE. There are some breakages that may be fixed through SCE adjustments.
    We may need to reconsider the PPMN requirements for Instance packages as part of SCE (and move to PPMN directly).

  • Reported: SCE 1.0b1 — Tue, 5 Jul 2022 21:41 GMT
  • Updated: Tue, 5 Jul 2022 21:41 GMT