1. OMG Mailing List
  2. Structured Asurance Case Metamodel (SACM) 2.1 RTF

Open Issues

  • Issues not resolved
  • Name: sacm2-rtf
  • Issues Count: 54

Issues Summary

Key Issue Reported Fixed Disposition Status
SACM21-17 Incorrect description of package SACM 2.0 open
SACM21-16 Invalid URL SACM 2.0 open
SACM21-15 Association is inconsistent with semantics SACM 2.0 open
SACM21-14 Broken Link SACM 2.0 open
SACM21-29 Duplicative paragraphs? SACM 2.0 open
SACM21-24 Punctuation and spacing errors SACM 2.0 open
SACM21-23 Spelling mistake in 9.1 SACM 2.0 open
SACM21-19 Missing role discription for terminology model SACM 2.0 open
SACM21-22 Spelling mistake in 2.5 SACM 2.0 open
SACM21-21 Mistake in element name in 2.3 text SACM 2.0 open
SACM21-20 Concepts in SACM 2 have no direct graphical notation SACM 2.0 open
SACM21-7 Need more consistency in packages, interfaces and binding SACM 2.0b2 open
SACM21-6 SACM needs support for Internationalization SACM 2.0b2 open
SACM21-5 Simplification of elements contained in packages SACM 2.0b2 open
SACM21-4 Need to simplify internationalization support in Expressions. SACM 2.0b2 open
SACM21-3 Alow AssertedRelationship to express if it is a counter relationship SACM 2.0b2 open
SACM21-2 Simplify ArtifactElement and its sub-types SACM 2.0b2 open
SACM21-1 Align with American English to support use of SACM by The Open Group SACM 2.0b2 open
SACM21-31 B and A or A and B SACM 2.0 open
SACM21-30 Replace "that" with "whether"? SACM 2.0 open
SACM21-25 Spelling mistake in 11.8 SACM 2.0 open
SACM21-18 Misleading section title for 1.3 Artifact SACM 2.0 open
SACM21-58 In 11.13 the +target should have multiplicity of 1 SACM 2.0 open
SACM21-13 Address missing elements of first 12 issues and address style consistency SACM 2.0b2 open
SACM21-12 Need for the ability to group SACMElements SACM 2.0b2 open
SACM21-11 Better support for patterns is needed SACM 2.0b2 open
SACM21-10 Simplification of ArtifactAssetRelationship SACM 2.0b2 open
SACM21-9 Need to simplify the citation classes of SACM SACM 2.0b2 open
SACM21-8 Elements in all parts of SACM need to be considered as artifacts and appropriate context and support relationships captured. SACM 2.0b2 open
SACM21-55 Unnecessary constraint statement in 11.11 SACM 2.0 open
SACM21-107 Graphical notation for SACM Argumentation concepts SACM 2.0 open
SACM21-66 Confirm URI on title page SACM 2.0 open
SACM21-62 Outdated constraints for class Claim SACM 2.0 open
SACM21-64 SACM21-14 and SACM21-16 bad urls SACM 2.0 open
SACM21-68 Typo on pdf pg 10 SACM 2.0 open
SACM21-67 http -> https SACM 2.0 open
SACM21-65 SACM21-20 the changes are inconsistent with pdf SACM 2.0 open
SACM21-75 Date or date in 12.9 SACM 2.0 open
SACM21-74 Date or date in 12.7 SACM 2.0 open
SACM21-73 text and figure mismatch ArgumentPackage<-->ArgumentPackageInterface SACM 2.0 open
SACM21-72 newline SACM 2.0 open
SACM21-71 multiplicity in figure and text do not match SACM 2.0 open
SACM21-70 trailing bullet SACM 2.0 open
SACM21-69 SPMS version SACM 2.0 open
SACM21-109 New notations for asserted context and asserted artifact context SACM 2.0 open
SACM21-80 SACM21-1 through 13 were unnecessary SACM 2.0 open
SACM21-79 Issue 55 material includes Issue 30 changes SACM 2.0 open
SACM21-78 multiplicity change missing figures SACM 2.0 open
SACM21-77 Missing Concrete Syntax in 11.10 SACM 2.0 open
SACM21-76 Date or date in 12.11 SACM 2.0 open
SACM21-83 Why MOF 2.0 SACM 2.0 open
SACM21-82 PNG images SACM 2.0 open
SACM21-81 !!.14 or 11.14 SACM 2.0 open
SACM21-84 http -> https in MOF file SACM 2.0 open

Issues Descriptions

Incorrect description of package

  • Key: SACM21-17
  • Status: open  
  • Source: TGR Safety Management Ltd ( Timothy G Rowe)
  • Summary:

    The specification relates to ArtifactPackage, but the description of the package describes it as ArgumentPackage.

  • Reported: SACM 2.0 — Tue, 12 Jun 2018 01:56 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:


