Different Meanings of Different Variants/Versions of a Model Elements Need to be Labeled, e.g. for Claims
Legacy Issue Number: 16511
Source: MITRE ( Samuel Redwine)
Claims and other items can have versions that simultaneously exist but have different meanings. For example, what a Claim might represent includes:
Planned values to be achieved
Supported (established, justified) values
Two or more of these can be relevant at the same time.
A suggestion has been made that SBVR be used (within associated properties?) to make this distinction. This would require that SBVR be available for these contents. Use of a TaggedValue is another possibility. Regardless of what mechanism is used, some standardization should be included for the key meanings.
Placing this distinction within the contents of claim true-false statement might be more awkward and not make it as readily handled by tools as having it reside in a property.
In any case, what is standardized needs to have precise definitions or distinguishable among multiple definitions (or explicitly made usage/implementation dependent?) as subtle variations in meaning are possible. Note that for some assertions differences might be entirely in the value for confidence.
Reported: ARM 1.0b1 — Thu, 25 Aug 2011 04:00 GMT
Disposition: Closed; No Change — SACM 2.0
Addressed by harmonization to create SACM 2.0.
SACM 2 has added a new attribute to the base ModelElement class called isAbstract. This allows any part of an SACM model to marked as a placeholder for later instantiation according to optionally provided ImplementationConstraints. Status / lifecycle information about whether a modelElement is, for example, ‘Agreed / Confirmed / Rejected’, could also be added to any model element (if required) using TaggedValue (which could use a community consensus vocabulary established using the Terminology package).
Updated: Tue, 19 Dec 2017 20:05 GMT