| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| SACM24-4 | name should be a multi-string | SACM 2.3b1 | open | |||
| SACM24-3 | ExpressionLangString should not exist | SACM 2.3b1 | open | |||
| SACM24-2 | ExpressionLangString should not exist | SACM 2.3b1 | open | |||
| SACM24-1 | Grammatical errors | SACM 2.3b1 | open |
right now the Name of a model element can not be a multi-string... which it should be
There is no reason to have both LangString and ExpressionLangString, given the constraint on ExpressionLangString that the expression and the content cannot both have values. If you insist on having both, have a common base class that includes only the 'lang' attribute - then LangString can have the content field and ExpressionLangString can have the 'expression' field.
There is no reason to have both LangString and ExpressionLangString, given the constraint on ExpressionLangString that the expression and the content cannot both have values. If you insist on having both, have a common base class that includes only the 'lang' attribute - then LangString can have the content field and ExpressionLangString can have the 'expression' field.
Generally: This document is replete with grammatical errors. Has someone run a grammar checker on it?
Specifically:
In addition, the 'Attributes' section for 'ExpressionLangString' states:
"expression:Terminology::ExpressionElement[1] (composition) – a reference"
The field is either a reference or a composition - but not both. Pick one.