Web 7.0™ / TDW AgenticOS™ / TDW™ / Hyperonomy™ Digital Identity Lab

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.

Click here to download the Technical White Paper (TWP) Document Development Plan and Schedule (PDF).

Acknowledgements

• Microsoft Corporation

Click the HUB-ARM to enlarge it. It will open in a new tab. Read the narration provided below the HUB-ARM.

Narration

Each bullet in the list below describes a numbered bubble in the diagram above.

1. Alice’s App (1) has secure access to Alice’s Public Data (5), Alice’s Private Data (8), and Alice’s Secret Data (11).
2. Alice’s App (1)’s secure access is realized by the Layer D Hub Service Endpoints (2). The Layer D Hub Service Endpoints (2) support intelligent, semantics-based, query-by-schema access via a pubic interface exposed by a collection of Hub Protocol Handlers (3).
3. Layer D Hub Service Endpoints (2)’s collection of supported Hub Protocol Handlers (3) might include: Bluetooth, HTTP REST, gRPC, Web Sockets, etc.
4. Layer D Hub Service Endpoints (2) primarily provide access to the functionality supported by the Layer D Federated Query and Retrieval Service (4). The functionality supported by the Layer D Federated Query and Retrieval Service includes intelligent federated routing of semantics and schema-based queries plus aggregated retrieval of matching resources from Alice’s Public Data (5), Alice’s Private Data (8), and/or Alice’s Secret Data (11).
5. Alice’s Public Data (5) is managed by the Hub Microkernel (6) which supports UJWT Data Vaults (7) containing collections of unsigned JWT resources.
6. The Hub Microkernel (6) provides CRUD access to the collections of unsigned JWT resources in one or more UJWT Data Vaults (7) attached to the Hub Microkernel (6).
7. One or more UJWT Data Vaults (7) can be attached to a Hub Microkernel (6) and are used to store collections of unsigned JWT resources.
8. Alice’s Private Data (8) is managed by the Hub Microkernel (9) which supports JWS Data Vaults (10) containing collections of JWS (signed JWT) resources.
9. The Hub Microkernel (9) provides CRUD access to the collections of JWS (signed JWT) resources in one or more JWS Data Vaults (10) attached to the Hub Microkernel (9).
10. One or more JWS Data Vaults (10) can be attached to a Hub Microkernel (9) and are used to store collections of JWS (signed JWT) resources.
11. Alice’s Secret Data (11) is managed by the EDV Microkernel (12) which supports JWE Data Vaults (13) containing collections of JWE (encrypted JWT) resources.
12. The EDV Microkernel (12) provides CRUD access to the collections of JWE (encrypted JWT) resources in one or more JWE Data Vaults (13) attached to the EDV Microkernel (12).
13. One or more JWE Data Vaults (13) can be attached to an EDV Microkernel (12) and are used to store collections of JWE (encrypted JWT) resources.
14. An Indexing Crawler Service (14) might enable the indexing of publicly available content in Alice’s Data Vaults (7, 10, 13). Private and Secret Data Vaults will most likely not expose any indexable data vault-level or resource-level data.
15. A Data Vault Directory Service (DVDS) (15) might exist to enable the lookup and resolution of Alice’s Data Vaults (7,10, 13) by various public data vault properties. Private and Secret Data Vaults will most likely not expose any public data vault properties and would not be locatable using the DVDS (15).

Acknowledgements

The above proposal for describing a Hub using the TDW Hub Architecture Reference Model (HUB-ARM) was inspired by Daniel Buchner’s verbal description of a Hub during the DIF SDS/CS call on Thursday, March 11, 2021 plus subsequent conversations on the DIF SDS/CS mailing list (Adrian Gropper).

To download a copy of the Dewitter Platform Requirements List, click here:

• Trusted Content Storage (TCS Stack): Decentralized Twitter (Dewitter) Platform Requirements List

Copyright (c) 2021 Michael Herman (Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
https://creativecommons.org/licenses/by-sa/4.0/legalcode

I didn’t discover/understand I was a First Principles Thinker until relatively recently. Now, it’s my goto skill. Onward…

“Sometimes called “reasoning from first principles,” the idea is to break down complicated problems into basic elements and then reassemble them from the ground up. It’s one of the best ways to learn to think for yourself, unlock your creative potential, and move from linear to non-linear results.”

First Principles: The Building Blocks of True Knowledge (https://fs.blog/2018/04/first-principles/)

“I think it is most important to reason from first principles rather than by analogy. One of the ways we conduct our lives is we reason by analogy. We do this because something was like something else that was done or it was like what other people were doing. It’s mentally easier to reason by analogy rather than from first principles.”

First Principles Method Explained by Elon Musk (https://www.youtube.com/watch?v=NV3sBlRgzTI)

“You boil things down to the most fundamental truths
And you say “what are we sure is true” or “as sure as possible, what is true”
And then “reason up from there”
That takes a lot more mental energy.”

First Principles Method Explained by Elon Musk (https://www.youtube.com/watch?v=NV3sBlRgzTI)

Click on this video…

As well as this second video…

Video 2. The Most Powerful Way to Think | First Principles (https://www.youtube.com/watch?v=HZRDUZuIKg4)

I wager that most First Principles Thinkers are monarchs of their own belief system.

Download this presentation from here: The Rise and Fall of a Brand: Michael Eisner.

If you don’t have time, the following is the key slide.

And voila, it worked first crack.  Here are links to a couple of sample definitions:

• Shared Definition for Digital Identity (with full metadata):
  https://github.com/mwherman2000/tdw-glossary-1/blob/e4b96a0a21dd352f67b6bd93fdac66a1599ed35f/model/motivation/Principle_id-72c83ae5b01346b7892e6d2a076e787f.xml
  
• Shared Sovrin Glossary Definition Example:
  https://github.com/mwherman2000/tdw-glossary-1/blob/e4b96a0a21dd352f67b6bd93fdac66a1599ed35f/model/motivation/Driver_id-3399778b5b2f028f56014f9eb6c56f54.xml

Yesterday afternoon, I downloaded and imported the entire Sovrin Glossary V3 into Archi and the https://github.com/mwherman2000/tdw-glossary-1 repository. It contains all 249 SF Glossary terms and definitions plus a couple dozen of my own definitions (yes, the TDW Glossary supports ingesting multiple upstream glossaries and can create/refresh multiple downstream glossaries.)

Here are some screenshots:

Archi Open Source Modeler for Architecture Modeling

The Archi® modeling toolkit is targeted toward all levels of Enterprise Architects and Modelers. It provides a low cost to entry solution to users who may be making their first steps in the ArchiMate modeling language, or who are looking for an open-source, cross-platform ArchiMate modeling tool for their company or institution and wish to engage with the language within a TOGAF® or other Enterprise Architecture framework.

Archi open source modeler website (https://www.archimatetool.com/)

You can download and support the latest version of Archi from here: https://www.archimatetool.com/ .

You can download the latest version of the coArchi, Model Collaboration Plugin for Archi from here: https://www.archimatetool.com/plugins/#coArchi

Best regards,
Michael Herman
Sovrin Foundation Self-Sovereignist

A generic Replication Pipeline is illustrated below.

Outbound Processing Service

Outbound Processing Service is responsible for capturing and recording Replication Events that occur in the Source Repository. Outbound Processing Service is controlled by Replication Maps which determine what Events need to be captured, packaged, and transferred to the Target Repository. Groups of Replication Events are packaged into two types of messages or objects: Queued Items and Replication Packages.

Queued Item

A Queued Item is a unit of work to be transferred to a Target Repository for remote execution. The Replication Web Service on a Target Repository is called to push a Queued Item from the Source Repository to a Target Repository.

Replication Package

A Replication Package is a collection of one or more Replication Events plus data about the changed information that is packaged in a format specific to the Replication Transport being used. When an Event is being processed, Outbound Processing Service calls the Source repository object model to extract the changed information from the Source Repository.

Package Transfer Service

The Package Transfer Service activity is responsible for the transfer and receipt of Queued Items and the downloading of Replication Packages (Packages) from the Source Repository to the Target Repository. Package Transfer is the process that sits between Outbound Processing Service (on the Source Repository) and Inbound Processing Service (on the Target Repository).

Inbound Processing Service

Inbound Processing Service is responsible for processing the Queued Items and Packages received and accepted by the Target Repository and applying them to the repository. The Queued Items and Packages are applied to the Target Repository content base by calling the Target Repository object model.