W3C home > Mailing lists > Public > public-rww@w3.org > October 2011

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

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 31 Oct 2011 09:36:26 +0100
Cc: Sebastian Dietzold <tramp@informatik.uni-leipzig.de>, Alexandre Bertalis <alexandre@bertails.org>, Joe Presbrey <presbrey@csail.mit.edu>, Read-Write-Web <public-rww@w3.org>
Message-Id: <916F49AC-4258-4762-AFEF-58C233D0ECF8@bblfish.net>
To: Melvin Carvalho <melvincarvalho@gmail.com>

On 29 Oct 2011, at 00:02, Melvin Carvalho wrote:

> On 28 October 2011 23:46, Henry Story <henry.story@bblfish.net> wrote:
>> On 28 Oct 2011, at 23:40, Melvin Carvalho wrote:
>>> 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
>>> [snip[
>>> This is a nice app, but doesnt foaf kind of provide an address book already?
>> foaf provides a data structure. It is not an application.
>>> 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 ...
>> That can be done too. Perhaps that is what the data.fm is about. That's what the address
>> book is mean to be able to write to.
>> An address book that can do new pings to people seems like a fun and easy
>> thing to do, is cool because it works in the cell phone, and there are a few
>> of of our projects this could work together with.
> You're assuming that everyone has a semantically enabled address book.

No not at all. It is just a real application that one can use to think through the issues
with something fun at the end to show. It's a use case if you will, with real working code,
like some of the other projects we have in the WebID space.

In the end we should be able to specify these with simple test suites using curl. 

> I think we first need a simple messaging system, then to build a mini
> social net.

That's just another plan. Sounds good too. But I am focusing on the address book right now,
since we have some code and people who are interested in it.

> Then apps like an address book, imho.
> You can, of course, try it the other way round, but then you have to
> persuade enough others to use the same system, which can sometimes be
> as tricky as coding the app itself! :)

Are you saying that an address book app that does PUT, POST of RDF to data.fm won't work
because it's an address book app? I don't understand.


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

Social Web Architect
Received on Monday, 31 October 2011 08:37:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:39:55 UTC