W3C home > Mailing lists > Public > public-html-media@w3.org > January 2017

[encrypted-media] Resolve ambiguous and/or contradictory explanations of time

From: ddorwin via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 Jan 2017 22:33:49 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-203757259-1485556427-sysbot+gh@w3.org>
ddorwin has just created a new issue for 
https://github.com/w3c/encrypted-media:

== Resolve ambiguous and/or contradictory explanations of time ==
As discussed in 
https://github.com/w3c/encrypted-media/issues/59#issuecomment-275488967
 and subsuquent comments, the definition of 
[Time](https://w3c.github.io/encrypted-media/#time) is ambiguous 
and/of contradictory. The same is true of references to time elsewhere
 in the spec.

Specific changes include:
1. Change all references to the unofficial ES6 draft to the official 
spec. Specifically, replace 
https://people.mozilla.org/~jorendorff/es6-draft.html#sec-date-objects
 with https://tc39.github.io/ecma262/#sec-time-values-and-time-range.
1. Rely on 
https://tc39.github.io/ecma262/#sec-time-values-and-time-range, 
providing only clarifying text when necessary. Perhaps, highlight the 
important parts in a non-normative Note to avoid redundantly and 
potentially confusingly defining time.
1. Ensure references to "Unix time" are removed.
1. Be explicit that time is represented in milliseconds ("millisecond 
accuracy" and "instants... it can represent... every millisecond" are 
not sufficiently explicit).
1. In algorithms, reference the Time definition rather than defining 
the meaning of the time value in each algorithm. For example, "...let 
expiration time be the [new] expiration time in milliseconds since 01 
January 1970 UTC" is redundant and incomplete.

Please view or discuss this issue at 
https://github.com/w3c/encrypted-media/issues/370 using your GitHub 
account
Received on Friday, 27 January 2017 22:33:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 January 2017 22:33:55 UTC