- From: Peter Williams <home_pw@msn.com>
- Date: Fri, 14 Jun 2013 15:20:22 +0000
- To: public-webid Group <public-webid@w3.org>, Henry Story <henry.story@bblfish.net>
- CC: "foaf-protocols@lists.foaf-project.org" <foaf-protocols@lists.foaf-project.org>
- Message-ID: <SNT402-EAS2388C5D4E655589B2FEE7692800@phx.gbl>
When it was written, the public didn't know the meaning of the term metadata. Now they do - educated by means of showing privacy vulnerabilities specific to a web “founded on”insecure metadata. And they have a good intuition of specifically -”social” class of threat models specific to metadata. They also have a mental model of how vendors, contractors and security professionals may be part of the threat (to personal privacy invasion); willingly or otherwise. For a specifically social trust protocol the change in the public’s perceptions and education level on the threats they face does changes the (scope of the) problem. The freedom box is now perceived to be not so free (depending on context); and may be actually rather worthless, unless you count the “feel good” factor. How does WebID - in its updated philosophy - address the newly revealed threat of specifically institutional snooping? If I look back at the concept of the VeriSign cert in netscape-grade https, it was specifically intended (by VISA) to be a feel good security technology, note, no ifs, no buts, no caveats. It was to change nothing (but make you feel good about the new internet threats that came into the concept set of the general public, circa 1994). Sent from Windows Mail From: Henry Story Sent: Friday, June 14, 2013 2:36 AM To: public-webid Group Cc: foaf-protocols@lists.foaf-project.org On 13 Jun 2013, at 22:31, Henry Story <henry.story@bblfish.net> wrote: > Yes, we have two specs: > > https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/tls-respec.html > https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html > > I am not sure why we don't get the full html view anymore. > Anyone know what we need to change? I fixed these. The problem is related to the move to the new respec.js https://github.com/darobin/respec/ It no longer allows one to add spec refs to the js as one used to be able to see diff https://dvcs.w3.org/hg/WebID/rev/7f01174c75b0 So the TLS spec now is missing two references [[ berjon.biblio["RFC5746"] = "E. Rescorla, M. Ray, S. Dispensa, N. Oskov, <a href=\"http://tools.ietf.org/html/rfc5746\"><cite>Transport Layer Security (TLS) Renegotiation Indication Extension</cite></a> February 2010. Internet RFC 5246. URL: <a href=\"http://tools.ietf.org/html/rfc5746\">http://tools.ietf.org/html/rfc5746</a> "; berjon.biblio["WEBID"] = "Andrei Sambra, Stéphane Corlosquet. <a href='https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html' ]] Any idea how one can get those added to the code using the new specref? https://github.com/tobie/specref > > We split the identity part from the TLS part, and we have a definition > of WebID that is simple and implementable. Also a bit of philosophical > > We should be close to a new release. All we need is one document > to describe the other two docs. And perhaps a few tweaks.... > > Henry > > Begin forwarded message: > >> From: Dan Brickley <danbri@danbri.org> >> Subject: [foaf-protocols] WebID status recap? >> Date: 13 June 2013 21:39:26 CEST >> To: foaf-protocols@lists.foaf-project.org >> >> It's mid-2013. Can someone share an overview of the current status of >> WebID aka foaf+ssl, in terms of implementations, adoption and >> documentation at W3C? >> >> Thanks, >> >> Dan >> _______________________________________________ >> foaf-protocols mailing list >> foaf-protocols@lists.foaf-project.org >> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols > > Social Web Architect > http://bblfish.net/ > Social Web Architect http://bblfish.net/ _______________________________________________ foaf-protocols mailing list foaf-protocols@lists.foaf-project.org http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
Received on Friday, 14 June 2013 15:33:53 UTC