reportEventsDirectly and respondCurrentDataDirectly clarifications

[GCoxCasey]

Please could we have some clarification on section 4.1 of Lucid Protocol specification 3.0.
the section is shown below:

4.1 Data formats
The FD sends data values to the SA in a flexible data format. This supports simple data as well as full detail. While in JSON format, variable names and data layout are optimised to reduce message size.
Data is sent in the order that it is gathered. FD Configuration regulates when and how data is sent, such as on a priority basis. However, earlier data is always sent before later data unless the FD is responding to a request for data gathered in a specified period.
Reporting of data is always in ascending time order unless either of these two boolean properties are true in the FD Profile.
If reportEventsDirectly is specified with true, then the FD may send data values where the Action type is 3, and the data values associated with that event can be sent before other data values.
If respondCurrentDataDirectly is specified with true, then the FD will respond to SA current data request messages with the latest current data before sending older data.

1. reportEventsDirectly - Action Type is 3

We think 'Action Type is 3' is intended to mean 'Action Type 1 or 2' is that correct?

2. ReportEventsDirectly Scenario

The specification says:

Data is sent in the order that it is gathered.
and
However, earlier data is always sent before later data unless the FD is responding to a request for data gathered in a specified period.

Given the following scenario:

1. AIP-001 logs 10 logged data samples at the FD (ActionType 0)
2. Later AIP-001 state changes causing an ActionType 2 event to be logged.
3. FD connects to the broker.
4. FD publishes UP/data message containing the data for AIP-001.

QUESTIONS

1. Does the FD send the (later) ActionType 2 event in the UP/data json data array before the (earlier) logged data in the same payload?
   (so the timestamps of the samples for the point would then be out of order)
2. If it does, is the FD expected to specify a specific Reason code for this event (for example STATE CHANGE?)

3. respondCurrentDataDirectly Scenario

Based on the same ' ReportEventsDirectly Scenario' but also with respondCurrentDataDirectly enabled.

QUESTIONS

1. Is the FD required to send the current data and event data in a specific order before the logged data in the same UP/data payload?
   By this we mean if both respondCurrentDataDirectly and ReportEventsDirectly are enabled should current data always be added to the data array in the json before (or after) the event data.
2. Is the FD required to set the reason code for the current data to CURRENT ?

[davisonm]

Discussed in meeting of 15/06/2026. No dsolution determined. Decided to leave ticket open. The possibility of dropping the flags could be considered.