Fix minor formatting issues, expand acronyms.

privacy.html

@@ -123,10 +123,10 @@ <h1>Privacy Analysis</h1>
       <section>
         <h2>Does this specification deal with personally-identifiable information?</h2>
         <p>
-Yes. The properties inside Verifiable Claims are PII
+Yes. The properties inside Verifiable Claims are Personally Identifiable Information (PII).
         </p>
         <p>
-Recommendation. None as the specification makes this clear.
+Recommendation: None as the specification makes this clear.
         </p>
       </section>
 
@@ -136,7 +136,7 @@ <h2>Does this specification deal with high-value data?</h2>
 Potentially yes. The specification places no restrictions on what data can be placed in a Verifiable Claim, but it could be highly sensitive personal data.
         </p>
         <p>
-Recommendation.  Protocols that carry Verifiable Claims should always encrypt the Verifiable Claim payload. In addition, Verifiable Claims that contain highly sensitive personal data should have that data encrypted inside the Verifiable Claim, so that any entity that captures the Verifiable Claim is not able to see the sensitive information.
+Recommendation:  Protocols that carry Verifiable Claims should always encrypt the Verifiable Claim payload. In addition, Verifiable Claims that contain highly sensitive personal data should have that data encrypted inside the Verifiable Claim, so that any entity that captures the Verifiable Claim is not able to see the sensitive information.
         </p>
       </section>
 
@@ -146,7 +146,7 @@ <h2>Does this specification introduce new state for an origin that persists acro
 Not of itself no, as the specification only specifies a data structure. However, protocols that use this specification may introduce new state.
         </p>
         <p>
-Recommendation. None
+Recommendation: None
         </p>
       </section>
 
@@ -156,7 +156,7 @@ <h2>Does this specification expose persistent, cross-origin state to the web?</h
 Yes. Verifiable Claims contain a random though potentially persistent identifier of the subject. This is passed between the issuer and the inspector. Consequently collusion between them could identify the subject to the inspector, even though the Verifiable Claim itself does not. This is because in many cases the issuer will know the complete identity of the subject, even if the Verifiable Claim only contains a small proportion of it (such as age).
         </p>
         <p>
-Recommendation. The subject should limit the distribution of Verifiable Claims containing the same PId to a minimal number of origins. The subject should obtain Verifiable Claims with different PId to send to different origins wherever possible.
+Recommendation: The subject should limit the distribution of Verifiable Claims containing the same PId to a minimal number of origins. The subject should obtain Verifiable Claims with different PId to send to different origins wherever possible.
         </p>
       </section>
 
@@ -166,7 +166,7 @@ <h2>Does this specification expose any other data to an origin that it doesn’t
 Yes. It is the purpose of Verifiable Claims to present identity attributes of the subject to the inspector. Note however that this is always with the full consent of the subject, except in the special case where the holder is not the subject. In this latter case the holder must be authorized to present this information to the inspector, otherwise the inspector should reject it.
         </p>
         <p>
-Recommendation. Inspectors should only accept Verifiable Claims from subjects or from holders who are authorized to present them to the inspector.
+Recommendation: Inspectors should only accept Verifiable Claims from subjects or from holders who are authorized to present them to the inspector.
         </p>
       </section>
 
@@ -176,7 +176,7 @@ <h2>Does this specification enable new script execution/loading mechanisms?</h2>
 Not of itself no, as the specification only specifies a data structure. However, protocols that use this specification may enable script loading.
         </p>
         <p>
-Recommendation. None
+Recommendation: None
         </p>
       </section>
 
@@ -186,7 +186,7 @@ <h2>Does this specification allow an origin access to a user’s location?</h2>
 Yes. Verifiable Claims may contain location information such as a subject’s home address, phone number, or current postal address.
         </p>
         <p>
-Recommendation. None.
+Recommendation: None.
         </p>
       </section>
 
@@ -196,7 +196,7 @@ <h2>Does this specification allow an origin access to sensors on a user’s devi
 Not of itself no, as the specification only specifies a data structure. However, protocols that use this specification may enable access to sensors on a user’s device.
         </p>
         <p>
-Recommendation. None.
+Recommendation: None.
         </p>
       </section>
 
@@ -206,7 +206,7 @@ <h2>Does this specification allow an origin access to aspects of a user’s loca
 Not of itself no, as the specification only specifies a data structure. However, protocols that use this specification may enable an origin to access aspects of a user’s local computing environment.
         </p>
         <p>
-Recommendation. None.
+Recommendation: None.
         </p>
       </section>
 
@@ -216,7 +216,7 @@ <h2>Does this specification allow an origin access to other devices?</h2>
 Not of itself no, as the specification only specifies a data structure. However, protocols that use this specification may enable an origin to access other devices e.g. to move a Verifiable Claim from one device to another.
         </p>
         <p>
-Recommendation. None.
+Recommendation: None.
         </p>
       </section>
 
@@ -226,7 +226,7 @@ <h2>Does this specification allow an origin some measure of control over a user
 Not of itself no, as the specification only specifies a data structure. However, protocols that use this specification may enable an origin some measure of control over a user agent’s native UI.
         </p>
         <p>
-Recommendation. None.
+Recommendation: None.
         </p>
       </section>
 
@@ -236,7 +236,7 @@ <h2>Does this specification expose temporary identifiers to the web?</h2>
 Potentially yes. The subject’s ID in a Verifiable Claim could be a temporary identifier that is not stored permanently anywhere.
         </p>
         <p>
-Recommendation. Verifiable Claims should be encrypted during transfer to avoid their contents being snooped.
+Recommendation: Verifiable Claims should be encrypted during transfer to avoid their contents being snooped.
         </p>
       </section>
 
@@ -253,17 +253,17 @@ <h2>How should this specification work in the context of a user agent’s "incog
 This specification only presents a data model. However protocols that use this specification should be able to work in incognito mode.
         </p>
         <p>
-Recommendation. None.
+Recommendation: None.
         </p>
       </section>
 
       <section>
         <h2>Does this specification persist data to a user’s local device?</h2>
         <p>
-The overall life cycle of Verifiable Claims envisages that they are stored persistently on the user’s local device or on a remote device under the user’s control. However, Verifiable Claims on their own, if captured by a hostile entity, should not be of any value to it, except in so far as the Verifiable Claim may potentially reveal a small amount of PII about the subject.
+The overall life cycle of Verifiable Claims envisages that they are stored persistently on the user’s local device or on a remote device under the user’s control. However, Verifiable Claims on their own, if captured by a hostile entity, should not be of any value to it, except in so far as the Verifiable Claim may potentially reveal a small amount of Personally Identifiable Information (PII). about the subject.
         </p>
         <p>
-Recommendation. Verifiable Claims should be encrypted during storage to prevent them being stolen by an attacker
+Recommendation: Verifiable Claims should be encrypted during storage to prevent them being stolen by an attacker
         </p>
       </section>
 
@@ -273,7 +273,7 @@ <h2>Does this specification have a "Security Considerations" and "Privacy Consid
 Yes.
         </p>
         <p>
-Recommendation. Ensure they are good enough.
+Recommendation: Ensure they are good enough.
         </p>
       </section>
 
@@ -283,7 +283,7 @@ <h2>Does this specification allow downgrading default security characteristics?<
 No. The specification simply defines a data structure and a signature field.
         </p>
         <p>
-Recommendation. None
+Recommendation: None
         </p>
       </section>