 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
116 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
-- any octect string up to 16 bytes
XML Representation:
<xs:complexType name="CodeWord" >
<xs:simpleContent>
<xs:annotation>
<xs:documentation>
any octect string up to 16 bytes
</xs:documentation>
</xs:annotation>
<xs:extension base="CodeWord-string" >
<xs:attribute name="EncodingType" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="base64Binary"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:simpleType name="CodeWord-string">
<xs:restriction base="xs:base64Binary">
<xs:minLength value="2"/>
<xs:maxLength value="22"/>
</xs:restriction>
</xs:simpleType >
Used By: This entry is used directly by one other data structure in this standard, a DF called
DF_SignalRequest <ASN> <XML>. In addition, this item may be used by data structures in other ITS
standards.
7.34 Data Element: DE_CoefficientOfFriction
Use: Coefficient of Friction of an object, typical a wheel in contact with the ground. This DE is typically
used in sets where the value of each wheel is provided in turn as a measure of relative local traction.
ASN.1 Representation:
CoefficientOfFriction ::= INTEGER (0..50) -- re-confirm this range
-- where 0 = 0.00 micro (frictonless)
-- and 50 = 0.98 micro, in steps of 0.02
XML Representation:
<xs:simpleType name="CoefficientOfFriction" >
<xs:annotation>
<xs:documentation>
re-confirm this range
where 0 = 0.00 micro (frictonless)
and 50 = 0.98 micro, in steps of 0.02
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:unsignedByte">
<xs:maxInclusive value="50"/>
</xs:restriction>
</xs:simpleType>
Used By: This entry is used directly by one other data structure in this standard, a DF called
DF_VehicleStatus <ASN> <XML>. In addition, this item may be used by data structures in other ITS
standards.
Remarks: [Note: I seem to recall the ESS people defined some of this for mobile field devices, we should
compare with them and see what we can re-use.]
 |