Microsoft SharePoint Products and Technologies: 20th Anniversary Celebration

Microsoft “Tahoe” Airlift and RC1 Announcements

Figure 1. Microsoft SharePoint Evolution
Figure 2. Microsoft SharePoint Portal Server 2001: Installation Splash Screen

Microsoft Products and Technologies Whitepapers

Client: Microsoft Corporation SharePoint Product Group / Microsoft IT Showcase

Exchange 2000 Web Storage System Articles

Outlook 10 Drops Support for the Local Web Storage System Articles

Leave a comment

Filed under Uncategorized

TDW Glossary: SOVRONA Ecosystem Neighborhood: What is the SOVRONA Mesh (SOVRONA Network)?

Click the neighborhood to open it in a new tab.

Figure 1. SOVRONA Ecosystem Neighborhood

Key Definitions

SOVRONA Mesh (SOVRONA Network)

The SOVRONA Mesh is comprised of a network of SOVRONA Nodes (each hosting its own replica of the SOVRONA Ledger) and includes and is governed by the SOVRONA Governance Framework (SGF). The SOVRONA Mesh excludes the Agents that communicate with the SOVRONA Mesh via the HyperLedger Indy Service Endpoint exposed by each SOVRONA Node.

Resources

  1. INDY-ARM (https://mwherman2000.github.io/indy-arm/)
  2. SOVRIN-ARM (https://mwherman2000.github.io/sovrin-arm/)

Leave a comment

Filed under Uncategorized

Transcription of Selected Parts of the DIF SDS/CS March 11, 2021 Zoom Call: Hub and EDV Discussion featuring Daniel Buchner’s Description of a Hub

Transcription of Selected Parts of the DIF SDS/CS March 11, 2021 Zoom Call: Hub and EDV Discussion featuring Daniel Buchner’s Description of a Hub

Context

This is a transcription of selected parts of the EDV-Hub conversation during the DIF SDS/CS Thursday weekly Zoom call on March 11, 2021. This is the call where Daniel Buchner described (verbally) several aspects about what is and what is not a Hub.

This partial transcription focuses primarily on Daniel’s comments as they relate to the question “what is a Hub?”.

NOTE: The time code timestamps are accurate but not precise. They may be out by +/- a couple of seconds.

Recording

Link to the Zoom recording (audio plus chat): https://us02web.zoom.us/rec/share/-6PUTYTQfZt-2E23VYFFUcAQsdjiocqGy8hlOaCk1jNOC41EuEHmB8UP7hpmOmfs.qbMCfoK4E_wwDXmV

Transcription

28:00 Dmitri: EDVs are for the most part defined.

28:35 Michael: What I was looking for is a litmus test. Oh yah, it goes in this bucket. Oh yah, it goes in that bucket. We don’t have that simple working definition – pair of working definitions – that easily contrasts the two.

29:40 Adrian: I’ve never felt I’ve understood Hubs in those terms.

30:14 Daniel: I think what a Hub is definitely not completely mutable by the user. It’s a standard interface for at a basic …

30:50 Daniel: What a Hub is really is a friendly application-level set of interfaces and functionality over an EDV that provides stuff like queuing up push-style messages to the owner of the Hub when they come online and go grab all of the outstanding objects. It allows people to store data by semantic type so that I can say here’s my Tweet objects [31:12 Daniel continuing], here’s my list objects, here’s playlist objects, and be able to give permissions in capability form out to people to see and decrypt parts of those objects.

So, this is what it is in a nutshell. An EDV is a great thing but you have to answer the question as Michael did in his paper with Twitter. Can you build Twitter off of just the EDV API elegantly, maybe you could torture yourself to do it but could you build it elegantly, would it be something [31:42 Daniel continuing] that speaks to app developers – probably not. You need a layer that is more app-focused…in my opinion.

32:10 Daniel: A Hub was always designed to be a rather dumb datastore. It’s not trying to do complex data transformations. [32:16 Daniel continuing] It’s a semantic searchable store of data that you can get permissions to certain subsets of the data as an app asking Alice for those permissions. [32:27 Daniel continuing] An Agent is very much more powerful. An Agent is actually pulling data down, decrypting it, doing a bunch of things. [32:35 Daniel continuing] I would see a Hub like an application datastore that is yours. That you allow apps to store data for you or other people. You can have one living on a local device; you could have one in the cloud. You could have an instance in several places and they all can sync together and even though they are implemented differently by a cloud provider (like Microsoft), they would have all the same APIs and guarantees because it is a standard. That’s how I envision it.

32:43 Orie (in chat): https://medium.com/decentralized-identity/rhythm-and-melody-how-Hubs-and-agents-rock-together-ac2dd6bf8cf4

33:00 Michael: So, does the Hub’s datastore wrap or build upon on an EDV? …or is it completely like left vs. right?

33:01 Daniel (in chat): A Hub is a gateway/router between apps and EDVs.

33:10 Daniel: If you read that post that Orie posted in the chat. It is really great that he referenced that. [33:16 Daniel continuing] A Hub is essentially a layer that

33:20 Daniel: We hoping that at the end of this, a Hub can sit above an EDV is where the EDV is where everything is encrypted and a sort of level-level thing. The Hub is like the application-style interface. Maybe like the Firebase API that speaks internally to store encrypted objects in a low-level way with the EDV.

33:31 Orie (in chat): EDV <> Hub <> Agent

33:37 Daniel: Orie is absolutely right but I would probably reverse the order. An Agent is super powerful; a Hub is less powerful; an EDV is very low-level storage and it is sort of like a Hub is the app layer that sits on top of an EDV …hopefully.

47:32 Daniel (in chat): It is a semantically indexed datastore, of which it can only see truly public data

52:17 Michael (in chat): Hub = intelligent public service endpoint … for EDV data

52:31 Daniel (in chat): YES!

52:39 Daniel (in chat): slightly intelligent

53:02 Daniel (in chat): only in the sense that it can layer some semantic APIs over the internal public objects.

End of Transcription

1 Comment

Filed under Uncategorized

TDW Glossary: (Part of) The Big Picture

Click the diagram below to enlarge it…

Figure 1. Digital Identity, Verifiable Data Registry, and Sovrin Utility Neighborhoods

Leave a comment

Filed under Uncategorized

ORTHOGONAL DEFECT CLASSIFICATION (ODC4MSFT)

Billg Fall 1997 Retreat: Improving the Software Development Processes at Microsoft

Click here to download:

Leave a comment

Filed under Uncategorized

Fully Decentralized Twitter (Dewitter) App Scenario: Platform Requirements (presentation to DIF SDS/CS WG – March 18, 2021)

Click here to download:

1 Comment

Filed under Uncategorized

Trusted Digital Web: Trusted Content Storage (TCS) Whitepapers

  1. Trusted Digital Web: Trusted Content Storage Architecture (TCS Stack): Architecture Reference Models (TCS-ARMs) – Work-in-Progress
  2. Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) App Scenario
  3. Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) Platform Requirements List
  4. TDW Hub Architecture Reference Model (HUB-ARM)
  5. Trusted Content Storage (TCS Stack): Secure Resource Sharing (SRS) using Replicated Stubs: Solution Concept
  6. Fully Decentralized Twitter (Dewitter) App Scenario: Platform Requirements (presentation to DIF SDS/CS WG – March 18/2021)
