Merge pull request #1826 from mmccool/resolve-privacy-immutable-id-as…

…-property Resolve privacy-immutable-id-as-property
w3c · May 24, 2023 · 1d1b269 · 1d1b269
2 parents 8a954c9 + 29a72c3
commit 1d1b269
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 6 deletions.
diff --git a/index.html b/index.html
@@ -7364,11 +7364,12 @@ <h5>Immutable Identifiers</h5>
           of the change in identifier when a change is made.
           Note however that some classes of devices, e.g., medical devices,
           may require immutable IDs by law in some jurisdictions.
-          <span class="rfc2119-assertion" id="privacy-immutable-id-as-property">
-          Ideally, any required immutable identifiers SHOULD only be 
+          <!-- <span class="rfc2119-assertion" id="privacy-immutable-id-as-property"> -->
+          Ideally, any required immutable identifiers should only be 
           made available via affordances, such as a property, whose value can
           only be obtained after appropriate authentication and
-          authorization, and managed separately from the TD identifier.</span>
+          authorization, and managed separately from the TD identifier.
+          <!-- </span> -->
           If it is necessary to use an immutable identifier as the TD identifier, 
           extra attention should be paid to secure 
           access to files, such as Thing Descriptions, containing such

diff --git a/index.template.html b/index.template.html
@@ -6073,11 +6073,12 @@ <h5>Immutable Identifiers</h5>
           of the change in identifier when a change is made.
           Note however that some classes of devices, e.g., medical devices,
           may require immutable IDs by law in some jurisdictions.
-          <span class="rfc2119-assertion" id="privacy-immutable-id-as-property">
-          Ideally, any required immutable identifiers SHOULD only be 
+          <!-- <span class="rfc2119-assertion" id="privacy-immutable-id-as-property"> -->
+          Ideally, any required immutable identifiers should only be 
           made available via affordances, such as a property, whose value can
           only be obtained after appropriate authentication and
-          authorization, and managed separately from the TD identifier.</span>
+          authorization, and managed separately from the TD identifier.
+          <!-- </span> -->
           If it is necessary to use an immutable identifier as the TD identifier, 
           extra attention should be paid to secure 
           access to files, such as Thing Descriptions, containing such