|     SAE J2735-Draft-Rev28 [issued: 11-10-08]   -  223 -  This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.                 <xs:enumeration value="useFor50meters"/>                 <xs:enumeration value="useFor100meters"/>                 <xs:enumeration value="useFor500meters"/>                 <xs:enumeration value="useFor1000meters"/>                 <xs:enumeration value="useFor5000meters"/>                 <xs:enumeration value="forever"/>              </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_RoadSideAlert <ASN> <XML>.   In addition, this item may be used by data structures in other  ITS standards.  8.3 Data Element: DE_FurtherInfoID [ATIS]  Use:  This data element provides a link number to other messages (described here and in other message set  standards) which relate to the same event.  Use zero when unkown or not present.  ASN.1 Representation:    FurtherInfoID ::= INTEGER (0..65535)     -- a link to any other incident      -- information data that may be available      -- in the normal ATIS incident description      -- or other messages     -- two bytes in length  XML Representation:    <xs:simpleType name="FurtherInfoID" >        <xs:annotation>           <xs:documentation>                     a link to any other incident              information data that may be available              in the normal ATIS incident description              or other messages              two bytes in length           </xs:documentation>        </xs:annotation>        <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_RoadSideAlert <ASN> <XML>.   In addition, this item may be used by data structures in other  ITS standards.  Remarks:  Some message sets allow a request of other relevant messages by use of this ID, some others do  not. Some messages do not yet support this ID and force the message receiver to sort the recovered  message to align event geographically.  This is expected to be an area of harmonization.  Developers should  also note that data from different source agencies can vary with the numbering used as well.  8.4 Data Element: DE_HorizontalDatum:cd [LRMS]  Use:  The underlying horizontal geodetic datum for a geographic coordinate.  ASN.1 Representation:    HorizontalDatum ::= ENUMERATED {wgs-84           (0),    wgs-84egm-96     (1),    nad83            (2),    nad27            (3),   ... -- # LOCAL_CONTENT  }  |