Issues for Mailing list of the Dynamic Deployment and Configuration for RTC (DDC4RTC) 1.0 FTF

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 17455: The XMI is invalid and produces many errors at http://syseng.nist.gov/se-interop/sysml/validator/
Issue 17456: The type of property RTComponentPortDescription
Issue 17457: The XMI includes the UML state machine metamodel
Issue 17458: All EA – specific content should be removed
Issue 17459: The model should us platform-independent data types
Issue 17460: It is not clear how much of the model is normative

Issue 17455: The XMI is invalid and produces many errors at http://syseng.nist.gov/se-interop/sysml/validator/ (ddc4rtc-ftf)

The XMI is invalid and produces many errors at http://syseng.nist.gov/se-interop/sysml/validator/ 

 The type of property RTComponentPortDescription:: properties is not Property from the external specification but the built-in EAJava_Property

 

The XMI includes the UML state machine metamodel

Here are three issues that I found in the XMI file mars/12-06-12:

 

1.       All EA – specific content should be removed

Here are three issues that I found in the XMI file mars/12-06-12:

The model should not use Java-specific data types EAJava_boolean etc: instead it should use platform-independent data types

 Here are three issues that I found in the XMI file mars/12-06-12:

It is not clear how much of the model is normative.  The state diagram that corresponds to figure 8.9 is clearly not normative.  If some of these diagrams are normative, I believe that there should be two separate XMI files, one for normative content and the other for informative content