[foaf-protocols] Getting the basic Use Cases (Test Suite) sorted out.

[Kingsley Idehen]

Nathan wrote:
> Kingsley Idehen wrote:
>> All,
>>
>> I don't have enough cycles to edit Wikis right now, but can't we have 
>> a simple set of use cases? For instance, I had a skype session with 
>> Henry yesterday, within minutes our crossed wires were isolated and 
>> resolved.
>> My initial demos goals (as clearly labeled by my demos to date):
>>
>> 1. Get a WebID in 5 minutes or less
>> 2. Join the Cheese Club (basic demonstration of using an ODS WebID 
>> against another FOAF+SSL base data space)
>> 3. Share something and protect using FOAF+SSL based ACLs (one 
>> mechanism for demonstrating compatibility with other sources of WebIDs)
>> 4. Demonstrate compatibility with WebIDs generated outside ODS via 
>> ODS login and signup interaction --- WIP
>>
>> What Henry wanted:
>>
>> 1. Demonstrate cross compatibility across FOAF+SSL implementations 
>> via WebID based login and signup interactions (#4 on my list above)
>> 2. I guess variants of 1-3 above.
>>
>> So to Henry (his world view and resulting context), there wasn't a 
>> compelling  FOAF+SSL value prop. demo from ODS since his item #1 was 
>> a WIP (not working from his view point).
>>
>>
>> To avert the confusion above, because none of us are in identical 
>> situations (priorities wise), why don't we have a clear set of use 
>> cases. A minimal test suite of sorts. For example, something like:
>>
>> 1. Generate a WebID
>> 2. Join signup and login to a FOAF+SSL Data Space
>> 3. Share something and protect using FOAF+SSL based ACLs from your 
>> Data Space
>> 4. Demonstrate compatibility with WebIDs generated by a 3rd party 
>> FOAF+SSL compliant Data Space (via login and signup interaction).
>>
>
> let's make one each :) [set of 1-4 above]
>

Let's harmonize via a Wiki page. The end product should be a clear 
minimum set of tests. We can't have individual specific test suites for 
anything that's multi-faceted.

Testing to an agreed test suite will make all the offerings better.

-- 

Regards,

Kingsley Idehen	      
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen