Issue: Discrepancy in revision times for content published in the DD4T format

Content published in the DD4T content model may reflect an incorrect revision time stamp after it is converted to R2 due to missing time zone information in the DD4T model.

Problem: The DD4T data model does not include a time zone in the revision date and time for published content. The R2 data model, on the other hand, does include the time zone, and the Model Service includes this information in the content model.

When the Model Service Converter finds content that was published to the DD4T format and proceeds to convert it to the R2 model, the converter must add the time zone because there is none in the original DD4T version. As a default, the Model Service uses the time zone of the local machine where it is running, and this can result in a shift in the time zone.

Note that the Model Service uses the ISO 8601 standard for expressing dates and time, and time zones are relative to UTC (Coordinated Universal Time).

Solution: Be aware that the revision times indicated in R2 content models may be different from the revision times for the same content previously rendered in the DD4T model.