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

Revise Considerations section #21

Open
csarven opened this issue Mar 29, 2023 · 2 comments
Open

Revise Considerations section #21

csarven opened this issue Mar 29, 2023 · 2 comments

Comments

@csarven
Copy link
Member

csarven commented Mar 29, 2023

Re #considerations

Privacy considerations have been voiced in the past

No need to say that.

regarding the visibility of different data types in the Public Type Index Document. One can potentially deduce the type of data a WebID owner possesses on their storage.

This can use some guidance, e.g.:
"
As the Public Type Index document is intended to be publicly readable, users are advised to only include information that correspond with the kind of data they make readable on their storage. Similarly, users are advised to move information they consider to be sensitive to Private Type Indexes. As such applications are encouraged to inform users when writing information to public or private type indexes and what that entails.
"

In addition to Privacy Considerations, consider adding subsections along the lines of those in https://solidproject.org/TR/protocol#considerations .

@timea-solid
Copy link
Member

timea-solid commented Apr 9, 2023

@csarven
Why no mention:

Privacy considerations have been voiced in the past

No need to say that.

I would not expect this to be the case if not mentioned. Or do you want me to document the considerations further?

@csarven
Copy link
Member Author

csarven commented Jun 1, 2023

That particular start of the sentence in the privacy considerations is filler text because everything in the specification could be said to have been "voiced in the past". Remove it. Expand on the considerations, turn it around, guide / advise on the actual cases/scenarios. Use the one I provided in quotes as a starter and add to it or rewrite it as you see fit.

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

No branches or pull requests

2 participants