 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
168 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<xs:appinfo>
notInUseOrNotEquipped (0)
emergency (1)
nonEmergency (2)
pursuit (3) -- all others Future Use
</xs:appinfo>
<xs:documentation>
values to 127 reserved for std use
values 128 to 255 reserved for local use
</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:unsignedInt">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="3"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="notInUseOrNotEquipped"/>
<xs:enumeration value="emergency"/>
<xs:enumeration value="nonEmergency"/>
<xs:enumeration value="pursuit"/>
</xs:restriction>
</xs:simpleType >
</xs:union>
</xs:simpleType>
Used By: This entry is used directly by one other data structure in this standard, a MSG called
MSG_EmergencyVehicleAlert <ASN> <XML>. In addition, this item may be used by data structures
in other ITS standards.
Remarks: There are remaining issues with this data element, and changes may occur after serious review
by a number of different agencies types. For example, codes (such as NEMSIS codes) are not really
uniform and understood (even within a single service); the urgency of a "code 3" run is different in
different parts of the world. Perhaps the common element here is what action the receiving driver is
supposed to do (nothing, follow flagman, be alert, pull over, etc.). See also some of the "mandatory" ITIS
advice codes like this. For some applications, some slow speed maneuvering type codes are likely added in
future editions (moving a fire truck or tow truck around an incident scene, for example).
7.112 Data Element: DE_RTCM_MsgType (REMOVE)
Use: The RTCM-MsgType provides the 12 bit value defined in the RTCM standards for each message. In
this standard this is rounded to 16 bits (2 bytes) and the upper four bits are defined as zero when one of the
RTCM messages are used. Any bit being set to one in this range would indicate a locally defined (non
national standard) meaning. Note that the RTCM message standard itself defines some private proprietary
message types (in the range 4001 to 4095 in the 12 bit system) and these are also supported. Refer to the
the RTCM for the latest list of these assignments and uses.
ASN.1 Representation:
RTCM-MsgType ::= INTEGER (0..65535)
XML Representation:
<xs:restriction base="xs:unsignedShort"/>
</xs:simpleType>
Used By: This entry is used directly by one other data structure in this standard, a MSG called
MSG_RTCM_Corrections (Revise this as per VSC) <ASN> <XML>. In addition, this item may be
used by data structures in other ITS standards.
Remarks: DEBATE NOTE: We might want to make this a long enumerated list of possible message
types to make the XML instances more readable to others. On the other hand, I am not sure all the RTCM
 |