[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Social-discuss] The Case for Branching Elgg?
From: |
Story Henry |
Subject: |
Re: [Social-discuss] The Case for Branching Elgg? |
Date: |
Sat, 10 Apr 2010 18:56:31 +0100 |
On 8 Apr 2010, at 13:00, Melvin Carvalho wrote:
> 2010/4/3 Sean Corbett <address@hidden>
>
>> It certainly seems doable and the code base is very nice and
>> straightforward; Ian and I have actually been spending time with it trying
>> to figure out a way to get two Elgg instances we've installed on our school
>> network to "talk to each other." Of course I think there would need to be a
>> lot more work done on it to attain all the goals that we've established, but
>> it would provide a useful basis for development.
>>
>
> I've started fixing up the FOAF in elgg, so that instances can become part
> of the (federated) foaf cloud. You can start to see some of the results
> here:
>
> http://www.foafer.org/?file=http%3A%2F%2Fgnusocial.me%2Fpg%2Fprofile%2Fbblfish%3Fview%3Dfoaf
>
> Right now you can browse from profile to profile, across server boundries.
> To make profile browsing completely federated, I'll need to allow links out
> (links in are already possible).
btw, one thing that could be quite cool, would be to add virtuoso to Elgg
http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/
One could then leave the mysql DB as it is now, and yet have an RDF view on it,
including all the rdf tools one probably needs. I think Virtuoso will be part
of KDE...
Henry
- Re: [Social-discuss] The Case for Branching Elgg?, (continued)
Re: [Social-discuss] The Case for Branching Elgg?, Sean Corbett, 2010/04/03