Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

say something about trailing slashes #49

Closed
michielbdejong opened this issue May 23, 2019 · 2 comments · Fixed by #54
Closed

say something about trailing slashes #49

michielbdejong opened this issue May 23, 2019 · 2 comments · Fixed by #54

Comments

@michielbdejong
Copy link
Contributor

In https://www.w3.org/TR/ldp-bp/#include-a-trailing-slash-in-container-uris it's recommended to refer to a container with a trailing slash, but i think it can be expected of a server to add that trailing slash if it's missing?
For instance I I write:

<#owner> acl:accessTo <https://mypod.com/foo> .

in https://mypod.com/foo/.acl then the server should interpret that as

<#owner> acl:accessTo <https://mypod.com/foo/> .
@michielbdejong
Copy link
Contributor Author

remark from @timbl in weekly meeting: if there's no trailing slash, then there's no match

@csarven
Copy link
Member

csarven commented May 28, 2019

Specs ought to develop independently, and should not be based on a particular implementation or convention. That goes for WAC not having knowledge or dependency on LDP or expect that WAC should follow a specific URI Template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants