Re: Scope of PDS/IdH/EDV Discussion (Re: Invitation to Personal Data Hubs, Identity Hubs, EDV Roadmap Discussion)

Daniel Hardman
 

My point was that the contrast is misleading.

A more insightful contrast would be DIDComm vs. RESTful web services secured by certificates + user login. Both run over HTTP, and both are a "whole extra layer over simple HTTP."

On Sun, Nov 17, 2019 at 6:43 PM Lucas Tétreault <lucas@...> wrote:
The discussions I've heard indicate one of the goals of DIDComm is to be transport agnostic. Either way, it's still a whole extra layer over simple HTTP....


From: Daniel Hardman <daniel.hardman@...>
Sent: Sunday, November 17, 2019, 7:10 p.m.
To: Manu Sporny
Cc: Michael Herman (Parallelspace); Daniel Buchner; Sam Curren; aries@...; indy@...; Rouven Heck; W3C Credentials CG; Tobias Looker; Orie Steele; Dmitri Zagidulin
Subject: Re: Scope of PDS/IdH/EDV Discussion (Re: Invitation to Personal Data Hubs, Identity Hubs, EDV Roadmap Discussion)

Other protocol work, like communication over DIDComm,
  Bluetooth, CoAP, etc. should continue to be incubated at DIF and
  Aries.

HTTP and DIDComm are not alternatives to one another. DIDComm runs over HTTP.

Join indy@lists.hyperledger.org to automatically receive all group messages.