Why is a Glossary like a Network of Balls connected by Elastics?

Why is it good to think of a Glossary as a Network of Balls connected by Elastics?

From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Sent: March 24, 2021 8:47 AM
To: Leonard Rosenthol <lrosenth@adobe.com>; David Waite <dwaite@pingidentity.com>; Jim St.Clair <jim.stclair@lumedic.io>
Cc: Drummond Reed <drummond.reed@evernym.com>; sankarshan <sankarshan@dhiway.com>; W3C Credentials CG (Public List) <public-credentials@w3.org>; Hardman, Daniel <Daniel.Hardman@sicpa.com>
Subject: TDW Glossary [was: The “self-sovereign” problem (was: The SSI protocols challenge)]

RE: First and foremost, without a definition/clarification of “Verifiable”, both of your statements are ambiguous. 

Leonard, I don’t disagree with your feedback. What I have been rolling out to the community is selected neighborhoods of closely related terms from the TDW Glossary project.

[A Glossary is] like a bunch of balls explicitly connected by elastics: add a new ball to the model and all of the existing balls in the neighborhood need to adjust themselves. The more balls you have in the network, the more stable the network becomes. So it is with visual glossaries of terms, definitions, and relationships.

Michael Herman, March 2021

Verifiable and Verifiable Data Registry are in the model but currently, they don’t have specific verified definitions.

The TDW Glossary is a huge, visual, highly interrelated, multi-disciplinary, multi-standard, 6-domain, semantic network model (https://hyperonomy.com/2021/03/10/tdw-glossary-management-platform-gmp-initial-results/) that includes:

  1. Common English Language concepts – various dictionaries and reference web sites
  2. Sovrin Glossary concepts – https://sovrin.org/library/glossary/ and https://mwherman2000.github.io/sovrin-arm/
  3. Enterprise Architecture concepts – https://pubs.opengroup.org/architecture/archimate3-doc/
  4. HyperLedger Indy Architecture Reference Model concepts – https://mwherman2000.github.io/indy-arm/
  5. HyperLedger Aries Architecture Reference Model concepts – https://mwherman2000.github.io/indy-arm/
  6. Did-core concepts – https://w3c.github.io/did-core/
  7. VC concepts – https://w3c.github.io/vc-data-model/
  8. Others?

All new and updated terms, their definitions, metadata, and relationships, are automatically being published here: https://github.com/mwherman2000/tdw-glossary-1 (e.g. https://github.com/mwherman2000/tdw-glossary-1/blob/e4b96a0a21dd352f67b6bd93fdac66a1599ed35f/model/motivation/Principle_id-72c83ae5b01346b7892e6d2a076e787f.xml)

Other references:

Here’s a snapshot of what the TDW Glossary “all-in” view looks like today (aka the “network of balls connected by elastics”). The TDW Glossary has (or will very soon have) more than 500 terms and definitions plus associated metadata and relationships.

Thank you for the feedback, Leonard. Keep it coming.


Figure 1. TDW Glossary: “All In” View

Leave a comment

Filed under Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s