Re: Scope of PDS/IdH/EDV Discussion (Re: Invitation to Personal Data Hubs, Identity Hubs, EDV Roadmap Discussion) from Lucas Tétreault on 2019-11-18 (public-credentials@w3.org from November 2019)

From: Lucas Tétreault <lucas@vivvo.com>
Date: Mon, 18 Nov 2019 01:43:48 +0000
To: "daniel.hardman@evernym.com" <daniel.hardman@evernym.com>, Manu Sporny <msporny@digitalbazaar.com>
CC: "Michael Herman (Parallelspace)" <mwherman@parallelspace.net>, Daniel Buchner <daniel.buchner@microsoft.com>, Sam Curren <telegramsam@gmail.com>, "aries@lists.hyperledger.org" <aries@lists.hyperledger.org>, "indy@lists.hyperledger.org" <indy@lists.hyperledger.org>, Rouven Heck <rouven.heck@consensys.net>, W3C Credentials CG <public-credentials@w3.org>, Tobias Looker <tobias.looker@mattr.global>, Orie Steele <orie@transmute.industries>, Dmitri Zagidulin <dzagidulin@gmail.com>
Message-ID: <YT1PR01MB38657689663E82679CE3F0EEAD4D0@YT1PR01MB3865.CANPRD01.PROD.OUTLOOK.COM>

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....

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Daniel Hardman <daniel.hardman@evernym.com>
Sent: Sunday, November 17, 2019, 7:10 p.m.
To: Manu Sporny
Cc: Michael Herman (Parallelspace); Daniel Buchner; Sam Curren; aries@lists.hyperledger.org; indy@lists.hyperledger.org; 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.

Received on Monday, 18 November 2019 01:43:52 UTC