D-042 Is a commitment's flight start and end a calendar date, as the examples write them, or a point in time?

What we propose

A point in time, a Timestamp, as the offer window's valid_from and valid_until are.

As written

A commitment's flight_start and flight_end are calendar dates, such as 2026-10-06, as the examples write them. The text names no time zone that reads them.

The as-written variant takes the option date. Switch the type map to As written to see it.

Options

• timestamp Chosen

  A point in time, a Timestamp, as the offer window's valid_from and valid_until are.

• date As written

  A calendar date, YYYY-MM-DD, as the examples write it.

Why

The text gives flight_start and flight_end no type, and every example writes a calendar date, such as 2026-10-06. A calendar date names no instant until a time zone reads it (D-038), and no clock the specification has reads a flight: main has none, and the open PRs' time_zone reads only the daypart and the frequency cap's period. So two parties can disagree on when a flight starts. One form for every point in time also lets a receiver compare a flight with the offer window, valid_from and valid_until, which are Timestamps. The schema departs from the examples: a flight starts and ends at a date-time with an offset.

What we ask the specification to change

Write a commitment's flight_start and flight_end as RFC 3339 date-times, as valid_from and valid_until are, such as 2026-10-06T00:00:00-04:00. The examples write calendar dates, which name no instant until a time zone reads them.

The specification lines it rests on

Each line is quoted as the record pins it. Expand an item to read the quote.

main

• § 5.6.1, the commitment.flight_start key row L294 at 44dfaaf

  flight_start | REQUIRED | The buyer's campaign start. Distinct from valid_from

• § 5.6.1, the commitment.flight_end key row L295 at 44dfaaf

  flight_end | REQUIRED | The buyer's campaign end. Distinct from valid_until

With the open PRs

• § 5.6.1, the commitment.flight_start key row L287 on main at 981a74e

  flight_start | REQUIRED | The buyer's campaign start. Distinct from valid_from

• § 5.6.1, the commitment.flight_end key row L288 on main at 981a74e

  flight_end | REQUIRED | The buyer's campaign end. Distinct from valid_until

Examples that follow the text, not this change

What it shapes

main: Commitment.flight_end, Commitment.flight_start

With the open PRs: Commitment.flight_end, Commitment.flight_start