Re: A use-case for the Internet of Things WAS: [projectvrm] IBM's ADEPT Project: Rebooting the Internet of Things

[Adrian Gropper < >]

Kevin,

I probably don't understand Welcomer Framework in this context. As I see it, one's implant and the programmers for the implant shouldn't count on any cloud or any proprietary software for all sorts of security and privacy reasons. 

How does the Welcomer Framework deal with this use case?

Adrian

On Thursday, February 19, 2015, Kevin Cox < "> > wrote:

Adrian,

The Welcomer Framework (or similar) could act as the peer reviewed Open Source programmer in your use case.

Kevin

On Thu, Feb 19, 2015 at 11:25 PM, Adrian Gropper < ');" target="_blank"> > wrote:

Things that you have implanted or wear are in IoT. I've assembled a use case for the http://openid.net/wg/heart/ working group to highlight the relationships between personal and institutional systems. The clinical part is realistic and the cloud services are routine today. The institutions include the vendors and their clouds as well as the doctors who may not trust each other's systems. It's at

https://docs.google.com/document/d/1Vuq8SS6RcfC0ywKlYdFpT_Uk4kM3qzwGWV36Vlfzj5k/edit?usp=docslist_api

Adrian

On Thursday, February 19, 2015, Kevin Cox < ');" target="_blank"> > wrote:

In our Open Source Welcomer Framework we have used the ideas from CloudOS and create connection things that are 

A connection thing is a connection between two entities along the data shared between the two entities.  Each entity can access the shared data independently of the other entity.  Each entity can connect to any other connection thing it has with any other entity with which it shares other data. 

An entity can only share data with other entities if the original sharing entity has agreed it can share all or part of the shared data. The rules of sharing could be passed through with XDI to integrate with other connection things but a simpler idea in the Welcomer and compatible Frameworks is to always access shared data from the original connection using the original rules.

The Framework does not yet have all the above but we are working iteratively towards it as we build connecting things that wish to share across applications.

Kevin

On Thu, Feb 19, 2015 at 7:21 PM, Doc Searls < > wrote:

Thanks, Phil. Great piece.  The line that follows your opening one is,

ADEPT is based onTelehash for peer-to-peer messaging, BitTorrent for decentralized file sharing, and the blockchain (via Ethereum) for smart contracts (this video from Primavera De Filippi on Ethereum is a good discussion of that concept).

Telehash is the brainbaby of Jeremie Miller, an old friend, father also of Jabber/XMPP, and I believe is on this list. Primavera is a Berkman colleague who may also be on this list. I’m cc’ing both of them to pull them in the conversational loop.

In my discussions with folks everywhere, IoT (and the own cycle) come up more and more. I think it’s a huge domain for VRM. (Thought: Internet of Owned Things.)

Let’s get the IBM folks in this conversation as well.

Doc

(In a rush, London)

On Feb 19, 2015, at 4:05 AM, Phillip J. Windley Ph.D. < > wrote:

The ADEPT project was mentioned here before. I took some time to look it over in depth and wrote up my thoughts:

http://www.windley.com/archives/2015/02/ibms_adept_project_rebooting_the_internet_of_things.shtml

Summary

The Internet of Things, only a few years old, needs a reboot. So says Paul Brody of IBM. The IBM Adept project is a proof of concept for an open, decentralized Internet of Things.

--

Adrian Gropper MD
Ensure Health Information Privacy. Support Patient Privacy Rights.
http://patientprivacyrights.org/donate-2/ 

--

Adrian Gropper MD
Ensure Health Information Privacy. Support Patient Privacy Rights.
http://patientprivacyrights.org/donate-2/