Re: [foaf-dev] FOAF profile management
Peter Williams <[email protected]> Tue, 14 Apr 2015 16:41:57 +0000
| Newsgroups | gmane.comp.web.rdfweb |
|---|---|
| Message-ID | <BY1PR0701MB16429210FAF1DE1A7E529BCEA7E60@BY1PR0701MB1642.namprd07.prod.outlook.com> |
--===============6316324704832470874== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_BY1PR0701MB16429210FAF1DE1A7E529BCEA7E60BY1PR0701MB1642_" --_000_BY1PR0701MB16429210FAF1DE1A7E529BCEA7E60BY1PR0701MB1642_ Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable Are folks aware of the heavy promotion of SSL auth client authentication (i= e client cert chain) in the openid connect world (during user authorization= ). A profile of webid to those semantics might be called for. Competition in cloud security for APIs and mobile app cross devices has mov= ed to server-side security contexts, that bridge the users main authenticat= ion context to the several secondary contexts maintained to facebook, googl= e, any other offering connected (and token guarded) services designed for = multi api vendor mashup. Sent from my Windows Phone ________________________________ From: Melvin Carvalho<mailto:[email protected]> Sent: =FD4/=FD14/=FD2015 9:23 AM To: Nicola Vitucci<mailto:[email protected]> Cc: foaf-dev Friend of a<mailto:foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]> Subject: Re: [foaf-dev] FOAF profile management On 14 April 2015 at 18:01, Nicola Vitucci <[email protected]<mailto:= [email protected]>> wrote: > Sounds great. You may want to look at: > > https://linkeddata.github.io/profile-editor/ > > Which also supports FOAF+SSL (which is now rebranded to WebID) > Hi Melvin, thanks for the pointer, I've tried the editor with my own FOAF profile and it is really cool! BTW, I forgot to mention that some preliminary work on the manager (which can be run from the command line too) can be found here: https://github.com/nvitucci/foaf-manager As for FOAF-SSL/WebID my main question is: what is the most up-to-date specification for the certificate description in a FOAF file? The terms defined in the Cert Ontology (http://www.w3.org/ns/auth/cert#) are still "unstable", and I've seen around different ways to describe the elements of a public key and their datatypes besides the examples shown there. Same goes for the format of the certificate, as on the WebID-TLS page (http://www.w3.org/2005/Incubator/webid/spec/tls/) the certificate example is reported as "no longer valid". What should I use in the validator? I'd also take a look at the Social Linked Data Platform (SoLiD) which descr= ibes many of the up to date practices for working with FOAF, WebID, RDF and= read write social data: https://github.com/linkeddata/SoLiD Thanks, Nicola --_000_BY1PR0701MB16429210FAF1DE1A7E529BCEA7E60BY1PR0701MB1642_ Content-Type: text/html; charset="windows-1256" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1= 256"> <meta content=3D"text/html; charset=3Dutf-8"> </head> <body> <div> <div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Are folks awa= re of the heavy promotion of SSL auth client authentication (ie client cert= chain) in the openid connect world (during user authorization).<br> <br> A profile of webid to those semantics might be called for.<br> <br> Competition in cloud security for APIs and mobile app cross devices has mov= ed to server-side security contexts, that bridge the users main authenticat= ion context to the several secondary contexts maintained to facebook, googl= e, any other offering connected (and token guarded) services designed for multi api vendor mashup.<br> <br> Sent from my Windows Phone</div> </div> <div dir=3D"ltr"> <hr> <span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:= bold">From: </span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr= ef=3D"mailto:[email protected]">Melvin Carvalho</a></span><br> <span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:= bold">Sent: </span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD4/= =FD14/=FD2015 9:23 AM</span><br> <span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:= bold">To: </span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr= ef=3D"mailto:[email protected]">Nicola Vitucci</a></span><br> <span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:= bold">Cc: </span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr= ef=3D"mailto:foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]">foaf-dev Friend of a</a></spa= n><br> <span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:= bold">Subject: </span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [= foaf-dev] FOAF profile management</span><br> <br> </div> <div> <div dir=3D"ltr"><br> <div class=3D"gmail_extra"><br> <div class=3D"gmail_quote">On 14 April 2015 at 18:01, Nicola Vitucci <span = dir=3D"ltr"> <<a href=3D"mailto:[email protected]" target=3D"_blank">nicola.vi= [email protected]</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; border= -left:1px solid rgb(204,204,204); padding-left:1ex"> <span class=3D"">> Sounds great. You may want to look at:<br> ><br> > <a href=3D"https://linkeddata.github.io/profile-editor/" target=3D"_bl= ank">https://linkeddata.github.io/profile-editor/</a><br> ><br> > Which also supports FOAF+SSL (which is now rebranded to WebID)<br> ><br> <br> </span>Hi Melvin,<br> <br> thanks for the pointer, I've tried the editor with my own FOAF profile<br> and it is really cool! BTW, I forgot to mention that some preliminary<br> work on the manager (which can be run from the command line too) can be<br> found here:<br> <br> <a href=3D"https://github.com/nvitucci/foaf-manager" target=3D"_blank">http= s://github.com/nvitucci/foaf-manager</a><br> <br> As for FOAF-SSL/WebID my main question is: what is the most up-to-date<br> specification for the certificate description in a FOAF file? The terms<br> defined in the Cert Ontology (<a href=3D"http://www.w3.org/ns/auth/cert#" t= arget=3D"_blank">http://www.w3.org/ns/auth/cert#</a>) are still<br> "unstable", and I've seen around different ways to describe the e= lements<br> of a public key and their datatypes besides the examples shown there.<br> Same goes for the format of the certificate, as on the WebID-TLS page<br> (<a href=3D"http://www.w3.org/2005/Incubator/webid/spec/tls/" target=3D"_bl= ank">http://www.w3.org/2005/Incubator/webid/spec/tls/</a>) the certificate<= br> example is reported as "no longer valid". What should I use in th= e<br> validator?<br> </blockquote> <div><br> </div> <div>I'd also take a look at the Social Linked Data Platform (SoLiD) which = describes many of the up to date practices for working with FOAF, WebID, RD= F and read write social data:<br> <br> <a href=3D"https://github.com/linkeddata/SoLiD">https://github.com/linkedda= ta/SoLiD</a><br> </div> <div> </div> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; border= -left:1px solid rgb(204,204,204); padding-left:1ex"> <br> Thanks,<br> <br> Nicola<br> </blockquote> </div> <br> </div> </div> </div> </body> </html> --_000_BY1PR0701MB16429210FAF1DE1A7E529BCEA7E60BY1PR0701MB1642_-- --===============6316324704832470874== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZm9hZi1kZXYg bWFpbGluZyBsaXN0CmZvYWYtZGV2QGxpc3RzLmZvYWYtcHJvamVjdC5vcmcKaHR0cDovL2xpc3Rz LmZvYWYtcHJvamVjdC5vcmcvbWFpbG1hbi9saXN0aW5mby9mb2FmLWRldg== --===============6316324704832470874==--