| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| SPMS15-2 | Clarify ability to use KerML elements | SPMS 1.4b1 | open | |||
| SPMS15-1 | Add KerML support | SPMS 1.4b1 | open | |||
| SPMS15-4 | Editorial formatting / layout issues | SPMS 1.4b1 | open |
KerML is bridged to MOF so that KerML (and by extension SysML 2.0) elements can be used anywhere an MOF Element can be used.
It may be useful to highlight this in the text as a use case.
SPMS has a general connector to other specification elements by allowing any MOF-derived element to be part of an SPMS instance.
Request is to allow this connection to be to a MOF derived or a KerML derived element. If KerML is already technically allowable through a MOF avenue, then update text and possibly graphics to reflect this.
This is not a backwards compatibility breaking feature, and therefore does not require a 2.0 workflow.
None of the below change existing technical content or words. Solely formatting / layout errors.
Section 4:
Item 4.2 on Page 11 which appears to have a break in the middle of a list (see pg 12, the list continues), and then Page 15 is (unintentionally?) blank. I can’t actually remember the rules for when something is left intentionally blank, but IIRC it’s only for even pages, so new major sections / chapters start on an odd page #. Fixing page 11 will bump 15 back to 14, which then might get the intentional label. Don’t know what it affect as far as intentional blank pages after that. 
(But see next item, it may be the other page correction that gets everything in line.)
Section 8.4:
There’s a column shift in a table that spans between pages 21 and 22:
Is:
Associations
foundVia : SPMS::Formalisms::FormalizedDefinition [*]
A reference to the formal definition used for this particular observation.
Should be:
Associations
foundVia : SPMS::Formalisms::FormalizedDefinition [*] A reference to the formal definition used for this particular observation.
That would eliminate pg 22 if that line bounces up to pg 21. (That may be what re-corrects any later intentional blank page labels after the above change to pg 11/12 - they all seem to be correct after this.)
Section 11.3.3:
Figure 9 on page 35 is rendered strangely. Could be a Word -> PDF production error. Figure in original SVG file renders correctly in other tools. Could be a layers issue though, may need to be re-exported?
Section 11.4
Associations table has borders. It should not.