Discoverability of supported update methods on resources without read permission
@csarven ya está trabajando en esto.
Desde el 31/1/2023.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
This is not necessarily an issue, but more of a request for clarification inspired by an actual use case - whether misuse or valid, I do not know, hence why I am asking. If this is not the correct place to ask, I would appreciate any pointers to the appropriate location.
Are there any guidelines in the specification for how a client can discover supported update methods (or, in general, any write/delete/append support) on resources on a Solid server, when the client has write or append permissions but no read permission?
An example use case could maybe be an inbox, to which everyone has append permission but only the owner has read permission. So whenever a client wants to write to that inbox, the client would either know that the server supports specific types or updates (or updates in general) or just blindly send some form of update and hope it works.
Is there an existing way for a client to determine whether they can do updates on a resource without read permissions? Or if there is no way for a client to do that (without trying an update first), could something be done with response headers to indicate support for updates without read permission?
I tried to look through the open issues, but did not find anything addressing that.
Thank you in advance for your time, and apologies if this has been answered before.
- Lenguaje dominante
- HTML
- Estrellas
- 563
- Forks
- 112
- Merge medio
- 4 d 21 h
- PR fusionados (30 d)
- 3
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de solid/specification
-
new-work-item
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
solid/specification#806 · 11 comentarios · 4 reacciones ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
solid/specification#804 · 9 comentarios · 2 reacciones ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
solid/specification#799 · 1 reacción ·
-
topic: resource access
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
solid/specification#797 · 4 comentarios · 2 reacciones ·
-
End-to-End Encryption (E2EE)Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
solid/specification#788 · 4 comentarios · 1 reacción ·