RE: include privat ekeys Re: rsa ontology in cert namespace

 Stop calling a "cert" ontology too, since it precious little to do with certificates - as anyone understands the term. The bindings are not signed, and in RDF land show no sign of being signed in the next decade.  That said, I am signing our RSS feeds - bearing SSO link sets not blog page links and summaries - these days, using W3C's XML-DSIG. I can find no reason why I should not stuff a foaf card in HTML in the author/person element of the RSS feed or RSS item. Should that card have a webid graph within, an RSS feed of one item can sign the HTML serialization of the foaf card. Similarly, we are signing (XML) metadata describing our 100+ IDPs, using the OASIS standards. I dont see why, as we increasingly dominate the APIs for metadata management in windows, why similarly the foaf card should not be stuffed into the person and contact, fields too.   > From: timbl@w3.org
> Date: Wed, 23 Nov 2011 13:24:07 -0500
> CC: henry.story@bblfish.net; sergio.fernandez@fundacionctic.org; ddooss@wp.pl; public-xg-webid@w3.org
> To: Mo.McRoberts@bbc.co.uk
> Subject: include privat ekeys Re: rsa ontology in cert namespace
> 
> 
> On 2011-11 -22, at 04:51, Mo McRoberts wrote:
> > In RSA, the modulus and exponent tend to be called 'n' and 'e', respectively, but some variant on 'modulus' and 'exponent' are fine *if* you ony want to store public keys (if you want to cover private keys -- though I'm not sure why you would -[...]
> 
> If you are making an ontology for keys, I feel it should include private keys. Be complete.
> There is a lot of call for standards for private data, as well as public.
> There is W3C work on management of credentials.
> I might want also to do things like use RDF as an intermediate form
> in converting identities between SSL and SSH worlds for example.
> 
> Tim
> 
> 
>