AWS mediatailor documentation change
Summary
Clarified time format references for HLS/DASH playback
Security assessment
Change provides technical clarification for timestamp handling but does not address security issues or document security features.
Diff
diff --git a/mediatailor/latest/ug/ad-reporting-client-side-ad-tracking-schema.md b/mediatailor/latest/ug/ad-reporting-client-side-ad-tracking-schema.md index d683909ea..e45966a00 100644 --- a//mediatailor/latest/ug/ad-reporting-client-side-ad-tracking-schema.md +++ b//mediatailor/latest/ug/ad-reporting-client-side-ad-tracking-schema.md @@ -246,2 +246,2 @@ Make sure to provide a value. If you don't provide a value, issues can arise. | -`startTime` | The time position, in ISO 8601 seconds format, relative to the beginning of the playback session. The response includes start times for the entire ad avail and for each ad and beacon. | String | `PT9.943S` -`startTimeInSeconds` | The time position, in seconds format, relative to the beginning of the playback session. The response includes start times for the entire ad avail and for each ad and beacon. | Number | `9.943` +`startTime` | The time position, in ISO 8601 seconds format. For HLS, this is relative to the beginning of the playback session. For DASH, this is relative to the manifest's AST (Availability Start Time). The response includes start times for the entire ad avail and for each ad and beacon. | String | `PT9.943S` +`startTimeInSeconds` | The time position, in seconds format. For HLS, this is relative to the beginning of the playback session. For DASH, this is relative to the manifest's AST (Availability Start Time). The response includes start times for the entire ad avail and for each ad and beacon. | Number | `9.943`