Navigation bar
  Print document Start Previous page
 93 of 240 
Next page End  

SAE J2735-Draft-Rev26 [issued: 09-18-08] 
-
93 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
         <xs:element name="statusRear" type="WiperStatusRear"  minOccurs="0"/>
         <xs:element name="rateRear" type="WiperRate"  minOccurs="0"/>
      </xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
Remarks: Note that when the state changes an event flag may be raised in the BSM and this data frame
may be transmitted in Part II of that message to relate the new state.
7. Data Elements
Messages and data frames specified in Clauses 5 and 6 shall be composed of message elements.  Any
message or data frame specified in Clauses 6 or 7 shall have all of its DEs specified in this clause, except
those DEs that are primitive ASN.1 data types or those that are adopted from other functional areas, or
defined in other volumes of the family of standards.  In the later cases, the referenced standards shall be
consulted.
Regarding equivalent entries to be placed into a data registry. The mapping between data elements and
analogous meta data entries have been explained in other ITS stds. In addition, some meta information is
constant in this entire standard and need not be repeated with each entry here. These include the sponsor
and steward of the entries [SAE], the registration status [registered once the standard is adopted] and the
revision date [the date of the standards adoption]. The class name is always ITS.
The productions of ASN.1 which follow shall be considered normative in nature.  While the majority of the
normative content is reflected in the actual syntax of the ASN.1 some entries also have additional
statements in the ASN.1 comments which shall be considered to be normative as well.  In addition, the
commentary provided with each entry may also provide additional normative restrictions on the proper use
of the entry which shall be followed. The XML productions follow directly from the ASN.1 specifications
and the same rules shall be applied.
7.1 Data Element: DE_Extent
Use: The spatial distance over which this message applies and should be presented to the driver.  Under
certain conditions some messages may never be shown to the driver of a vehicle if they are short in
duration and other conflicting needs supercede the display until such time as the subject message is no
longer relevant.
ASN.1 Representation:
Extent ::= ENUMERATED {
    useInstantlyOnly   (0),
    useFor3meters      (1),
    useFor10meters     (2),
    useFor50meters     (3),
    useFor100meters    (4),
    useFor500meters    (5),
    useFor1000meters   (6),
    useFor5000meters   (7),
    forever          (255)  -- very wide area
    }
    -- encode as a single byte
XML Representation:
<xs:simpleType name="Extent" >
      <xs:annotation>
         <xs:appinfo>
            useInstantlyOnly (0)
Click to Convert - Powerful PDF Converter and HTML Converter.