- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Fri, 16 Jan 2015 09:47:03 +0100
- To: public-webid <public-webid@w3.org>, public-rww <public-rww@w3.org>
- Message-ID: <CAKaEYhJvkxsa9gxD0idk9t-6c_76HM1RD9qTawJXfSetfOeraA@mail.gmail.com>
FYI: ---------- Forwarded message ---------- From: Manu Sporny <msporny@digitalbazaar.com> Date: 16 January 2015 at 06:03 Subject: Linked Data Signatures spec published To: Web Payments <public-webpayments@w3.org>, Credentials Community Group < public-credentials@w3.org> Hi all, The Linked Data Signatures specification has been extracted from the old Secure Messaging specification. This was done after it became fairly clear that most of the people we were showing the specification to didn't really care about the encryption portions (which we'll extract into a separate specification later on). We have also received quite a bit of strong push-back on the "Secure Messaging" name, thus the re-branding. For those new to the discussion, in order to do digital signatures in JSON-LD, we need two specs and a vocabulary: 1. The RDF Dataset Normalization spec 2. The Linked Data Signatures spec 3. The Security vocabulary #2 was a part of the Secure Messaging spec until now. It'll live on its own from now on. Here's a very rough draft: https://web-payments.org/specs/source/ld-signatures/ This spec has a preliminary implementation here: https://github.com/digitalbazaar/jsonld-signatures and an npm and bower package: https://www.npmjs.com/package/jsonld-signatures -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: The Marathonic Dawn of Web Payments http://manu.sporny.org/2014/dawn-of-web-payments/
Received on Friday, 16 January 2015 08:47:32 UTC