ELD Log Event Sequences

[HVCSFriend]

7.25 Event Type from the ELD mandate dictates that Event Type Data Range: 1-7 as described on Table 9 of this appendix; Data Length: 1 character; Data Format: as in ; Disposition: Mandatory; Examples: [1], [5], [4], [7]

We may want to have EventTypeCode and EventType, depending which format the upstream telematics system sends. It should be the eventTypeCode, but in the ELD Mandate "Example of Print/Display detail log data," the Event Type/Status that is displayed is the eventType string message and not the eventTypeCode number.

[BenGardiner]

I'm going to build on top of these changes to (hopefully) completely resolve the ELD changes needed. Here's a plan overview:

• Rename the objects to "Log Event" instead of "Duty Status XXX" [DONE]

• Include EventDataCheckValue [DONE]

• Add a naming prefix requirement for any extensions [DONE]

• close #84 b/c day logs will be created by post-processing

• resolve all of #85, #76, #66, #60 and #59 in changes: use a single eventtype to designate the different events and their subtypes. remove the current 'eventType', rename the current status to 'eventType' re-sort and massage the enums to the new 'eventType'

[BenGardiner]

The changes collected here are intended to migrate the ELD log event data types to a scheme where compliance reports can be generated by processing sequences of the log event objects. This is captured as an explicit use case now, see: Generate ELD reports for compliance from OTAPI in progress -- issue #94

Summary of changes here:

• Rename the objects to "Log Event" instead of "Duty Status XXX"
• Add a naming prefix requirement for any extensions
• resolve all of #85, #76, #66, #60 and #59 in changes: use a single eventtype to designate the different events and their subtypes. remove the current 'eventType', rename the current status to 'eventType' re-sort and massage the enums to the new 'eventType'
• remove eventRecordStatus, can be derived from sequence of Log Event Objects
• remove eventTypeCode, can be derived from sequence of Log Event Objects
• rename 'outputFileComment' to 'comment' -- removes the association to ELD output files
• remove the notion of STATUS_AUTHORITY / EVENTTYPE_AUTHORITY
• remove malfunction, can be derived from a sequence of Log Event Objects

Resolves the following issues:

• convert some combo enums into flags -- #85
• require co-drivers in the Day Log Event -- #84
• include a list of contributors -- #77 opened
• Ensure Duty Status Log has all 'normal statuses' -- #76
• add missing Duty Status Log fields -- #66
• Use Case: Driver Availability - Add Driver Current Status blocked -- #60
• Use Case: Compliance and Safety Monitoring - Add Standard Coding for Malfunctions/Data Diagnostic Event Detection blocked -- #59
• require a prefix 'namespacing' for extensions -- #111