Express "identifiable information" (non)normatively
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
(Derived from https://github.com/solid/specification/pull/13/files#r305292422 )
The Privacy Considerations section has a subsection for "Identifiable Information".
We need to determine what's deemed to be identifiable information and express that in terms of (non)normative text... and so we also know what should be in a test suite.
Then we can revisit statements like:
In order to prevent leakage of non-resource data, error responses SHOULD NOT contain identifiable information.
So, if we know the set or categories for identifiable information, then the recommendation could switch to MUST NOT, unless we also cover exceptions. I presume that there are no need to explore exceptions to allow the inclusion of identifiable information in error responses.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Privacy Considerations section and its “Identifiable Information” subsection. Define the categories in normative and non-normative terms, determine what the test suite should cover, and revisit whether the error-response recommendation should be strengthened from SHOULD NOT to MUST NOT, including any justified exceptions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100