[foaf-protocols] using windows to mint web id credentials,

[Kingsley Idehen]

On 11/26/11 8:50 PM, Henry Story wrote:
>
> On 27 Nov 2011, at 00:29, Kingsley Idehen wrote:
>>
>> As you can see, we get the same effect using RDFa or Microdata based 
>> structured data islands within blogspot.com <http://blogspot.com> posts.
>>
>> We don't need to extend a silly syntax war to WebID. Let's keep WebID 
>> in the conceptual realm. It components boil down to:
>
> I Agree, so  let's not spend so much energy then trying to convince 
> Peter, who just produced his first WebId Profile, to  change it, to 
> what is furthermore a  different format for which we don't have 
> parsers? (None of my projects has a parser for them).

I try to provide answers that have a big picture in mind. Its always 
about mass rollout and adoption without friction.

A small group of hackers isn't how WebID is going to blow up. We can't 
use the existence of parsers for our favorite syntaxes as the yardstick. 
We have to learn to accept that EAV/SPO graphs can be serialized using a 
variety of formats. Sticking to one or two isn't the solution. Look for 
what has legs and broad interest or adoption, then embrace. 
HTML+Microdata has legs, and adoption curve already has the hockey stick 
shape. Let's ride it all the way to WebID adoption at massive scales.

>
> We will get to complete syntax agnosticism, don't worry.

It isn't something we control. Non of us control the Web. Thus, its 
always best to just tap into the FORCE that is the Web.

> We started off with only rdfxml, and are now at xml + rdfa, so you can 
> see  we are moving in the right direction.

Not disputing the support for xhtml+rdfa, but we cannot be frozen in 
time. We now have to embrace HTML+Microdata as a visible option. Then 
use the power of osmosis to pull in the many developers in this realm. 
Most are of the Web 2.0 variety, the very community that we need the 
most re. bootstrap.

> But not every programming language has every parser available to them, 
> and asking servers to implement all of them is impossible: an 
> implementation would end up so huge it would make a mockery of any 
> idea of simplicity we were making.

No. Far from it. We want mass adoption by whatever means necessary. 
Luckily, this simply means being accommodating of markup languages and 
syntaxes for expressing and serializing EAV/SPO based directed graphs.

>
> Anyway, have a great weekend!
>
> All the best,
>
> Henry
>
>
>
> Social Web Architect
> http://bblfish.net/
>


-- 

Regards,

Kingsley Idehen	
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20111127/5ebb5e05/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1625 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20111127/5ebb5e05/attachment-0001.bin