Purpose field for claims requests and revving of policy_url
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 3
- Avg merge
- 20h 14m
- Merged PRs (30d)
- 1
Description
Originally submitted by Nat (Nat Sakimura) on 2019-09-12
Currently, we are relying on policy_url for the purpose statement for the claims request.
We have come some distance since we have defined it and the trend is to making it possible to state per claim purposes when needed. (see for example ISO/IEC 29184).
It might be a good time to consider something like:
{
"email":
{
"essential": true,
"purpose":"to send receipt",
"example":"aliceexample.com"
}
}
Bitbucket status: open
Bitbucket origin: issue 1108
Contributor guide
No contributing guide indexed for this repository
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
Begin with the claims request and policy_url behavior described in the issue. Compare the proposed per-claim purpose JSON example with ISO/IEC 29184, then define the scope for revving policy_url and record what constitutes an agreed specification change.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100