Drupal stores datetime fields in UTC time with no timezone identifier. For instance, for a site in Eastern Time, the datetime 10/31/2017 - 5:30AM will be stored as 2017-10-31T09:30:00

This violates ISO 8601:

If no UTC relation information is given with a time representation, the time is assumed to be in local time

This becomes problematic if data is ever exported from Drupal. For instance, external apps consuming data via JSON API would never expect a datetime formatted like that to be in UTC (unless the hosting site just happened to be in that timezone): #2913941: [PP-1] Fields using the DateTimeIso8601 @DataType are missing an explicit time zone: missing a normalizer

If Drupal is going to store dates in UTC, it should append the timezone to comply with ISO 8601, i.e. 2017-10-31T09:30:00Z

Comments

Dane Powell created an issue. See original summary.

Dane Powell’s picture

Issue summary: View changes
Dane Powell’s picture

Issue summary: View changes
mpdonadio’s picture