-
Notifications
You must be signed in to change notification settings - Fork 584
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
Privacy & Security #399
Privacy & Security #399
Conversation
Signed-off-by: Day, Jem <[email protected]>
spec.md
Outdated
* Data | ||
|
||
Domain specific [data](#data) *SHOULD* be encoded to restrict visibility to | ||
trusted parties. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may need to add something like: The exact mechanism by which it is encoded is out of scope of this specification.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does "encoded" mean here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've changed the wording - please take another look.
@clemensv I was simply trying to avoid the word 'encrypt' as i felt that was to loaded.
Minor edits, but overall I like the direction it's headed - thanks! |
Signed-off-by: Day, Jem <[email protected]>
Signed-off-by: Day, Jem <[email protected]>
LGTM Can you add this new section to the TOC? |
Signed-off-by: Day, Jem <[email protected]>
Still LGTM |
Signed-off-by: Day, Jem <[email protected]>
Approved on the 3/21/2019 call - with the s/encode/encrypt/ change. Possible future PRs may wordsmith this further. |
Signed-off-by: Day, Jem [email protected]