Issue 19286: Abstract syntax for the initial values (sysml-rtf) Source: Airbus Group (Mr. Yves Bernard, yves.bernard(at)airbus.com) Nature: Uncategorized Issue Severity: Summary: The abstract syntax supporting the specification of initial values for properties of SysML block has to be clarified and aligned with the intended semantics. In SysML 1.4, §8.3.1.2.8 says: “A compartment with a label of “initialValues” may be used to show values of properties belonging to a containing block. These values override any default values that may have been previously specified on these properties on their originally defining block” While §8.3.2.3 says: “An entire tree of context-specific values can be specified on a containing block to carry values of nested properties as shown on an internal block diagram”, then: “If a property belonging to a block has a specification of initial values for any of the properties belonging to its type, then the default value of that property must be a UML InstanceValue element. This element must reference a UML InstanceSpecification element created to hold the initial values of the individual properties within its usage context. The instance specification must be unnamed and owned by the same package that owns the outermost containing block for which the initial values are being specified” If the specification of an initial value is “context specific”: · It cannot be specified using the default value of a property · It should be possible to distinct initial value depending on the context, i.e. we need a resolution mechanism to know which initial value has to be used Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: March 21, 2014: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: "BERNARD, Yves" To: "issues@omg.org" CC: "Sysml-Rtf (sysml-rtf@omg.org)" Date: Fri, 21 Mar 2014 08:52:43 +0100 Subject: Abstract syntax for the initial values Thread-Topic: Abstract syntax for the initial values Thread-Index: Ac9E2Mj7zDmZ5hefRM23hNlQjSuMrw== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org Hi Juergen, This is a new issue for SysML. Description: The abstract syntax supporting the specification of initial values for properties of SysML block has to be clarified and aligned with the intended semantics. In SysML 1.4, §8.3.1.2.8 says: .A compartment with a label of .initialValues. may be used to show values of properties belonging to a containing block. These values override any default values that may have been previously specified on these properties on their originally defining block. While §8.3.2.3 says: .An entire tree of context-specific values can be specified on a containing block to carry values of nested properties as shown on an internal block diagram., then: .If a property belonging to a block has a specification of initial values for any of the properties belonging to its type, then the default value of that property must be a UML InstanceValue element. This element must reference a UML InstanceSpecification element created to hold the initial values of the individual properties within its usage context. The instance specification must be unnamed and owned by the same package that owns the outermost containing block for which the initial values are being specified. If the specification of an initial value is .context specific.: · It cannot be specified using the default value of a property · It should be possible to distinct initial value depending on the context, i.e. we need a resolution mechanism to know which initial value has to be used Thanks, Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. X-Trusted-NM: yes Subject: Re: Abstract syntax for the initial values From: Nerijus Jankevicius Date: Fri, 21 Mar 2014 10:07:40 +0200 Cc: "issues@omg.org" , "Sysml-Rtf (sysml-rtf@omg.org)" To: "BERNARD, Yves" X-Mailer: Apple Mail (2.1874) X-Virus-Scanned: amavisd-new at omg.org Yves, I see no issue here. Block may define default values of the properties (using default value of the property), but these defaults can be changed in any particular context where this block is used. Redefinition and resolution mechanism of default values is described in exact same text you just paste - 8.3.2.3. Default values are redefined using slot values of an InstanceSpecification, which should be unnamed and owned in the same package as the redefinition context. This technique is successfully implemented in MagicDraw. You may look for a sample model under /samples/sysml/context specific values.mdzip if interested. See you in Reston, Nerijus On Mar 21, 2014, at 9:52 AM, BERNARD, Yves wrote: Hi Juergen, This is a new issue for SysML. Description: The abstract syntax supporting the specification of initial values for properties of SysML block has to be clarified and aligned with the intended semantics. In SysML 1.4, §8.3.1.2.8 says: .A compartment with a label of .initialValues. may be used to show values of properties belonging to a containing block. These values override any default values that may have been previously specified on these properties on their originally defining block. While §8.3.2.3 says: .An entire tree of context-specific values can be specified on a containing block to carry values of nested properties as shown on an internal block diagram., then: .If a property belonging to a block has a specification of initial values for any of the properties belonging to its type, then the default value of that property must be a UML InstanceValue element. This element must reference a UML InstanceSpecification element created to hold the initial values of the individual properties within its usage context. The instance specification must be unnamed and owned by the same package that owns the outermost containing block for which the initial values are being specified. If the specification of an initial value is .context specific.: · It cannot be specified using the default value of a property · It should be possible to distinct initial value depending on the context, i.e. we need a resolution mechanism to know which initial value has to be used Thanks, Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "BERNARD, Yves" To: Nerijus Jankevicius CC: "issues@omg.org" , "Sysml-Rtf (sysml-rtf@omg.org)" Date: Fri, 21 Mar 2014 12:06:57 +0100 Subject: RE: Abstract syntax for the initial values Thread-Topic: Abstract syntax for the initial values Thread-Index: Ac9E3KkHNiPkN/ycRf+mfi3E0LZ2BAAFfXcA Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org Nerijus, Thanks. The point is that it links the definition context to package containing the .block for which the initial values are being specified. rather than to this block itself. This induces a specific semantics for the Packages that they don.t have (i.e. defining a context). Nothing prevents a Package from containing blocks which have distinct initial values for properties of the same type. In addition, it is not clear why the current text only applies to properties for which any property of their type have an initial value. What about the other cases? Yves De : Nerijus Jankevicius [mailto:nerijus@nomagic.com] Envoyé vendredi 21 mars 2014 09:08 À: BERNARD, Yves Cc : issues@omg.org; Sysml-Rtf (sysml-rtf@omg.org) Objet : Re: Abstract syntax for the initial values Yves, I see no issue here. Block may define default values of the properties (using default value of the property), but these defaults can be changed in any particular context where this block is used. Redefinition and resolution mechanism of default values is described in exact same text you just paste - 8.3.2.3. Default values are redefined using slot values of an InstanceSpecification, which should be unnamed and owned in the same package as the redefinition context. This technique is successfully implemented in MagicDraw. You may look for a sample model under /samples/sysml/context specific values.mdzip if interested. See you in Reston, Nerijus On Mar 21, 2014, at 9:52 AM, BERNARD, Yves wrote: Hi Juergen, This is a new issue for SysML. Description: The abstract syntax supporting the specification of initial values for properties of SysML block has to be clarified and aligned with the intended semantics. In SysML 1.4, §8.3.1.2.8 says: .A compartment with a label of .initialValues. may be used to show values of properties belonging to a containing block. These values override any default values that may have been previously specified on these properties on their originally defining block. While §8.3.2.3 says: .An entire tree of context-specific values can be specified on a containing block to carry values of nested properties as shown on an internal block diagram., then: .If a property belonging to a block has a specification of initial values for any of the properties belonging to its type, then the default value of that property must be a UML InstanceValue element. This element must reference a UML InstanceSpecification element created to hold the initial values of the individual properties within its usage context. The instance specification must be unnamed and owned by the same package that owns the outermost containing block for which the initial values are being specified. If the specification of an initial value is .context specific.: · It cannot be specified using the default value of a property · It should be possible to distinct initial value depending on the context, i.e. we need a resolution mechanism to know which initial value has to be used Thanks, Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.