-
Key: SYSML-64
-
Legacy Issue Number: 10023
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
propertyPath definition. In Blocks, NestedConnectorEnd 8.3.2.5, Attributes, propertyPath, at the end of the entry description, it says "not including the property which is directly connected.". I gather the property directly connected is identified by the UML ConnectorEnd.role metaproperty? If so, Constraint [1] isn't true, and the multiplicity of propertyPath should be 1.., rather than 2... The entry should clarify if the intention to only use NestedConnector below ports (ie, use the UML ConnectorEnd.partWithPort metaproperty). I think the simplest solution is to just remove the quoted phrase above. The path will be from the Block owning the connector all the way down the connected property. These would need to be consistent with values of UML's ConnectorEnd.role and ConnectorEnd.partWithPort properties, if any (ie, the first two elements in the path would need to be the same as these, if they exist)
-
Reported: SysML 1.0b1 — Sat, 29 Jul 2006 04:00 GMT
-
Disposition: Resolved — SysML 1.0
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT