Re: [foaf-dev] FOAF profile management

--===============4230495053874083898==
Content-Type: multipart/alternative; boundary=001a11c33f28cd69d60513b191a2

--001a11c33f28cd69d60513b191a2
Content-Type: text/plain; charset=UTF-8

On 14 April 2015 at 18:01, Nicola Vitucci <[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?
>

The cert vocabulary is in use.  It hasnt been updated lately, I think,
mainly due to time constraints.  There's a patch waiting to go in I believe
to add Private Key terms.

The terms there are relatively stable, imho, and there are working system
based on exponent and modulus.

However if the new provisional WebID + RSA system (which uses the new web
cripto API) starts to get adopted, we could see addition of a PEM format
too.  Henry, Andrei and I discussed this recently and we all +1'd so that
may hopefully get added soon.

Terms in foaf and cert are generally maked unstable, but probably actually
are quite stable, imho.

>
>
> Thanks,
>
> Nicola
>

--001a11c33f28cd69d60513b191a2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 14 April 2015 at 18:01, Nicola Vitucci <span dir=3D"ltr">&lt;<a href=
=3D"mailto:[email protected]" target=3D"_blank">nicola.vitucci@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><span class=3D"">&gt; Sounds great.=C2=A0 You may want to look at:<br>
&gt;<br>
&gt; <a href=3D"https://linkeddata.github.io/profile-editor/" target=3D"_bl=
ank">https://linkeddata.github.io/profile-editor/</a><br>
&gt;<br>
&gt; Which also supports FOAF+SSL (which is now rebranded to WebID)<br>
&gt;<br>
<br>
</span>Hi Melvin,<br>
<br>
thanks for the pointer, I&#39;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>
&quot;unstable&quot;, and I&#39;ve seen around different ways to describe t=
he elements<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 &quot;no longer valid&quot;. What should I use in th=
e<br>
validator?<br></blockquote><div><br></div><div>The cert vocabulary is in us=
e.=C2=A0 It hasnt been updated lately, I think, mainly due to time constrai=
nts.=C2=A0 There&#39;s a patch waiting to go in I believe to add Private Ke=
y terms.<br><br></div><div>The terms there are relatively stable, imho, and=
 there are working system based on exponent and modulus.<br><br>However if =
the new provisional WebID + RSA system (which uses the new web cripto API) =
starts to get adopted, we could see addition of a PEM format too.=C2=A0 Hen=
ry, Andrei and I discussed this recently and we all +1&#39;d so that may ho=
pefully get added soon.<br><br></div><div>Terms in foaf and cert are genera=
lly maked unstable, but probably actually are quite stable, imho.<br></div>=
=C2=A0<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks,<br>
<br>
Nicola<br>
</blockquote></div><br></div></div>

--001a11c33f28cd69d60513b191a2--

--===============4230495053874083898==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZm9hZi1kZXYg
bWFpbGluZyBsaXN0CmZvYWYtZGV2QGxpc3RzLmZvYWYtcHJvamVjdC5vcmcKaHR0cDovL2xpc3Rz
LmZvYWYtcHJvamVjdC5vcmcvbWFpbG1hbi9saXN0aW5mby9mb2FmLWRldg==

--===============4230495053874083898==--