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
Problem
Having resources with URIs of type “/projects/semapps” is nice for the developer, but poses a number of problems:
It links the resource to an LDP container and prevents this container from being renamed/deleted.
It identifies the resource, whereas we'd like only those who can read it to know what it contains.
Proposed solution
Add an option to the LdpService so that all resources are created on the base URL (baseUrl) of the LDP server. When a resource is POSTed into a container, it is attached to the container. Nothing in the LDP spec prevents this from happening. The only requirement is that the URI of the newly created resource be returned.
This option would also ignore the “Slug” header.
To prevent the root container from having to display all LDP server resources, do not attach resources to the root container.
Translated with DeepL.com (free version)
The text was updated successfully, but these errors were encountered:
srosset81
changed the title
LDP service: option pour ne plus mettre de path/slug aux ressources
LDP service: option to remove path/slug from resources
May 6, 2024
Problem
Having resources with URIs of type “/projects/semapps” is nice for the developer, but poses a number of problems:
It links the resource to an LDP container and prevents this container from being renamed/deleted.
It identifies the resource, whereas we'd like only those who can read it to know what it contains.
Proposed solution
Add an option to the LdpService so that all resources are created on the base URL (baseUrl) of the LDP server. When a resource is POSTed into a container, it is attached to the container. Nothing in the LDP spec prevents this from happening. The only requirement is that the URI of the newly created resource be returned.
This option would also ignore the “Slug” header.
To prevent the root container from having to display all LDP server resources, do not attach resources to the root container.
Translated with DeepL.com (free version)
The text was updated successfully, but these errors were encountered: