Re: Getting the Address Book to work with read-write-web servers

On 27 October 2011 14:44, Henry Story <henry.story@bblfish.net> wrote:
> Hello,
>
>   As a way to get the read-write-web started we want to get the simplest and most basic linked and secure social web going.
>
>  The University of Leipzig - who are organising the Linked Data 2 - have the cool address book in Android I mentioned in a previous post here [1], as well as one that works in html5. On the server side we have
>  - Joe Presbrey's data.fm
>  - Alex Bertails scala based read-write-web to which I have just added WebID support (see the webid branch )
>  - others want to join?
>
> So the idea is to make it possible for these servers allow the same address book to do some of the following tasks, without knowing what is on the server:
>
>  1- of course GET foaf, in order to walk the social web
>  2- create a new directory perhaps for a user
>  3- PUT a WebID Profile there (i.e., some public foaf with a public key)
>  4- Be able to update statements in that graph (say when wanting to add a new key)
>  5- Create a non public foaf file
>  6- add access control rules in the right place about that non public foaf file
>  7- be able to notify someone when one is speaking about them - or when one wants to add a friend request
>
>
> So those are some of the things that need to be done. The idea then is that we should be able to put up these servers in different universities, and allow people using the address books to develop their up-to-date social networks.
>
>  So as a starting point, which I am not too satisfied with I have the following test case for read-write-web
> https://dvcs.w3.org/hg/read-write-web/file/9ca474c333e8/src/test/scala/auth/CreateWebIDSpec.scala
>
> Here are some perhaps arbitrary decisions:
>
>  1. POSTing a SPARQL query or update on an rdf resource updates it
>  2. that resource should have a Link: </.meta>; rel=meta so that the client knows where it can update the metada
>    if it is allowed to update it of course
>  3. if that resource is an RDF query then it should be possible to update the access control to it
>
> Btw. in my test cases I made the WebID profile only readable by myself, and was then wondering why I could not access it! :-) The server is using open http access probably and could not itself gain access to that file to test the webid...
>
>   Anyway, I propose we discuss this a bit here, and then have a conf call sometime soon to work out which are the lowest hanging fruits we want to solve first, so that the Address Book people can implement these things, and test them against our implementations.

This is a nice app, but doesnt foaf kind of provide an address book already?

One thing I'd like to see first is to give everyone a semantic inbox.
That would be a place where we can leave each other messages about how
to deliver the read write web step by step.  Eventually this could be
gamified to make it more fun and viral ...

>
>        Henry
>
>
> [1] http://vimeo.com/30014844
> [2] https://dvcs.w3.org/hg/read-write-web/
>
> Social Web Architect
> http://bblfish.net/
>
>
>

Received on Friday, 28 October 2011 21:41:26 UTC