"Identified as a need for both the Social Web WG and Web Annotations WG due
to dependence on JSON-LD"
Says who? SocialWGs deliverables explicitly make JSON-LD processing a non
requirement. If we require LD processing, then then I would express
absolutely no surprise when everyone ignores it. In other words, all of our
work would be for naught and our standard a failure.
Which brings us on to
"Graph Normalization algorithm is hidden from developers, but very complex"
Erm, how? Surely some developer must implement it?
Or are you suggesting that this is a non-issue because its hidden by a
library how is this supposed to work until the standard is sufficiently
ubiquitous that I can get a complete and adaptable implementation no matter
what language I use? Your mitigating factor isnt a valid mitigating factor.
That should just say
"Graph Normalization algorithm is very complex"
Experience shows that complicated specifications generally fail unless they
bring something truly compelling to the table.
When the alternative is the widely adopted, part of the webcrypto, simpler,
more flexible JOSE... How do you expect to win?
(Not that I think SM is entirely meritless - e.g. clear signing is useful -
just that it is probably dead in the water as long as LD processing is
mandated)
On 18 Nov 2014 15:56, "☮ elf Pavlik ☮" <perpetual-tripper@wwelves.org>
wrote:
> I remember some conversation during TPAC about systems behind firewall
> not fit to make requests back to some other server as required in
> webmention.org . I think that JSON-LD Secure Messaging could offer some
> solutions here.
>
> Mozilla Open Badges already have hosted version (similar to how pattern
> used for WebMention works) as well as signed version, both explained in
> current (pre JSON-LD) spec:
>
> https://github.com/openbadges/openbadges-specification/blob/master/Assertion/latest.md#badge-verification
>
>
> -------- Forwarded Message --------
> Subject: Digital Signatures for Credentials
> Resent-Date: Mon, 17 Nov 2014 02:32:41 +0000
> Resent-From: public-credentials@w3.org
> Date: Sun, 16 Nov 2014 21:32:16 -0500
> From: Manu Sporny <msporny@digitalbazaar.com>
> To: Credentials Community Group <public-credentials@w3.org>
>
> During the call last week, we touched on the last major item (digital
> signatures) that needs to be aligned between the Badge Alliance
> technology stack and the Credentials technology stack. Like all
> technology, there are upsides and downsides to each approach. I thought
> I'd try and summarize them in this email.
>
> The Credentials technology stack[1] focuses on extensibility via Linked
> Data / JSON-LD and thus uses a digital signature mechanism that was
> built for graph-based data.
>
> The Badge Alliance technology stack had focused on pure JSON data and
> re-using the IETF's JOSE digital signature stack. I've written about
> Digital Bazaar's concerns with JOSE before[2].
>
> In general, both technologies allow a developer to:
> * Digitally sign data
> * Verify digitally signed data
> * Express public/private keypairs
> * Encrypt and decrypt data in message envelopes
>
> In this respect, neither technology is that different from what XML
> Digital Signatures enables one to do.
>
> Both SM and JOSE use JSON as the basic container format due to JSON's
> popularity with developers. When comparing the SM vs. JOSE technology
> stacks, here are some of the key pros/cons:
>
> JSON-LD Secure Messaging Pros:
> * Clear-text signatures (easier to see/debug what's going on)
> * Works with any RDF syntax (N-Quads, TURTLE, etc.)
> * Ensures discoverability of public keys via the Web
> * Simpler interface for Web developers
> * Extensible message format due to JSON-LD
> * Designed to integrate cleanly with HTTP Signatures
> * Identified as a need for both the Social Web WG and
> Web Annotations WG due to dependence on JSON-LD
>
> JSON-LD Secure Messaging Cons:
> * Not an official standard yet
> * Graph Normalization algorithm is hidden from developers, but
> very complex
>
> JOSE Pros:
> * First mover advantage
> * Already an IETF standard with thorough security review
> * More software libraries exist for JOSE
>
> JOSE Cons:
> * Signed data is an opaque blob, which is very difficult to try and
> debug
> * Fairly difficult to use for Web developers due to exposing too much
> complexity
> * Format is not extensible, requires coordination through IETF
> * No standardized public key discoverability mechanism
>
> The biggest downside with the SM approach is that it's not a W3C
> standard yet and that will take some time (1-2 years). The technology is
> done and there are multiple interoperable implementations out there, so
> we're not concerned about it not getting through the standardization
> process once it enters the process. With the recent hallway discussion
> at W3C TPAC, we feel that we should be able to get the minimum number of
> W3C member votes necessary to take the specs REC-track.
>
> So, with that introduction - are there any thoughts on SM vs. JOSE? Does
> anyone feel that strongly one way or the other? Any pros/cons that are
> not in the list above that should be?
>
> -- manu
>
> [1] http://opencreds.org/specs/source/roadmap/#technology-stack
> [2]
> http://lists.w3.org/Archives/Public/public-webpayments/2013Aug/0004.html
>
> --
> 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/
>
>
>
>
>