W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

Re: WebIDRealm RDFa

From: Henry Story <henry.story@bblfish.net>
Date: Thu, 5 Jan 2012 02:08:33 +0100
Cc: public-xg-webid@w3.org
Message-Id: <0A1FDD3B-236A-46B4-955A-6BAA9F3335C6@bblfish.net>
To: Kingsley Idehen <kidehen@openlinksw.com>

On 5 Jan 2012, at 01:45, Kingsley Idehen wrote:

> On 1/4/12 7:42 PM, Henry Story wrote:
>> On 5 Jan 2012, at 01:37, Henry Story wrote:
>> 
>>> On 5 Jan 2012, at 01:27, Kingsley Idehen wrote:
>>> 
>>>> On 1/4/12 7:16 PM, Henry Story wrote:
>>>>> On 5 Jan 2012, at 01:09, Kingsley Idehen wrote:
>>>>> 
>>>>>>> But anyway, clearly you don't want to work on a common test suite to help new people join.
>>>>>> See my opening comments. It's been done before, many times over with standards much more complex than WebID, used by masses of people world wide.
>>>>> Ok. So are you against a webid test suite then? Yes/No
>>>> FWIW - No.
>> Oops, that was probably meant as "No I am not against a test suite" (the FWIW confused me)
>> 
>> :-)
> 
> Yes, my parser works :-)

Great. Now the next question is: are you prepared to help with the project of building an open source test suite? 

   What would you find a reasonable thing your end point can provide so that test suites could hook onto it, and build up a report? I am speaking about an end-point such as http://id.myopenlink.net/ods/webid_demo.html but others could be ok. What can it produce that would be easy for a test suite to consume?

  Henry


> 
> Kingsley
>> Good so then, how do you think we should go around to do that simply?
>> 
>> It's nearly 2am here, so I'll go to sleep.
>> 
>> See you tomorrow.
>> 
>> 	Henry
>> 
>>> Why? What would be the problem with having an OpenSource set of tests to help newcomers who produce new WebID Protocol endpoints to run a bunch of tests against it to find out if they are WebID compliant?
>>> 
>>> Did we not in this thread use a whole bunch of tests suites/validators? For RDFa, for RDF/XML etc....
>>> 
>>> Were they not helpful?
>>> 
>>> It would help if you explained your position more clearly because it could be that we have a misunderstanding between what you think I am talking about and what I think I am talking about.
>>> 
>>> Henry
>>> 
>>> 
>>>> 
>>>> Kingsley
>>>>> If yes, how do you think we should proceed.
>>>>> If no, why do you think we should not have one?
>>>>> 
>>>>> 
>>>>> 
>>>>>>> Perhaps WebID would be just too simple then....
>>>>>> No comment :-)
>>>>> 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
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> Social Web Architect
>>> http://bblfish.net/
>>> 
>> 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
> 
> 
> 
> 
> 
> 

Social Web Architect
http://bblfish.net/
Received on Thursday, 5 January 2012 01:14:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 January 2012 01:14:16 GMT