You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
"
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.
Re #considerations
No need to say that.
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 .
The text was updated successfully, but these errors were encountered: