- From: Henry Story <henry.story@bblfish.net>
- Date: Fri, 29 Mar 2013 09:14:08 +0100
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: public-webid <public-webid@w3.org>
- Message-Id: <397AA66A-5CDD-46F9-9380-75A632F023CD@bblfish.net>
On 29 Mar 2013, at 08:53, Melvin Carvalho <melvincarvalho@gmail.com> wrote: > > > On 29 March 2013 08:37, Henry Story <henry.story@bblfish.net> wrote: > > On 22 Mar 2013, at 10:42, Melvin Carvalho <melvincarvalho@gmail.com> wrote: > >> Currently we have: >> >> rdfs:domain foaf:Agent; >> >> This seems slightly restrictive. >> Many things can have a key, e.g. a certificate, an account, an app etc. Agent perhaps does not cover every conceivable use case? > > You can create new relations to relate those things to keys if you need to. > > foaf:primaryTopic can relate a document keys it is about for example. > > We need a relation to relate the agent that is the one that controls the private key > of the public key to the public key, as that is what WebID authentication and most > other protocols need to work. > > In bitcoin users have a pseudo anonymous account. Each account has a key pair. It would be great to be able to model this. Why could one not think of an account as an Agent? It can transfer money, it can accept payments, etc... It is a micro agent related to you. > > It's perhaps the most serious use of PKI on the web after ecommerce. > > >> >> Is the parent of Agent an owl : Thing? > > Social Web Architect > http://bblfish.net/ > > Social Web Architect http://bblfish.net/
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 29 March 2013 08:14:56 UTC