[OpenID] Finally the Shit has hit the fan!

[Phillip Hallam-Baker]

You don't have to buy the whole semantic web story to use or implement FOAF.

I agree that it is a very important technology that we need to look
at. But there is one problem that Linked In has solved that I do not
know how to solve in FOAF-world and that is spam control.

I am absolutely not saying that because I want to dump on FOAF, its
because that is a problem that has to be solved if FOAF can genuinely
replace what I get from LinkedIn and at the moment I can't see any way
I can make that work without central mediation that I find really
convincing.


On Mon, Jun 7, 2010 at 12:51 PM, Story Henry <henry.story at bblfish.net> wrote:
>
> On 7 Jun 2010, at 18:42, Steven Livingstone-Perez wrote:
>
>> The idea in principal appeals but a lot seems to be dependent on browser
>> vendor support & OpenID in the browser should really have been (and should
>> still be [1]) a no brainer for the browser vendors - I anticipate the same
>> level of "uptake" by them for this.
>
> It already works in the browser, and has for years. The problem is that most people here don't want to look at the solution, because of fear of the semantic web it seems, or some such (not sure).
>
>  You can see it working in this home made video
>
>     http://www.youtube.com/watch?v=8iZPJBpI2Po&feature=player_embedded
>
>  (I welcome people coming up with better videos)
>  The protocol is detailed here:
>
>     http://esw.w3.org/Foaf+ssl
>
>  There are some small browser improvements that could be made, though it would not take long to convince some of the browsers vendors to make them.
>
> Henry
>
>>
>>
>> In short, until we can get the browsers to put social as a first class
>> citizen (and look how long universal OpenSearch support in the browsers
>> took) we have a battle.
>
> _______________________________________________
> specs mailing list
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs
>



-- 
Website: http://hallambaker.com/