Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #231: Ensure both individualization types produce compliant Distinctive Identifiers #235

Merged
merged 4 commits into from
Jun 9, 2016

Conversation

ddorwin
Copy link
Contributor

@ddorwin ddorwin commented Jun 9, 2016

Also renames the two types to more accurately reflect their behavior.

…stinctive Identifiers

Also renames the two types to more accruately reflect their behavior.
@@ -3841,11 +3835,14 @@
<li><p>MUST NOT be passed to or through the application via these APIs.</p></li>
<li><p>MUST be sent to a URL selected independently of any origin and application.</p></li>
</ul>
<p>
Implementations MUST NOT expose, even in encrypted form, <a def-id="origin">origin(s)</a>-, origin- or application-specific information, or values that are <a def-id="associable"></a> with orign(s) to centralized servers since this could create a central record of all origins visited by a user or device.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/orign(s)/origin(s)/

@mwatson2
Copy link
Contributor

mwatson2 commented Jun 9, 2016

LGTM with 2 typos.

@ddorwin ddorwin merged commit 67d2e70 into w3c:gh-pages Jun 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants