-
Key: SCE-85
-
Status: closed
-
Source: BPM Advantage Consulting ( Dr. Stephen White)
-
Summary:
The export of BPM+ languages is centered around the SCEModel element. This is the base class for all model elements. Other packages, based on SCEPackage, can be within the SCEModel, but they would not have a separate exporter or exporter version. Currently, all sub-packages could be assigned separate version, but this does not make sense.
-
Reported: SCE 1.0b1 — Mon, 8 Jan 2024 19:08 GMT
-
Disposition: Resolved — SCE 1.0b2
-
Disposition Summary:
Move exporter and exporterVersion to the SCEModel class
The export of BPM+ languages is centered around the SCEModel element. This is the base class for all model elements. Other packages, based on SCEPackage, can be within the SCEModel, but they would not have a separate exporter or exporter version. Currently, all sub-packages could be assigned separate version, but this does not make sense.
Thus, exporter and exporter version should be moved to the SCEModel Class. -
Updated: Mon, 16 Sep 2024 14:12 GMT
-
Attachments:
- Figure 10 - SCEInstances MM V3.svg 286 kB (image/svg+xml)
- Figure 2 - SCE High-Level Elements v6.svg 590 kB (image/svg+xml)
- Figure 6 - The SCEPackage Metamodel V2.svg 227 kB (image/svg+xml)
- Figure 7 - SCEModel MM V4.svg 528 kB (image/svg+xml)
SCE — Exporter information is located in the wrong class
- Key: SCE-85
- OMG Task Force: Specification Common Elements (SCE) 1.0 FTF