- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Mon, 10 Oct 2011 20:08:42 +0200
- To: Henry Story <henry.story@gmail.com>
- Cc: WebID XG <public-xg-webid@w3.org>, Stéphane Corlosquet <scorlosquet@gmail.com>
On 10 October 2011 20:02, Henry Story <henry.story@gmail.com> wrote: > > On 10 Oct 2011, at 19:25, Melvin Carvalho wrote: >>> is for cert:pubKey +1 >> >> It may be good to be consistent with other ontologies e.g. >> >> http://payswarm.com/vocabs/security >> > > A public key property refers to a URL that contains information about a public key. > > sec: publicKey > Status: unstable > Domain: sec:Key, owl:Thing > Range: xsd:anyURI > The following example demonstrates the expression of a public key belonging to the identity https://payswarm.example.com/i/bob. > > That is a completely different relation. The relation we are putting forward in the cert ontology is from a > person/agent to a mathematical public key. The sec ontology refers to a different relation. > > So on your argument we should not use the same name then, since that would be confusing. My current WebID public key is a URI ( http://melvincarvalho.com/#key1 ) As I try to avoid using bnodes, if I can. > >> so cert:publicKey +1 >> >> I see the point about confusion, but Java uses Double and double, for >> class and literal, and tho it is confusing, I think still usable > > It is not so much a question of confusion, as of making it easier to make typos. > > > Henry > > Social Web Architect > http://bblfish.net/ > >
Received on Monday, 10 October 2011 18:09:10 UTC