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
We should create the same or improved user story using HTTP-Signature and the Solid-Client, and then illustrate each case with some runnable code, that allows one to explore every aspect of working with LDP.
The text was updated successfully, but these errors were encountered:
Looking at the the current version of rww-play curl interactions, they seem to go a bit too quickly to something difficult to understand et. PATCH. Better would be to have a story that starts with the simplest. So we can accept that we started with writing one key to the file system by hand (we want to later get rid of even that). Here is a sequence that would go from simple to more complex:
GET a file that is protected eg. /2013/
POST a key there
( this would make more sense if there was a password based auth method by default - so I'll look into that)
use the newly generated key to change the acl ownership rule of the directory using PUT (the acl can nicely be built using banana-rdf's diesel library
create a foaf:Group and make it visible only to members of the group
(the foaf group can be a new file, and so add a link to the card using PATCH )
add new people to the foaf:Group as they come along with PATCHes. Eg. Add timbl.
The rww-play curl interactions wiki page explains SoLiD access control using WebID-TLS authentication.
We should create the same or improved user story using HTTP-Signature and the Solid-Client, and then illustrate each case with some runnable code, that allows one to explore every aspect of working with LDP.
The text was updated successfully, but these errors were encountered: