- From: Timothy Holborn <timothy.holborn@gmail.com>
- Date: Tue, 06 Sep 2016 13:12:48 +0000
- To: Melvin Carvalho <melvincarvalho@gmail.com>, Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-rww <public-rww@w3.org>
- Message-ID: <CAM1Sok3wneAaSWAQ2OvOv-HuXav73W_oO=dOh=GuisDDEA_pVg@mail.gmail.com>
On Tue, 6 Sep 2016 at 22:30 Melvin Carvalho <melvincarvalho@gmail.com> wrote: > On 6 September 2016 at 14:17, Kingsley Idehen <kidehen@openlinksw.com> > wrote: > >> On 9/6/16 4:08 AM, Timothy Holborn wrote: >> >> Is this problem impacting virtuoso functionality also? >> >> >> None of this has anything to do with Virtuoso. All of these issues relate >> to: >> >> [1] WebID-Profile Documents >> [2] WebID+TLS Authentication Protocol >> [3] Proper understanding of the above. >> >> Thus far, the only quirk I've found is that some of my WebID-Profile >> documents contain Turtle content that's a little laxed on prefix handling. >> By that I mean: if prefixes aren't declared and Virtuoso is the target >> platform, we use local prefix caches to resolve namespaces to URIs. Net >> effect, other platforms that don't go this far will result in WebID-Profile >> document processing errors. >> >> The biggest problem with some of the SoLiD apps is that they simply don't >> provide any diagnostic information when this errors occurs. Thus, you have >> the root of the "Virtuoso isn't SoLiD" compliant meme :( >> >> I've found this out under 5 minutes during a session with Sarven >> Capadisli when testing http://dokie.li with one of my WebIDs. Anyway, >> more to come on all of this as a lot has been discovered and I prefer to >> explain it all in plain English. >> > > Sorry if ive implied virtuoso isnt solid compliant. What I think would be > a better narrative is that it would be really awesome to see solid apps > running on virtuoso and vice versa. The advantage of this is to grow the > network effect. By using demos both platforms become more attractive. > > You make a good point in part, in that many apps dont have an exhaustive > error suite, but most have at least some error checking, and there is more > in the console. Distributed debugging is a hard problem, and takes a long > time, also app developers are always finding a line between functionality > and robustness. > > I found this library: http://cs.stanford.edu/people/karpathy/convnetjs/ not sure if it's helpful, but it looked really interesting to me ;) > You correctly point out that this issue is simply related to Webid > profiles and TLS authentication. It's great that safari has such a neat > integration with the keychain. I think blog posts like Brent's help. > Better documentation, better error checking and guiding the user, all > positives. > > >> >> Kingsley >> >> >> Tim.H. >> >> On Tue., 6 Sep. 2016, 5:29 pm Neil Macehiter, <neil.macehiter@gmail.com> >> wrote: >> >>> Thanks both. I have been able to gain access to my databox. I signed up >>> using Safari rather than Chrome and it created the certificate in my >>> keychain. When I accessed username.databox.me I was prompted for the >>> newly created certificate and was able to login. So, it doesn't look like >>> Chrome allows the creation of the certificate. What should I do about the >>> two other accounts I created: can they be deleted? >>> >>> On Mon, 5 Sep 2016 at 23:48 Timothy Holborn <timothy.holborn@gmail.com> >>> wrote: >>> >>>> that should be noted somewhere in the documentation. >>>> >>>> >>>> On Tue, 6 Sep 2016 at 07:24 Melvin Carvalho <melvincarvalho@gmail.com> >>>> wrote: >>>> >>>>> On 4 September 2016 at 11:02, Neil Macehiter <neil.macehiter@gmail.com >>>>> > wrote: >>>>> >>>>>> Hello >>>>>> >>>>>> I am trying to sign-up for Solid. I have created 2 IDs: neilmacehiter >>>>>> and nmacehiter but in both cases it does not install a new certificate in >>>>>> Chrome. I am only given the option of selecting existing certificates. Are >>>>>> you able to delete the WebIDs and explain how I can ensure it creates a >>>>>> certificate for authentication. >>>>>> >>>>> >>>>> Hi Neil & welcome! >>>>> >>>>> Thanks for trying solid. >>>>> >>>>> The system was working quite well until recently, when there was an >>>>> unexpected change in the browser, making life a bit more difficult. >>>>> >>>>> In order to get your certificate, you need to click the small green >>>>> and turn on 'key generation' in the site settings. >>>>> >>>>> Hope that helps! >>>>> >>>>> >>>>>> >>>>>> Thanks in advance >>>>>> >>>>>> Neil >>>>>> >>>>> >>>>> >> >> -- >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software (Home Page: http://www.openlinksw.com) >> >> Medium Blog: https://medium.com/@kidehen >> Blogspot Blog: http://kidehen.blogspot.com >> Twitter Profile: https://twitter.com/kidehen >> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about >> LinkedIn Profile: http://www.linkedin.com/in/kidehen >> Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this >> >>
Received on Tuesday, 6 September 2016 13:13:29 UTC