Issue 18704: Navigation through non-properties (sysml-rtf)
Source: NASA (Mr. Christopher Delp, Christopher.L.Delp(at)jpl.nasa.gov)
Nature: Revision
Severity: Critical
Summary: Many UML elements are semantically equivalent to properties, but are not properties in the abstract syntax, such as behavior parameters, activity variables and call behavior actions.  This means they cannot be used with deep nested connectors and other elements requiring property navigation.  Add stereotypes based on properties that have "runtime" instance values for these elements.
Resolution: 
Revised Text: 
Actions taken:
May 9, 2013: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 09 May 2013 09:46:57 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-Tracker: AAAAAA==


*******************************************************************************
Name:            Chris Delp
Employer:        JPL
mailFrom:        Christopher.L.Delp@jpl.nasa.gov
Terms_Agreement: I agree
Specification:   Systems Modeling Language
Section:          
FormalNumber:    ptc/2011-08-10
Version:         1.3
Doc_Year:        2012
Doc_Month:       June
Doc_Day:         01
Page:             
Title:           Navigation through non-properties
Nature:          Revision
Severity:        Critical
CODE:            3TMw8
B1:              Report Issue


Description:


Many UML elements are semantically equivalent to properties, but are not properties in the abstract syntax, such as behavior parameters, activity variables and call behavior actions.  This means they cannot be used with deep nested connectors and other elements requiring property navigation.  Add stereotypes based on properties that have "runtime" instance values for these elements.