Fix w3c#272: Individualization clarifications

encrypted-media-respec.html

@@ -3911,13 +3911,16 @@ <h4>Individualization</h4>
             The resulting identifier(s) MUST be <a def-id="non-associable-by-application"></a> and <a href="#uses-distinctive-identifiers">use of them</a> MUST only be exposed to a <a href="#per-origin-identifiers">single origin</a>.
             This process MAY be performed multiple times, such as after identifier(s) are <a href="#allow-identifiers-cleared">cleared</a>.
           </p>
-          <p>This process MUST be performed either <a href="#direct-individualization">directly by the user agent</a> or <a href="#app-assisted-individualization">through the application</a>.
+          <p>This process MUST be performed either <a href="#direct-individualization">directly by the user agent</a> or <a href="#app-assisted-individualization">through the application</a> depending on the CDM implementation.
             The mechanisms, flow, and restrictions for the two types of individualization are different, as described in the following sections.
           </p>
 
           <section id="direct-individualization">
             <h5>Direct Individualization</h5>
-            <p>Direct Individualization is performed between the <a def-id="cdm"></a> and an origin- and application-independent server.
+            <p>
+              Direct Individualization is performed between the <a def-id="cdm"></a> and an origin- and application-independent server.
+              Although the server is origin-independent, the result of the individualization enables the CDM to provide origin-specific identifiers per the other
+              requirements of this specification.
               The process MUST be performed by the user agent and MUST NOT use these APIs.
             </p>
             <p class="note">For example, such a process may initialize a client device and/or obtain a <a href="#per-origin-identifiers">per-origin</a> <a href="#allow-identifiers-cleared">clearable</a> identifier by communicating with a pre-determined server hosted by the user agent or CDM vendor, possibly <a href="#uses-distinctive-permanent-identifiers">using Distinctive Permanent Identifier(s)</a> or other <a href="#permanent-identifier">Permanent Identifier(s)</a> from the client device.

index.html

@@ -1208,7 +1208,7 @@
       <a class="logo" href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" alt="W3C"></a>
     </p>
     <h1 class="title p-name" id="title" property="dcterms:title">Encrypted Media Extensions</h1>
-    <h2 id="w3c-editor-s-draft-19-july-2016"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time property="dcterms:issued" class="dt-published" datetime="2016-07-19">19 July 2016</time></h2>
+    <h2 id="w3c-editor-s-draft-20-july-2016"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time property="dcterms:issued" class="dt-published" datetime="2016-07-20">20 July 2016</time></h2>
     <dl>
       <dt>This version:</dt>
       <dd><a class="u-url" href="https://w3c.github.io/encrypted-media/">https://w3c.github.io/encrypted-media/</a></dd>
@@ -6632,12 +6632,13 @@ <h4 id="h-privacy-individualization" resource="#h-privacy-individualization"><sp
         <p>
           Identifiers, especially <a href="#distinctive-identifier">Distinctive Identifiers</a>, are sometimes generated or obtained via a process called individualization or provisioning. The resulting identifier(s) <em class="rfc2119" title="MUST">MUST</em> be <a href="#non-associable-by-application">non-associable by applications</a> and <a href="#uses-distinctive-identifiers">use of them</a> <em class="rfc2119" title="MUST">MUST</em> only be exposed to a <a href="#per-origin-identifiers">single origin</a>. This process <em class="rfc2119" title="MAY">MAY</em> be performed multiple times, such as after identifier(s) are <a href="#allow-identifiers-cleared">cleared</a>.
         </p>
-        <p>This process <em class="rfc2119" title="MUST">MUST</em> be performed either <a href="#direct-individualization">directly by the user agent</a> or <a href="#app-assisted-individualization">through the application</a>. The mechanisms, flow, and restrictions for the two types of individualization are different, as described in the following sections.
+        <p>This process <em class="rfc2119" title="MUST">MUST</em> be performed either <a href="#direct-individualization">directly by the user agent</a> or <a href="#app-assisted-individualization">through the application</a> depending on the CDM implementation. The mechanisms, flow, and restrictions for the two types of individualization are different, as described in the following sections.
         </p>
 
         <section id="direct-individualization" typeof="bibo:Chapter" resource="#direct-individualization" property="bibo:hasPart">
           <h5 id="h-direct-individualization" resource="#h-direct-individualization"><span property="xhv:role" resource="xhv:heading"><span class="secno">11.4.2.1 </span>Direct Individualization</span></h5>
-          <p>Direct Individualization is performed between the <a href="#cdm">CDM</a> and an origin- and application-independent server. The process <em class="rfc2119" title="MUST">MUST</em> be performed by the user agent and <em class="rfc2119" title="MUST NOT">MUST NOT</em> use these APIs.
+          <p>
+            Direct Individualization is performed between the <a href="#cdm">CDM</a> and an origin- and application-independent server. Although the server is origin-independent, the result of the individualization enables the CDM to provide origin-specific identifiers per the other requirements of this specification. The process <em class="rfc2119" title="MUST">MUST</em> be performed by the user agent and <em class="rfc2119" title="MUST NOT">MUST NOT</em> use these APIs.
           </p>
           <div class="note">
             <div class="note-title marker" aria-level="6" role="heading" id="h-note134"><span>Note</span></div>