Re: LDP Interop via CIMBA and Virtuoso

worked fine, baring some 25 year old issues that noone wants solved (since it puts W3C in the hot seat on crypto complicity). Easy to work around.

Windows 8.1 phone trial not a success (being a communications device, more regulated that an PC for crypto). Windows 8.1 PC did fine.

Sent from Surface Pro

From: Kingsley Idehen
Sent: ‎Tuesday‎, ‎July‎ ‎22‎, ‎2014 ‎8‎:‎53‎ ‎AM
Cc:, peter Msn

On 7/22/14 11:23 AM, Melvin Carvalho wrote:

You're almost there! Now you just need to create a channel for your posts.

Did you attempt to create a new channel? 

One other thing

Logging in to

I am not on there in an obvious way i.e., not via the WebIDs you know (see comments below). I'll connect back there one this side of interop is done, by that I mean:

1. Support for any WebID re. CIMBA -- as opposed to WebIDs where as the Idp
2. Loosely coupling the CIMBA app, deployment platform Virtuoso, and actual data storage -- e.g., Dropbox, Google Drive, OneDrive etc..
3. Having Public mean "Public" as opposed to "Public with a WebID that's verifiable using WebID-TLS" -- by not being really Public the user has to manually make each blog post "Really Public" etc..

I can find 3 profiles for you ( 1 normal, 2 QA) in webizen, but I cannot find any channels in them.  When I click your name, I get the spinner which never completes.

Yes, because that WebID resolves to document hosted by an instance that didn't initially work with CIMBA. Note the comments in our pull request [1]



Kingsley Idehen       
Founder & CEO 
OpenLink Software     
Company Web:

Personal Weblog 1:

Personal Weblog 2:

Twitter Profile:

Google+ Profile:

LinkedIn Profile:

Personal WebID:

Received on Tuesday, 22 July 2014 17:19:16 UTC