sysand add seil-isr/ros2-sysmlv2
StringMessage for std_msgs/msg/String and TFMessage for
tf2_msgs/msg/TFMessage.LaserScan.ranges, are ordered nonunique, so a list may repeat a value.
Arrays of structured messages, such as Path.poses, are ordered.ParameterDescriptor.floatingPointRange and integerRange are optional
([0..1]), as in rcl_interfaces/msg/ParameterDescriptor.LifecycleStates follows the rcl default state machine: the four primary
states, the six transition states, and 25 transitions. Seven are requested
by events. Eighteen leave a transition state on the result of its callback,
the new TransitionCallbackReturn (Success, Failure, Error). The six
callback action definitions gain an out attribute result.configuring, activating, and so on)
instead of the primary states; ErrorEvent is removed; the exits of
errorProcessing are named onErrorSuccess, onErrorFailure, and
onErrorError (before: errorRecoverySuccess, errorRecoveryFailure).nav2_msgs sources. SmoothPathResult gains
errorMsg. The new CostmapMetaData carries all seven fields of
nav2_msgs/msg/CostmapMetaData, and Costmap carries it as
costmapMetadata, since the ROS2 field name metadata is a reserved
keyword.QoSCompatible carries its rule: false for a best-effort publisher with a
reliable subscriber and for a volatile publisher with a transient-local
subscriber, true for every other pair, including policies that defer to the
middleware (system default, unknown, best available). Deadline and
liveliness are not compared.WaitGoal.waitTime is
renamed time, the name of the Jazzy field. Costmap.metadataResolution,
metadataWidth, and metadataHeight are removed; their values are
costmapMetadata.resolution, costmapMetadata.sizeX, and
costmapMetadata.sizeY. A usage of QoSCompatible now has a value, so a
publisher and subscriber pair that the rule calls incompatible evaluates to
false.TopicConnection, ServiceBinding, and ActionBinding are interface
definitions, the SysML v2 construct for a connection whose ends are ports.
Their names and ends are unchanged, and no constraint was added. A usage may
be written with the keyword connection or interface. StaticTransform
and DynamicTransform stay connection definitions, since frames are parts.
The doc comment of TopicConnection says what agreement of its two ends
means (same topic name after namespace resolution, same message type,
compatible QoS) and where each is checked; ServiceBinding and
ActionBinding have doc comments in the same style.InterfaceDefinition, so a query for
ConnectionDefinition by exact metaclass no longer returns them. Model text
written against 0.1.1 is not affected in the cases we checked: usages with
either keyword, and user subtypes declared with interface def or
connection def, validate without change.in and out reversed.sysand build writes it, the series note reworded, and a logo that collapses cleanly where the index page blocks external images.First public release, alpha quality: the vocabulary is complete and validated, and its shape may still change before 1.0.
ros2_sysmlv2/.item def against the ROS2 Jazzy interface sources.