forked from w3c/encrypted-media
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix w3c#353: Remove at-risk list from SOTD.
- Loading branch information
Showing
2 changed files
with
4 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -883,7 +883,7 @@ | |
| <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/W3C-ED"> | ||
| <!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--> | ||
| <link rel="canonical" href="https://www.w3.org/TR/encrypted-media/"> | ||
| <meta name="generator" content="ReSpec 6.1.0"> | ||
| <meta name="generator" content="ReSpec 6.0.2"> | ||
| <script id="initialUserConfig" type="application/json"> | ||
| { | ||
| "specStatus": "ED", | ||
|
|
@@ -1375,7 +1375,7 @@ | |
| } | ||
| </script> | ||
| </head> | ||
| <body class="h-entry toc-inline" role="document" id="respecDocument"> | ||
| <body class="h-entry" role="document" id="respecDocument"> | ||
| <div class="head" role="contentinfo" id="respecHeader"> | ||
| <p> | ||
| <a class="logo" href="https://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" alt="W3C"></a> | ||
|
|
@@ -1450,19 +1450,6 @@ <h2 id="h-sotd" resource="#h-sotd"><span property="xhv:role" resource="xhv:headi | |
| <p>The working group maintains <a href="https://github.com/w3c/encrypted-media/issues">a list of all bug reports that the editors have not yet tried to address</a>; there are also open bugs in the <a href="https://www.w3.org/brief/MjY5">previous bug tracker</a>. This draft highlights some of the pending issues that are still to be discussed in the working group. No decision has been taken on the outcome of these issues including whether they are valid.</p> | ||
| <p>Implementors should be aware that this specification is not stable. <strong>Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways.</strong> Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should join the mailing list mentioned below and take part in the discussions.</p> | ||
|
|
||
| <p>The following features are <strong>at risk</strong> and may be removed:</p> | ||
| <ul> | ||
| <li> | ||
| <p>The | ||
| <a def-id="persistent-usage-record-session" class="externalDFN"></a> session type and the related | ||
| <a def-id="media-key-session-destroyed-algorithm" class="externalDFN"></a> algorithm.</p> | ||
| </li> | ||
| <li> | ||
| <p>Setting the <var>media element</var>'s <code><a href="https://www.w3.org/TR/html5/embedded-content-0.html#dom-media-readystate">readyState</a></code> value based on key availability in the <a href="#wait-for-key">Wait for Key</a> and <a href="#resume-playback">Attempt to Resume Playback If Necessary</a> algorithms.</p> | ||
| </li> | ||
| </ul> | ||
|
|
||
|
|
||
| <p> | ||
| This document was published by the <a href="https://www.w3.org/html/wg/">HTML Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to | ||
| <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, | ||
|
|
@@ -6844,7 +6831,8 @@ <h3 id="h-user-tracking" resource="#h-user-tracking"><span property="xhv:role" r | |
| <h4 id="h-concerns-1" resource="#h-concerns-1"><span property="xhv:role" resource="xhv:heading"><span class="secno">11.4.1 </span>Concerns</span> | ||
| </h4> | ||
| <p><em>This section is non-normative.</em></p> | ||
| <p>A third-party host (or any entity, such as an advertiser, capable of getting content distributed to multiple sites) could use a <a href="#distinctive-identifier">Distinctive Identifier</a> or persistent data, including licenses, keys, key IDs, or <a href="#record-of-license-destruction">records of license destruction</a>, stored by or on behalf of the <a href="#cdm">CDM</a> to track a user across multiple sessions (including across <a href="https://www.w3.org/TR/html5/browsers.html#origin-0">origins</a> and <a href="#browsing-profile">browsing profiles</a>), building a profile of the user's activities or interests. Such tracking would undermine the privacy protections provided by the rest of the web platform and could, for example, enable highly-targeted advertising not otherwise possible. In conjunction with a site that is aware of the user's real identity (for example, a content provider or e-commerce site that requires authenticated credentials), this could allow oppressive groups to target individuals with greater accuracy than in a world with purely anonymous web usage. | ||
| <p>A third-party host (or any entity, such as an advertiser, capable of getting content distributed to multiple sites) could use a <a href="#distinctive-identifier">Distinctive Identifier</a> or persistent data, including licenses, keys, key IDs, or | ||
| <a href="#record-of-license-destruction">records of license destruction</a>, stored by or on behalf of the <a href="#cdm">CDM</a> to track a user across multiple sessions (including across <a href="https://www.w3.org/TR/html5/browsers.html#origin-0">origins</a> and <a href="#browsing-profile">browsing profiles</a>), building a profile of the user's activities or interests. Such tracking would undermine the privacy protections provided by the rest of the web platform and could, for example, enable highly-targeted advertising not otherwise possible. In conjunction with a site that is aware of the user's real identity (for example, a content provider or e-commerce site that requires authenticated credentials), this could allow oppressive groups to target individuals with greater accuracy than in a world with purely anonymous web usage. | ||
| </p> | ||
|
|
||
| <p>User- or client-specific information that could be obtained via implementations of the APIs in this specification includes:</p> | ||
|
|
||