Issues for Mailing list of the SysML-Modelica Transformation Specification Finalization Task Force
To comment on any of these issues, send email to sysml-modelica-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.
List of issues (green=resolved, yellow=pending Board vote, red=unresolved)
Issue 16376: Ecore is used for the Modelica metamodel in Part III rather than EMOF
Issue 16377: The UML Profile is represented in proprietary Eclipse format
Issue 16378: Section 2 Conformance requires more detail for practical definition of ‘full realization’ and ‘abstract syntax complianc
Issue 16379: Sections 3.1 and 3.2
Issue 16380: 6.1: this SysML issue does not belong here as such
Issue 16381: P6 uses ‘meta-case’ for transformation technology.
Issue 16382: Figure 2 uses stereotypes such as <<transformation>> that are not defined
Issue 16383: Section 8
Issue 16384: The QVT does not use the standard URI for the UML metamodel
Issue 16385: Not sure of the use of openmodelica.org.
Issue 16490: Incomplete Annex C Content
Issue 16545: SysML-Modelica Transformation Spec problem with <reference>
Issue 16556: SysML-Modelica Transformation Spec problem with <reference>
Issue 16593: clarification needed for the fromLibrary attribute
Issue 17214: new figure uses <<conformsTo>> <<transformation>> and <<instanceOf>> applied to lines using the Dependency notation
Issue 17215: In general the Part structure used is not appropriate for OMG specifications
Issue 17216: It's unclear what compliance would mean
Issue 17217: namespace definition in the XMI and the URI attribute of the Profile
Issue 17218: wrong reference
Issue 17221: The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3)
Issue 16376: Ecore is used for the Modelica metamodel in Part III rather than EMOF (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary:
Ecore is used for the Modelica metamodel in Part III rather than EMOF (EMOF is also supported by the EMF technology). Oddly though I can see no depiction of the metamodel in either ecore or EMOF: I would for example expect to see some UML class diagrams. Instead there is what appears to be Modelica syntax.
Resolution: The abstract syntax of Modelica, in other words its metamodel, needs to be represented in UML class diagrams. Figure 13 containing a representation of some Modelica metaclasses in an Ecore diagram will be replaced by UML class diagrams.
Revised Text: see pages 5 - 8 of ptc/2012-03-17
Actions taken:
July 21, 2011: received issue
July 19, 2012: closed issue
Discussion: There has been insufficient input to the current FTF to consider the resolution at
this time.
Disposition: Deferred
Issue 16377: The UML Profile is represented in proprietary Eclipse format (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: The UML Profile is represented in proprietary Eclipse format
Resolution: The SysML4Modelica has been converted into OMG-grade XMI and has been added to the inventory of files which still includes the profile in Eclipse format.
Disposition:Resolved
Revised Text:
Actions taken:
July 21, 2011: received issue
July 19, 2012: closed issue
Discussion: There has been insufficient input to the current FTF to consider the resolution at
this time.
Disposition: Deferred
Issue 16378: Section 2 Conformance requires more detail for practical definition of ‘full realization’ and ‘abstract syntax complianc (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: Section 2 Conformance requires more detail for the practical definition of ‘full realization’ and ‘abstract syntax compliance’
Resolution: Proposed change: leave out ‘full realization’ and ‘abstract syntax compliance’. In
addition, add a level 1 criteria referring to required level 0 compliance.
Revised Text: Section 2 (Conformance):
2nd and 3rd paragraphs
Compliance to Level 0 entails full realization of all the modeling concepts
included in the SysML4Modelica profile as defined in Part II of this specification.
Since no concrete syntax has been specified, only abstract syntax compliance is
required.
Compliance to Level 1 entails full realization of the bi-directional transformation
between SysML4Modelica models and corresponding Modelica models.
Replace by:
Compliance to Level 0: This level entails the support of all the modeling concepts
included in the SysML4Modelica profile as defined in Part II of this specification.
The SysML4Modelica profile must be compliant with OMG SysML v1.3.
Compliance to Level 1: In addition to the capabilities provided by Level 0, Level 1
supports the successful bi-directional transformation between SysML4Modelica
models and corresponding Modelica models. The bi-directional transformation is
considered successful if the original Modelica model and the Modelica model
generated by the round-trip transformation (Modelica->SysML4Modelica-
>Modelica) are semantically identical, that is, they result in the same simulation
results.
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Issue 16379: Sections 3.1 and 3.2 (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: 3.1 should reference version 1.1 of QVT.
3.2: It’s not clear how the MDA Foundation Model ‘constitute provisions of this specification’.
Resolution: Section 3.1 will reference version 1.1 of QVT and Section 3.2 will not refer to any
non-normative references including the MDA Foundation Model.
Revised Text: Section 3.1 (Normative References):
the 2nd bullet point
QVT, v1.0 (http://www.omg.org/spec/QVT/1.0/)
Replace by:
QVT, v1.1 (http://www.omg.org/spec/QVT/1.1/)
Section 3.2 (Non-normative References):
Replace the text in the section 3.2 by “None”.
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Issue 16380: 6.1: this SysML issue does not belong here as such (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: 6.1: this SysML issue does not belong here as such: if a change is needed it should be specified as a detailed edit to the SysML spec. Otherwise just raise the issue in the normal way.
Resolution: Section 6.1 will be deleted.
Revised Text: Delete Section 6.1 (Changes to Adopted OMG Specifications).
Delete the section heading 6.2. As a result, Section 6 won't have any
subsections.
Rename Chapter 6 from “Additional Information” to “Acknowledgments”.
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Issue 16381: P6 uses ‘meta-case’ for transformation technology. (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: P6 uses ‘meta-case’ for transformation technology.
Resolution: The capabilities of meta-CASE tools are not well-known. Therefore, the sentence
mentioning the implementation of the SysML-Modelica mapping by meta-CASE
tools is relaxed by referring to “tools” in general instead of “meta-CASE” tools.
Revised Text: Chapter 7 (Transformation Approach):
Remove the word “meta-CASE” in the 5th paragraph.
The revised text is then:
Such a formal definition of the mapping has the advantage that tools can be used
to generate executable transformations between SysML and Modelica modeling
tools.
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Issue 16382: Figure 2 uses stereotypes such as <<transformation>> that are not defined (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: Figure 2 uses stereotypes such as <<transformation>> that are not defined
Resolution: The <<transformation>> stereotype is a self-defined stereotype referring to a
mapping definition.
Revised Text: Section 7 (Transformation Approach):
Add the following sentence at the end of the 1st paragraph.
The «transformation» stereotype is a self-defined stereotype referring to a
mapping between the Modelica metamodel and the SysML4Modelica profile.
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Issue 16383: Section 8 (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: Section 8: presumably these are production rules for Modelica syntax. Does this need to be duplicated in this spec?
Resolution:
Revised Text:
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Discussion: There is no added value in duplicating the Modelica grammar production rules
from the Modelica specification. The grammar definition can be found in
"Appendix B Modelica Concrete Syntax" of the Modelica specification.
Disposition: Closed, no change
8/
Issue 16384: The QVT does not use the standard URI for the UML metamodel (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: The QVT does not use the standard URI for the UML metamodel
Resolution:
Revised Text:
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Discussion: Disposition: See issue 16385 for disposition
Issue 16385: Not sure of the use of openmodelica.org. (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: Not sure of the use of openmodelica.org.
Resolution: Issues 16384 and 16385 address the correctness of using non-normative URIs to
identify the UML and Modelica metaclasses in the QVT transformation. The
implementation of the transformation in QVT includes references to the
metaclasses of both the UML and Modelica metamodels. These references are
found next to the “modeltype” keyword at the beginning of each QVT
transformation.
Since no normative Modelica metamodel exists, there are no normative URIs to
identify the Modelica metaclasses. The QVT code can thus not refer to Modelica
metaclasses through normative URIs and be considered normative. The use of
non-normative URIs to identify the UML and Modelica metaclasses in the QVT
transformation is therefore acceptable.
The QVT code does not need to be changed. However, the SysML-Modelica
Transformation specification should not state that Parts III, IV and V of the
SysML-Modelica Transformation specification are normative since they are all
based on a non-normative Modelica metamodel from openModelica.
Revised Text: Section 13 (Modelica Meta-Modeling Approach):
Remove the following sentences at the end of the 1st paragraph:
“For the purpose of this transformation specification, the Modelica abstract
syntax metamodel defined in this Part of the specification is normative. This allows for an unambiguous mapping between the SysML4Modelica profile and
the Modelica language.”
Remove the the 2nd paragraph.
“Given the structure of the Modelica language as described in this document, the
differences in abstract syntax between the different Modelica tools are likely to be
small. Any difference in terminology or minor differences in structure can be
handled with tool-specific transformations that will be performed on the ASTs.”
Replace the 1st footnote on page 34:
“Part III of the SysML-Modelica Transformation Specification is normative.”
by
“Part III of the SysML-Modelica Transformation Specification is non-normative.”
Replace the 1st footnote on page 53:
“Part IV of the SysML-Modelica Transformation Specification is normative.”
by
“Part IV of the SysML-Modelica Transformation Specification is non-normative.”
Replace the 1st footnote on page 63:
“Part V of the SysML-Modelica Transformation Specification is normative.”
by
“Part V of the SysML-Modelica Transformation Specification is non-normative.”
Replace the 3rd bullet point on page 1:
“Part III — Modelica meta-model (normative)”
by
“Part III — Modelica meta-model (non-normative)” Replace the 4th bullet point on page 1:
“Part IV — SysML-Modelica mapping, a bidirectional mapping between the
SysML4Modelica profile and the Modelica meta-model (normative)”
by
“Part IV — SysML-Modelica mapping, a bidirectional mapping between the
SysML4Modelica profile and the Modelica meta-model (non-normative)”
Actions taken:
July 21, 2011: received issue
January 11, 2012: closed issue
Issue 16490: Incomplete Annex C Content (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Nature: Uncategorized Issue
Severity:
Summary: Source: Georgia Institute of Technology (Mr. Axel Reichwein, axel.reichwein(at)me.gatech.edu)
Summary: The QVT code shown in Annex C is incomplete. In addition, a figure showing an overview of the QVT implementation approach would be useful.
Resolution: The QVT code in Annex C is outdated and has to be replaced by the latest
version. Since the current QVT code consists of approx. 5000 lines of code, it
would be too large to be placed in Annex C. Instead, Annex C should contain a
URL reference to a separate document containing all QVT transformations in a
zipped file. In addition, a figure showing an overview of the QVT implementation
approach should be placed in Annex C.
Revised Text: Annex C (QVT Transformation):
The first sentence:
This part of the document includes the QVT-operational mapping rules. Each
section of the mapping below refers to the rule labels introduced in Part IV.
will be replaced by
The overview of an implementation of the SysML-Modelica Transformation based
on QVT is shown in Figure 37. All the Java and QVT transformation files used for
the implementation of the transformation have been zipped into a common file
that can be retrieved at this URL: http://www.omg.org/cgi-bin/doc? ptc/2011-08-16 Annex C will include the additional Figure 37:
Figure 37 will have the caption “Overview of an implementation of the SysMLModelica
Transformation based on QVT”.
In addition, all the QVT code in Annex C will be removed.
Actions taken:
August 10, 2011: received issue
January 11, 2012: closed issue
Issue 16545: SysML-Modelica Transformation Spec problem with <reference> (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Uncategorized Issue
Severity:
Summary: As found by Lenny Delligatti of Lockheed Martin.
On page 5 of the spec., it shows that the SysML4Modelica profile references the SysML profile (Figure 2 in the screenshot below):
But I believe that’s an error. I believe that a «reference» dependency is only legal from a profile to a metamodel.
One profile can «import» another profile (and thus transitively reference a metamodel), but not «reference» another profile.
Resolution: A UML dependency can be between any two NamedElements. The dependency can also be tagged with any stereotype and be given any name. So the <<reference>> dependency is by itself legal. However, a keyword such as <<import>> can also be applied to a dependency.The <<import>> keyword seems more suitable to be applied on a dependency between profiles. So the <<reference>> dependencies to the UML4SysML metamodel (as shown in the SysML spec) in Figure 2 are kept and the <<reference>> dependency between the SysML4Modelica and SysML profiles in Figure 2 is replaced by an <<import>> dependency.
Revised Text: see pages 9 - 10 of ptc/2012-03-17
Actions taken:
September 9, 2011: received issue
July 19, 2012: closed issue
Issue 16556: SysML-Modelica Transformation Spec problem with <reference> (sysml-modelica-ftf)
Click here for this issue's archive.
Click here for this issue's attachments.
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Uncategorized Issue
Severity:
Summary: As found by Lenny Delligatti of Lockheed Martin.
On page 5 of the spec., it shows that the SysML4Modelica profile references the SysML profile (Figure 2 in the screenshot below):
But I believe that’s an error. I believe that a «reference» dependency is only legal from a profile to a metamodel.
One profile can «import» another profile (and thus transitively reference a metamodel), but not «reference» another profile.
Resolution: See issue 16545 for disposition
Revised Text:
Actions taken:
September 9, 2011: received issue
July 19, 2012: closed issue
Discussion:
Issue 16593: clarification needed for the fromLibrary attribute (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Georgia Institute of Technology (Prof. Chris Paredis, Ph.D, chris.paredis(at)me.gatech.edu)
Nature: Clarification
Severity:
Summary: In the SysML-Modelica Transformation Specification (http://www.omg.org/spec/SyM/1.0/Beta1/PDF/), the attribute fromLibrary for the stereotype «modelicaClassDefinition» is not sufficiently clearly defined (Section 8.2, page 10). The spec mentions that some details (e.g. "value properties and parts") can be omitted when using the fromLibrary tag, but the spec is not sufficiently precise as to which details exactly can/should be omitted and which should still be retained. Since this is a construct that will likely be used extensively, it should be defined more precisely.
Resolution: The identified issue does not relate to the mapping of language constructs between SysML and Modelica but rather to a user- and tool-specific usability aspect of the transformation. The issue therefore does not identify a problem with the specification. Additionally, the “fromLibrary” attribute of the «modelicaClassDefinition» stereotype will be removed since it does not relate to the mapping of language constructs between SysML and Modelica.
Revised Text: Chapter 8.2 «modelicaClassDefinition»
Delete the last bullet point describing the “fromLibrary” attribute of the «modelicaClassDefinition» stereotype.
Actions taken:
October 12, 2011: received issue
July 19, 2012: closed issue
Issue 17214: new figure uses <<conformsTo>> <<transformation>> and <<instanceOf>> applied to lines using the Dependency notation (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary: the new figure still uses <<conformsTo>> <<transformation>> and <<instanceOf>> applied to lines using the Dependency notation. These have no defined meaning (either as keywords nor as stereotypes defined either in this specification, SysML or UML). Whatever <<instanceOf>> means it’s not the case that a transformationRecord is an instance of a transformation. If these stereotypes are retained there should be an explanation to say they are purely informal
Resolution: An additional sentence needs to be added stating that the <<conformsTo>>, <<transformation>> and <<instanceOf>> stereotypes are purely informal
Revised Text: Insert at the end of the first paragraph in Section 7:
“The <<conformsTo>>, <<transformation>> and <<instanceOf>> stereotypes are purely informal.”
Actions taken:
March 9, 2012: received issue
July 19, 2012: closed issue
Issue 17215: In general the Part structure used is not appropriate for OMG specifications (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Revision
Severity:
Summary: In general the Part structure used is not appropriate for OMG specifications. It does not make sense to label Part I as non-normative. Especially as Part I includes Conformance and Normative References!
Resolution: The part structure is kept since it is still considered helpful to structure the document. Part 1 needs to be labeled as normative.
Revised Text: Section 0, page 1:
Replace in the footnote:
“non-normative”
by:
“normative”
Actions taken:
March 9, 2012: received issue
July 19, 2012: closed issue
Issue 17216: It's unclear what compliance would mean (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Revision
Severity:
Summary: Section 2 includes in Level 0 Compliance “The SysML4Modelica profile must be compliant with OMG SysML v1.3.”. However a) this profile is part of this specification and b) SysML does not define compliance for Profiles. So it’s unclear what compliance would mean
Resolution: In order to avoid any confusion, the sentence "The SysML4Modelica profile must be compliant with OMG SysML v1.3" should be remove.
Revised Text: Delete this sentence in Section 2 on Compliance Level 0:
“The SysML4Modelica profile must be compliant with OMG SysML v1.3”
Actions taken:
March 9, 2012: received issue
July 19, 2012: closed issue
Issue 17217: namespace definition in the XMI and the URI attribute of the Profile (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Revision
Severity:
Summary: The namespace definition in the XMI and the URI attribute of the Profile is xmlns:SysML4Modelica=http://www.omg.org/spec/SysM/20120213. This uses SysM not the official directory (according to the other documents) which is the shorter SyM.
Resolution: The spec name “SysM” was wrongly used in the XMI definition of the SysML4Modelica profile. It needs to be changed to the shorter "SyM" version.
Revised Text: Replace “SysM” by “SyM” in the XMI definition of the SysML4Modelica profile
Actions taken:
March 9, 2012: received issue
July 19, 2012: closed issue
Issue 17218: wrong reference (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Revision
Severity:
Summary: The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3) included in the normative references
Resolution: See issue 17214 for disposition
Revised Text:
Actions taken:
March 9, 2012: received issue
July 19, 2012: closed issue
Issue 17221: The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3) (sysml-modelica-ftf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Revision
Severity:
Summary: The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3) included in the normative references
Resolution: The figure should reference UML package instead of the UML4SysML package.
Revised Text: see page 18 of ptc/2012-03-17 for details
Actions taken:
March 9, 2012: received issue
July 19, 2012: closed issue