solid / solid/data-interoperability-panel
Problem details
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if another panel would be more suitable but defining error messages in RDF possibly with a specific HTTP headers came up a number of times in the past. That's along the lines of https://github.com/solid/specification/issues/28 and https://github.com/solid/specification/issues/111 . If possible, a generalised solution may benefit both and can be useful in other cases. See also https://github.com/solid/specification/issues/112.
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
Read the related discussions in solid/specification issues 28, 111, and 112, then compare them with the proposed RDF and HTTP-header approach in this issue. A complete result would define an agreed general solution for error messages and explain how it addresses the referenced cases.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100