 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
37 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
a 'map node' is pob no needed -->
<xs:element name="appchCnt" >
<xs:simpleType>
<xs:restriction base="xs:unsignedByte">
<xs:minInclusive value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- the number of approaches
there will be at least this
many "lane states" that follow -->
<xs:element name="lanesCnt" >
<xs:simpleType>
<xs:restriction base="xs:unsignedByte">
<xs:minInclusive value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- hate this name ! -->
<xs:element name="states" >
<xs:complexType>
<xs:sequence minOccurs="1" maxOccurs="255">
<xs:element name="state" type="MovementState" />
<!-- each Movement/lane is given in turn and contains its state, and
seconds to the next event etc. -->
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="premept" type="PreemptionState" />
<!-- all posible pre-emption states and
other intersecton wide data is found
here -->
<xs:element name="localSPAT" type="local:SPAT" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
Remarks: Note: This message is still very draft it its overall format. There is no reason this message could
not nest multiple intersections worth of data at once, next edition I will allow nesting, Ed.