Association is inconsistent with semantics

  • Key: SACM21-15
  • Status: open  
  • Source: gmail.com ( Timothy Rowe)
  • Summary:

    The association `value` is shown as LangString[1..*], but the semantics describe it as a list of ExpressionLangString, not LangString.

  • Reported: SACM 2.0 — Sun, 10 Jun 2018 23:09 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Broken Link

  • Key: SACM21-14
  • Status: open   Implementation work Blocked
  • Source: gmail.com ( Timothy Rowe)
  • Summary:

    The link "http://www.goalstructuringnotation.info/sacm-examples
    Structured" leads to a "Site Unavailable" page.

  • Reported: SACM 2.0 — Fri, 8 Jun 2018 03:54 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Duplicative paragraphs?

  • Key: SACM21-29
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    p33: the last two paragraphs seem to be the same (from word to word) except the last words: "AssertedContext" and "ArtifactReference". I have no consistent understanding yet but it seems that the second paragraph should be removed (or something else was intended to be written there).

  • Reported: SACM 2.0 — Sun, 17 Feb 2019 04:02 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Punctuation and spacing errors

  • Key: SACM21-24
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In section 1.4 there is a missing "," after the word "Basically" at the beginning of the second sentence in the second paragraph. In section 9.2 "top level" should be hyphenated in the second sentence of the first paragraph. In the last sentence of section 11.1 the "." at the end is in the wrong place.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 19:23 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Spelling mistake in 9.1

  • Key: SACM21-23
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The word contained is spelled as"containined"

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 19:06 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Missing role discription for terminology model


Spelling mistake in 2.5

  • Key: SACM21-22
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Terminology misspelled as "Termonology" in Section 2.5

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:58 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Mistake in element name in 2.3 text

  • Key: SACM21-21
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Mistake in element name – remove “Model” from ArtifactModel::ArtifactPackage

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:56 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Concepts in SACM 2 have no direct graphical notation

  • Key: SACM21-20
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Need a concrete syntax for the Argumentation metamodel that can represent the semantic definitions of the elements for semantic transparency, easing the burden of learning the elements and allowing them to be perceived directly from the notation.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:54 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Need more consistency in packages, interfaces and binding

  • Key: SACM21-7
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    There are unnecessary differences between the Assurance Case, Terminology, Argument, and Artifact package definitions, interfaces, and bindings.

  • Reported: SACM 2.0b2 — Thu, 24 Aug 2017 20:03 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

SACM needs support for Internationalization


Simplification of elements contained in packages


Need to simplify internationalization support in Expressions.

  • Key: SACM21-4
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    There is currently no direct mechanism to support internationalization in SACM content.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:16 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Alow AssertedRelationship to express if it is a counter relationship

  • Key: SACM21-3
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In Argumentation package, AssertedRelationship should directly express if it is a counter relationship.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:18 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Simplify ArtifactElement and its sub-types

  • Key: SACM21-2
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    In SACM, all elements in the Argumentation package, Artifact package, Terminology package, and AssuranceCase package are considered to be Artifacts.

    Consequently ArtifactElement needs to be moved to the Base classes and be a direct sub-type of ModelElement. All elements in other packages then will sub-type ArtifactElement.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:19 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Align with American English to support use of SACM by The Open Group

  • Key: SACM21-1
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Use “artifact” instead of “artefact” is needed to make incorporation of SACM into The Open Group standards more practical.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:21 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

B and A or A and B

  • Key: SACM21-31
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    p39:Last sentences of 11.13 and 11.14: Is A and B intentionally exchange in "the truth of" parts of the two sentences?

    11.13: "An inference asserted between two claims (A � the source � and B � the target) denotes that the truth of Claim A is said to infer the truth of Claim B."

    11.14: "An AssertedInference between two claims (A � the source � and B � the target) denotes that the truth of Claim B is said to infer the truth of Claim A."

    I would expect that the inference of truth comes from the source and is asserted for the target so the other way than 11.14 Semantics part defines. [Remark: I am not a native English speaker so it might be strange just for me why the "said to infer" expression is used instead of "inferred from". I interpret "The truth of X is said to infer the truth of Y." as "Truth of Y can be inferred from the truth of X." or "The truth of X logically necessitates the truth of Y."- is it correct?]

  • Reported: SACM 2.0 — Sun, 17 Feb 2019 04:03 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Replace "that" with "whether"?

  • Key: SACM21-30
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    p38, 11.13, Attributes: If "isCounter" seems to be set to false then stating that "a flag indicating that the AssertedRelationship counters its declared purposes" seems to be controversial, although I understand that the "false" is a default value. I think, adding "that whether the AssertedRelationship counters" is more clear. E.g. in 11.10 at a similar case, it writes "indicating the state ..." which was more clear.

  • Reported: SACM 2.0 — Sun, 17 Feb 2019 04:03 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Spelling mistake in 11.8

  • Key: SACM21-25
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The section title "Literals" is misspelled.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 19:26 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Misleading section title for 1.3 Artifact

  • Key: SACM21-18
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The Artifact title is misleading label for this portion of the scope description, this section is actually is about Evidence.

  • Reported: SACM 2.0 — Sat, 16 Feb 2019 18:30 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

