[Redmine #6412] Dynamics definition of Longitudinal-Speed and Lateral-Lane Change
Bugzilla Link | 4027 |
Created on | May 23, 2019 09:56 |
Resolution | FIXED |
Resolved on | Dec 02, 2019 13:32 |
Version | 0.9.1 |
Extended Description
https://redmine.vires.com/issues/6412
René Weidling wrote:
Acoording to the MindMap, in the dynamics part the user can specify one (choice) boundary within which the defined action should be performed, i.e. either the time, the distance or the rate. In the schema, however, the user can set these simultaneously. Setting several boundaries can, however, lead to conflicting demands. Example from speed change:
<xsd:element name="Dynamics">
<xsd:attribute name="shape" type="Enum_Dynamics_shape" use="required"/>
<xsd:attribute name="rate" type="xsd:double" use="optional"/>
<xsd:attribute name="time" type="xsd:double" use="optional"/>
<xsd:attribute name="distance" type="xsd:double" use="optional"/>
</xsd:complexType>
</xsd:element>
To prevent conflicts and follow the MindMap it should read something like (not sure about the "use" attribute for the elements in a choice):
<xsd:element name="Dynamics">
<xsd:attribute name="shape" type="Enum_Dynamics_shape" use="required"/>
<xsd:choice>
<xsd:attribute name="rate" type="xsd:double" use="optional"/>
<xsd:attribute name="time" type="xsd:double" use="optional"/>
<xsd:attribute name="distance" type="xsd:double" use="optional"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
Otherwise, a description has to be provided, which parameter overrides the others in case of conflicting requirements.