Re: TPAC Plenary Wednesday - rww/ldp & webid

On 9/22/12 2:57 AM, Henry Story wrote:
> On 21 Sep 2012, at 18:36, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>
>> On 9/21/12 9:54 AM, Henry Story wrote:
>>> On 21 Sep 2012, at 15:42, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>>>
>>>> On 9/21/12 5:09 AM, Henry Story wrote:
>>>>> 2. Hands on using tools the community has built
>>>>>    * Make a WebID profile and certificate
>>>>>    * build a group of all members present
>>>>>    * give access to members of the group to some resources, Give access to friends of members of the group to others, etc...
>>>> Shouldn't we make this an interop level 0 item for the RWW community?
>>> What do you mean? (I mean how do we make this an interop level 0 item?)
>> I am referring to something like SWAT0 [1][2]. A variant that focuses on the functionality listed above which is a good baseline.
> yes good idea. We should try to see if we can get the SWAT tests working.

How about just making RWW-0 and then simply have it cover:

1. Making a cert
2. Authenticating via WebID
2. Authorize access to a Resource via a WebID based ACL .

Simple as that.

>
>>> It is true that we need to work on interoperability at this level. At present I think we'll probably find different platforms do things differently... But if we could demo it on even one server, then we can bring up the interop issue...
>> Demo on one server? We are dealing with the Web aren't we? There should be many interoperable servers that collectively make the point. As I keep on trying to tell you, this isn't solely about UI and/or UX. It's a composite of the aforementioned, combined with standards compliance etc..
> I am not saying this thing should work on one server. Just that if we have not reached interoperability completely by the time of TPAC, we can use TPAC to give us an aim of having software that should be interoperable, test it in there in an interoperability session,  discuss the issues, and come up with conventions [1] so that we then do become interoperable.

There are more than enough servers in place for what I described as 
RWW-0 above.
>
> Of course interoperability is the goal. But we may not have achieved it at the access control level yet by TPAC. That in part what the get together is for. (As well as introducing new people to what we are doing.

How have you arrived at this conclusion? Have you asked members of this 
forum about the statues of their products re. RWW-0 interop?

Kingsley
>
>     Henry
>
>
> [1] http://www.amazon.com/Convention-Philosophical-Study-David-Lewis/dp/0631232575
>
>>
>> Links:
>>
>> 1. http://bit.ly/NGY6Ag - SWAT0
>> 2. http://bit.ly/R5rj7Q -- SWAT0 Results
>>
>>
>>
>> Kingsley
>>>> -- 
>>>>
>>>> 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/
>>>
>>>
>>>
>>
>> -- 
>>
>> 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/
>
>
>


-- 

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