Re: Use cases - friending

On 21 Sep 2014, at 18:56, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote:

> On 09/21/2014 06:43 PM, henry.story@bblfish.net wrote:
>> 
>> On 21 Sep 2014, at 18:29, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote:
>> 
>>> On 09/21/2014 05:21 PM, Evan Prodromou wrote:
>>>> On 14-09-20 01:30 PM, ☮ elf Pavlik ☮ wrote:
>>>> We have a lot of use cases listed here:
>>>> 
>>>> https://www.w3.org/wiki/Socialwg/Use_cases
>>> "Friending: As a user on a social network, I would like to add other
>>> social network users to my friends list, and vice versa, as a basis for
>>> further interaction."
>>> 
>>> maybe we could fiddle with that all together? :)
>>> 
>>> next week i would like to export lists of my friendships and followings
>>> from twitter, facebook and google+, then publish it on my independent
>>> website: https://github.com/elf-pavlik/webprofiled/issues/5
>>> 
>>> for now NOT trying to handle friending/following interaction itself but
>>> just publish who i know and who knows me! plus maybe publishing later in
>>> my personal feed activity about establishing such new relationships
>>> 
>>> i plan to use JSON-LD + schema.org vocab + hydra:Collection. while
>>> working on that i could try to compare it with how other people here do
>>> it with Microformats, FOAF, AS2.0 Collections etc.
>> 
>> That seems like a very good use case. 
>> 
>> What is needed is just a way to notify someone - given their WebID [1] -
>> that one has added them to one's list of friends with a message.
>> It is really easy to specify a very simple "protocol" along Web2.0 lines.
>> as described in the paper "Friending on the Social Web"
>>   http://bblfish.net/tmp/2011/05/09/ 
>> But we should now be able to extend this for LDP in a way that would
>> be much more extensible.
>> 
>> The nice thing about LDP is that we don't need to care wether we use JSON-LD
>> or Turtle or even RDF/XML. We can specify this in terms of: 
>> 
>> 1. given a WebID find the messaging LDPC for that WebID - perhaps a specialised
>>    friending Messaging LDPC. 
>> 2. POST a friending graph - what would that look like
>> 
>> That seems to be about it. The person to whome the friend request has been
>> made can then do the same thing symmetrically.
> How about we get some working code deployed with different
> implementations and then focus on comparing them? You would use LPDC +
> FOAF, me for example Schema.org + hydra:Collection, someone else
> Microformats etc.

I don't see how that is going to help to have interoperability,
if we build three implementations that are incompatible. 

What I do see is that we can agree on the use case - which this thread is about -
then on the general data flow, for example the one I described above, and then
we can find people who wish to implement a proposal.

> 
> Since we have statement in
> https://www.w3.org/wiki/Socialwg/Social_syntax_requirements
> *Non-Requirements for a social syntax: Non-JSON encodings*
> and LDP just made JSON-LD a *MUST* could you please share you examples
> with us in JSON-LD instead of Turtle? -
> https://twitter.com/lehors/status/512088825888133120

Well yes, my point was that the syntax of the information is not what
mattered here. At present I still need to get my implementation of LDP
to pass the tests. I was slowed down due to the birth of Anaïs Trinity
on the Sept/10/2014 




But I am back on the ball now....

> 
> Microformats also has JSON serialization so we don't need to deal with
> HTML here - http://microformats.org/wiki/json
> 
> 
> 

Social Web Architect
http://bblfish.net/