Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J2353-2019 Data Dictionary: Standardizing Advanced Traveler Information System Data
The SAE J2353-2019 standard provides a comprehensive data dictionary for Advanced Traveler Information Systems (ATIS). By defining a consistent set of data element names, definitions, and types, it enables different ATIS implementations to share information seamlessly. This standard covers directory entries, search parameters, error notifications, spatial data, and more. Although declared ‘Stabilized’ by the SAE V2X Core Technical Committee (indicating mature technology with no planned updates), its framework remains a valuable reference for legacy and foundational ATIS deployments.
Scope and Structure of the ATIS Data Dictionary
The data dictionary in SAE J2353-2019 covers a wide range of information types critical for traveler information systems. Elements are organized by domain (e.g., DirectoryEntry, DirectorySearch, Error, Flight, Pollution) and are named using a hierarchical pattern that clearly indicates context and data type. For example, DirectoryEntry_Phone_Number comprises the domain (DirectoryEntry), the specific field (Phone), and the data type (Number). This structure promotes clarity and reduces ambiguity across multiple systems.
Below is an illustrative sample of data elements defined in the standard:
| Descriptive-Name | Data Type | Example Purpose |
|---|---|---|
| DirectoryEntry_Phone_Number | Text | Stores a phone number for a directory entry. |
| DirectoryEntry_Type_Code | Code | Indicates type of entry (e.g., restaurant, lodging). |
| DirectorySearch_Keywords_Text | Text | Keywords used for directory searches. |
| Error_NotificationCode_Code | Code | Machine-readable error classification code. |
| Incident_Location_Spatial | Spatial | Spatial location of an incident. |
| Lot_Status_Code | Code | Status of a parking lot (e.g., full, available). |
The dictionary categorizes elements as Code, Text, Quantity, Spatial, etc., enforcing consistency and easing automated processing. Mandatory and optional elements are explicitly defined, allowing implementers flexibility while ensuring core fields are always present.
Engineering Design Insights and Conformance
🛠️ One of the key design strengths of SAE J2353-2019 is its hierarchical naming convention. The pattern Domain_Attribute_Type makes it straightforward to identify the purpose and expected data type of each element. For example, ATIS_Date_Date immediately informs developers that this element belongs to the ATIS domain, represents a date, and is of type Date. This systematic approach reduces misinterpretation and facilitates mapping between different implementations.
🔍 Another insight is the inclusion of both mandatory and optional elements. Core elements like Message_Version_Number provide foundational structure, while optional fields like DirectoryEntry_ExtendedInformation_Text allow systems to include additional details without breaking compatibility. The standard also defines conformance criteria, ensuring that systems adhering to the dictionary can pass interoperability tests.
Callout: Stabilized Status SAE J2353-2019 has been stabilized, meaning no further revisions are planned. While this ensures backward compatibility, implementers should verify the continued suitability of these data elements against emerging technologies. The standard is a snapshot of validated practices, particularly useful for systems requiring long-term stability.
⚠️ Common Pitfall: Naming Compliance The hierarchical naming prefix (e.g., DirectoryEntry_) is mandatory for conformance. Omitting or modifying it can lead to non-compliant implementations and interoperability failures. Always include the full descriptive name as defined in the dictionary.
Frequently Asked Questions (FAQs)
1. Why was SAE J2353-2019 stabilized rather than reaffirmed or revised?
The SAE V2X Core Technical Committee found no active users for this technical report at the time of its periodic review. As a result, it was stabilized to preserve its content as a historical reference. Users are still responsible for verifying its applicability to current projects.
2. How are ATIS data elements uniquely named in this dictionary?
Each data element follows a Descriptive-Name that combines a domain prefix, attribute identifier, and data type suffix—for example, DirectoryEntry_RestaurantSubType_Code. This design ensures that every element is globally distinctive and self-descriptive, aiding in cross-system data integration.
3. What categories of data elements does SAE J2353-2019 cover?
The dictionary includes elements for directory services (e.g., names, phone numbers, types), travel condition reporting (e.g., incidents, parking lots), message handling (e.g., priority, confidence), pollution measurements, flight information, and spatial references—all essential for comprehensive traveler information.
4. How does the standard address conformance testing?
Section 4 of J2353-2019 outlines conformance requirements. Implementations must include all mandatory data elements and properly encode optional ones as defined. Adhering to the naming and type specifications is necessary to pass interoperability evaluations and ensure consistent data exchange.
