Skip to content

Add section addressing PII in schemas #168

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

Merged
merged 3 commits into from
Jun 22, 2023
Merged

Conversation

decentralgabe
Copy link
Collaborator

@decentralgabe decentralgabe commented Jun 20, 2023

fixes #166


Preview | Diff

index.html Outdated
</p>
<p>
Implementers are strongly advised to avoid constructing schemas with any personally
identifiable information.
Copy link
Collaborator

Choose a reason for hiding this comment

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

might be good to comment on "example" data here... make sure that "example" data is synthetic.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm hesitant to add an example to will such a monstrosity into the world, like

{
  "$id": "test-id",
  "type": "object"
  "properties": {
     "999-432-4819": { "type": "string" }
  }
}

where 999-432-4819 is someones SSN

Co-authored-by: Andres Uribe <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
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.

Add language around not including PII or sensitive information in JSON Schemas
4 participants