In 11.13 the +target should have multiplicity of 1

  • Key: SACM21-58
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The multiplicity of +target should be 1 (target:ArgumentAsset[1]).

  • Reported: SACM 2.0 — Mon, 18 Feb 2019 03:18 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Address missing elements of first 12 issues and address style consistency

  • Key: SACM21-13
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    There are several areas where the work packages for addressing issues 1, 2, 3, 5, 6, 7, 9, 11, or 12 missed changes, additions, and deletions to support internationalization and package simplification. Additionally, there are several style issues in the text that need to be made consistent.

  • Reported: SACM 2.0b2 — Fri, 25 Aug 2017 18:13 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Need for the ability to group SACMElements

  • Key: SACM21-12
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    To support multiple stakeholder views and purposes a mechanism for associating SACMElements is needed.

  • Reported: SACM 2.0b2 — Tue, 22 Aug 2017 15:44 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Better support for patterns is needed

  • Key: SACM21-11
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The ability to create patterns (e.g. AssuranceCase patterns, ArgumentPackage patterns, etc) that contain only abstract SACMElements is needed and the patterns should be re-usable.

  • Reported: SACM 2.0b2 — Tue, 22 Aug 2017 15:42 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Simplification of ArtifactAssetRelationship

  • Key: SACM21-10
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    ArtifactAssetRelationship can be simplified by removing all its sub-classes. The purpose of an ArtifactAssetRelationship can then be recorded by the property +property:Property in the ArtifactAsset class.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:19 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Need to simplify the citation classes of SACM

  • Key: SACM21-9
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    Citations can be simplified by removing them from Argumentataion, Artifact and Terminology classes and replacing them with +isCitation and +citedElement properties in SACMElement in the Base classes.

  • Reported: SACM 2.0b2 — Thu, 3 Aug 2017 19:13 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Elements in all parts of SACM need to be considered as artifacts and appropriate context and support relationships captured.

  • Key: SACM21-8
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    If all elements in Argumentation, Terminology, Artifact and AssuranceCase can be considered as artifacts the assertion that one or more artifact provide context for another artifact; and the assertion that one or more artifact support another artifact needs to be captured.

  • Reported: SACM 2.0b2 — Tue, 22 Aug 2017 15:41 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Unnecessary constraint statement in 11.11

  • Key: SACM21-55
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The constraint statement in 11.11 is unnecessary since there is no longer an assumed nor a toBeSupported attribute in the standard

  • Reported: SACM 2.0 — Mon, 18 Feb 2019 02:59 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:



Outdated constraints for class Claim

  • Key: SACM21-62
  • Status: open  
  • Source: LogicalHacking.com ( Achim D. Brucker)
  • Summary:

    The constraint section of the class Claims revers to two attributes ("assumed" and "toBeSupported") that are not part of the SACM 2.0 metamodel (they are replaced by the attribute "assertionDeclaration" of type "AssertionDeclaration).

    Proposed fix:

    Remove the constraint section. It is no longer required, as the "exclusive or"-constraint is already enforced by AssertionDeclaration being an enumeration.

  • Reported: SACM 2.0 — Tue, 19 Feb 2019 19:30 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

SACM21-14 and SACM21-16 bad urls

  • Key: SACM21-64
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    RB1 – Two of the issues, SACM21-14 and SACM21-16, referred to bad urls and were marked as “Closed; No Change,” but the resolution was not specified – what was done to resolve these two issues?

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:20 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Typo on pdf pg 10

  • Key: SACM21-68
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS3 - Typo on pdf pg 10: Issues: hhttp in URI -> https

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:22 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

http -> https

  • Key: SACM21-67
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS2 - http -> https throughout for omg.org, please check other sites and changeover as possible for futureproofing ( on omg.org: pdf pgs 1, 3, 4, 9, 10, 16 and pdf pgs 16, 65, 67).

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:22 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

SACM21-20 the changes are inconsistent with pdf

  • Key: SACM21-65
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    RB2 – For SACM21-20 the changes are inconsistent with the changes specified in the associated PDF file. In Concrete Syntax.pdf, Figure 11.2 contains the title "Concrete Syntax for ArguementPackage" whereas "ArgumentPackage" is used in the actual text. The misspelled version is still present in the table of contents.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:20 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Date or date in 12.9

  • Key: SACM21-75
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS10 – In 12.9 Event, under Attributes, date:Date[0..1] does not match naming of attribute in Figure 12.1, which is occurence:date[0..1]

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:28 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Date or date in 12.7

  • Key: SACM21-74
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS9 - In 12.7 Artifact, under Attributes, date:Date[0..1] does not match naming of type in Figure 12.1, which is date:date[0..1]

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:27 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

text and figure mismatch ArgumentPackage<-->ArgumentPackageInterface

  • Key: SACM21-73
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS8 – In 11.5 ArgumentPackageBinding, under Associations, participantPackage is listed as ArgumentPackageInterface, should be ArgumentPackage to match Figure 11.1.  Change type, or diagram.  The analogous Sec 12.4 ArtifactPackageBinding indicates the diagram here is likely correct.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:26 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

newline

  • Key: SACM21-72
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS7 – In 8.6 ModelElement (abstract), under Associations, need a newline between implementationConstraint and description.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:24 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

multiplicity in figure and text do not match

  • Key: SACM21-71
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS6 – In 8.2 SACMElement (abstract), under Attributes, isCitation and isAbstract do not match multiplicity in Figure 8.1

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:24 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

trailing bullet

  • Key: SACM21-70
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS5 - In 6.2 Acknowledgements, there is an extra trailing bullet.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:23 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

SPMS version

  • Key: SACM21-69
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS4 - In 3.2 Non-normative References, SPMS is at 1.2, update doc number to formal/17-11-01.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:23 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

New notations for asserted context and asserted artifact context

  • Key: SACM21-109
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    The notation previously selected for these concepts could cause confusion when viewed by those familiar with UML notations or when viewing UML notations in proximity to these SACM concepts.

  • Reported: SACM 2.0 — Wed, 20 Mar 2019 20:54 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

SACM21-1 through 13 were unnecessary

  • Key: SACM21-80
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS15 - SACM21-1 through 13 were unnecessary to add to archive and muddied the waters.  One for Mariano?

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:31 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

Issue 55 material includes Issue 30 changes

  • Key: SACM21-79
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS14 - Issue 55 (ptc-19-02-33/SACM21-55/11.11-deletion.pdf) includes editorial ‘that’ to ‘whether’ that is listed in changebar as Issue 30.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:31 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

multiplicity change missing figures

  • Key: SACM21-78
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS13 - Issue 58 (ptc-19-02-33/SACM21-58/11.13 multiplicity.pdf) does not include the graphic for Figure 7.2 on pg 12 and changes on pg 37 11.14 marked as Issue 31, 20 - should not have been in this file.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:30 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Missing Concrete Syntax in 11.10

  • Key: SACM21-77
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS12 - Issue 20 (ptc-19-02-33/SACM21-20/Concrete Syntax.pdf) does not include the Concrete Syntax added to Section 11.10 Assertion (abstract) and includes an editorial change (‘that’ to ‘whether’) on page 38 Sec 11.13 under Attributes that is not in the changebar or clean documents for issue 20. 

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:29 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Date or date in 12.11

  • Key: SACM21-76
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS11 – In 12.11 Activity, under Attributes, startDate:Date[0..1] does not match naming of type in Figure 12.1, which is startDate:date[0..1] and under Attributes, endDate:Date[0..1] does not match naming of type in Figure 12.1, which is endDate:date[0..1]

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:28 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

Why MOF 2.0

  • Key: SACM21-83
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS19 - Why MOF 2.0, and not 2.5.1?  If no technical reason, update to 2.5.1.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:33 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

PNG images

  • Key: SACM21-82
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS17 - The PNG images are less than optimal, and fuzzy throughout Section 11 and Annex C in both clean and changebar docs.  SVG preferred in general.  Can these be regenerated appropriately?

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:33 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT
  • Attachments:

!!.14 or 11.14

  • Key: SACM21-81
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS16 - Filename for SACM21-31/!!.14 - A2B.pdf  - I assume this should be 11.14… that’s going to wreak havoc with some filesystems.

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:32 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT

http -> https in MOF file

  • Key: SACM21-84
  • Status: open  
  • Source: MITRE ( Bob Martin)
  • Summary:

    JS18 - http -> https throughout for omg.org (all URIs)

  • Reported: SACM 2.0 — Mon, 18 Mar 2019 15:34 GMT
  • Updated: Mon, 1 Apr 2019 17:38 GMT