Figure 1. TDW Decentralized Twitter (Dewitter) App Scenario: Dewitter ARM
Figure 2. Trusted Digital Web: HUB Architecture Reference Model (HUB-ARM)

Leave a comment

Filed under Uncategorized

“Truly Collaborative Business Solutions” for Groove Workspace from Parallelspace Corporation

(1/5) @Ray Ozzie on the importance of understanding one’s self… This, to me personally, is the most impactful of all of Ray’s #CHMFellows #vignettes. https://instagram.com/p/CMf8X_SJdFw/

(2/5) Took me a long time to figure out who I am …in fact, it took until just recently. I’m a #FirstPrinciples Thinker: https://hyperonomy.com/2021/03/10/first-principles-thinking/
…which can be a huge frustration to me and those around me when you aren’t cognizant of who you are. Thank you @Ray Ozzie #CHMFellows

(3/5) For example, remember the Groove Tool development environment Parallelspace Corporation created using an the C Preprocessor and the (depreciated) Microsoft Visual Interdev web development platform (a precursor to Visual Studio)? #FirstPrinciples Thinking. #CHMFellows

(4/5) Groove Tools like Parallelspace eMail …the fully functional version of Microsoft Outlook that ran transparently inside a Groove workspace. #FirstPrinciples Thinking. #CHMFellows

(5/5) And many, many other custom Groove tools based on #FirstPrinciples Thinking. Thank you @Ray Ozzie
https://hyperonomy.com/2021/03/17/truly-collaborative-business-solutions-for-groove-workspace-from-parallelspace-corporation/

(6/5) …all accomplished with my trusted colleague Sanjay Malhotra. Great times. 🙂

Leave a comment

Filed under Uncategorized

TDW Glossary Relationship Compass

The TDW Glossary Relationship Compass was inspired by:

  1. ANSI/NISO Z39.19-2005: Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies
  2. Synaptica KMS – Enterprise Taxonomy Management
  3. TDW Glossary Management and Collaboration Platform (TDW-GMCP): Initial Results

Click each figure to enlarge it.

The points of the TDW Glossary Relationship Compass are based on the relationship types defined in ANSI/NISO Z39.19-2005.

Figure 1. TDW Glossary Relationship Compass
Figure 2. Neighborhood example from the TDW Glossary: MT: Digital Identity
Figure 3. TDW Glossary Relationship Compass for an example: MT: Decentralized Identity
Figure 4. Neighborhood example annotated using the TDW Glossary Relationship Compass: MT: Decentralized Identity
Figure 5. Neighborhood example annotated with Related Terms (RT): MT: Decentralized Identity

Leave a comment

Filed under Uncategorized

TDW Decentralized Glossary Management and Collaboration Platform (TDW Glossary): Digital Identity Neighborhood

Figure 1. Digital Identity Neighborhood

Leave a comment

Filed under Uncategorized