Hugh, hello. On 2013 Aug 8, at 00:05, Hugh Glaser wrote:
> Of course, it doesn't do the Personal Profile Document bit of it - I still > think I need a foaf-me style service for that (as long as I can persuade them > to use it). Or if you chose an indirection route, then you could create and host the FOAF document world-readable on your service (it is supposed to be the public key, of course), and give them WebID URIs which redirect to that. Supposing the WebID framework you choose can handle that, of course. If you created a purl.org/hughfriends/ domain, then you could create purl.org/hughfriends/pal1, .../pal2 for them, and issue them at the same time. If the conceptual model of the certificates is 'a key that opens a door', then it makes perfect sense for you to generate the things offline, yourself, and then hand them out. The purl.org/hughfriends/palX name won't really be visible to them, but they could conceptualise that as the sort of 'account number' that will be familiar from interactions with banks or utilities (it's not quite right as an idea, but it's in that direction). > Get them the p12 file somehow (most do have email!). Or PAs? These sound like very senior decision-makers indeed.... (they're not framing government internet policy or something, are they?) >> just n-t-f (I finally guessed this was non-technical friends, I think :-)) Sorry: I think I must have automatically avoided writing "Non-Technical Friends (NTF)", as that smells too much of spec-writing or grant proposals -- WebID is this week's light relief for me. All the best, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
