[Resending to sds-wg@dif.groups.io …didn’t get through the first time.] After last week's meeting, I sent out 3-4 architecture documents describing how the Syntergy Replicator replication pipeline wor

It’s called the sds-wg@dif.groups.io mailing list. :-) …what a convoluted process to subscribe to this list! Best regards, Michael Herman Self-Sovereign Blockchain Architect Trusted Digital Web Hypero

[Resending the Syntergy Replicator replication pipeline documents to sds-wg@dif.groups.io]

Here’s the third installment on different replication approaches: Microsoft Active Directory Replication Model. The AD Replication Model is interesting because it uses a different approach to track ad

Fourth installment on replication technologies: Microsoft Sync Framework 2.1 (retired in 2016). I’m including the Microsoft Sync Framework because this article includes a good detailed description of

With sincere regrets, I’m unable to attend today’s call. I’ll watch the recording and follow-up afterward with any comments. Michael

Ran across this paper this morning. Implies many subprinciples. Best regards, Michael Herman Self-Sovereign Blockchain Architect Trusted Digital Web Hyperonomy Digital Identity Lab Parallelspace Corpo

As a follow-up to the background information I’ve sent out regarding replication technologies, I’ve been working on a white paper over the last few days entitled: Secure Data Storage Working Group (sd

Today, on the W3C CCG Call, I learned there are 3 existing EDV implementations (e.g. Digital Bazzaar). Who are the other two? …github links? More importantly, do any of these implementations have a mo

RE: 3. Discussion of the relationship between EDV spec and Hub spec (layering, interface, etc). PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ I’ve taken a firs

RE: If everything on Daniel Buchner's proposed list could be done by EDV like https://lists.identity.foundation/g/sds-wg/message/65 would we still need Hubs? An alternative approach/suggestion: Make s

I know this is going to sound repetitive but … at the top of Daniel’s document, can someone add a couple of sentences distinguishing EDVs and Hub? More specifically, based on last week’s discussion, I

RE: 3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion. PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ p.s. …that is, visual

RE: the EDV spec defines a fully standalone HTTP server with support for authorization, delegation, and replication over HTTP with DIDs... Thank you, Orie, and, in general, I totally agree. But I’m al

RE: I’m also suggesting the CS specification should go further and define an EDV MIcrokerel layer and interface to make EDVs deployable For example. Consider this use case: https://github.com/decentra

RE: Michael has mentioned some other prior-art (in the replication context) that could be reviewed here. I'm sure there's more and across other contexts? Is there other work to document all the prior

Here’s a better link (I think): https://docs.google.com/document/d/1-Ve263KT7svN7oppIHyhK6idXikcbBsn/edit

As a follow-up to Daniel’s remarks on Thursday’s call: “it’s Decentralized Twitter!”, I’ve documented a fairly complete Decentralized Twitter (Dewitter) App Scenario with 50+ assumptions and use cases

What is the most interesting use case in Decentralized Twitter (Dewitter) app scenario so far? …the use case which might have the greatest impact on the architecture of an EDV Server Instance and EDV

An important new Dewitter use case/feature #23 was published last night …see below. So far, there have been 86 views of the blog post and 71 downloads of the Dewitter app scenario PDF. Personal Agent