Category Archives: Uncategorized

Difference between an auto maker ecosystem and a software platform ecosystem?

Answer: Nothing.

Leave a comment

Filed under Uncategorized

Web 7.0 Always On Trusted Personal Agent

Mockup – For Internal Use Only

Leave a comment

Filed under Uncategorized

Technology Wheel of Reincarnation

Check out…

On the Design of Display Processors T. H. Myer, I. E. Sutherland;
Communications of the ACM, Vol 11, No. 6, June 1968
(http://cva.stanford.edu/classes/cs99s/papers/myer-sutherland-design-of-display-processors.pdf)

It was not until we had traveled around the wheel several times that we realized what was happening. Once we did, we tried to view the whole problem from a broader perspective. We found that some questions had fairly clear answers, but others remained in doubt.

Wikipedia contributors, “LDS-1 (Line Drawing System-1),” Wikipedia, The Free Encyclopedia, https://en.wikipedia.org/w/index.php?title=LDS-1_(Line_Drawing_System-1)&oldid=1090999867 (accessed January 3, 2023).

Leave a comment

Filed under Uncategorized

Strategy Maps: A Real-life Example

The Customer Perspective can be relabelled Unique Customer Value Proposition because without a unique value proposition, your customer perspective can prove to be worthless.

Leave a comment

January 1, 2023 · 10:11 pm

A Note to Mothers

This a note of caution to Mothers as we approach the 7th anniversary of my Mother’s death, Beverly Margaret Herman (Mahura), on December 25, 2015. The untold story.

Why is this note a) a note of caution, and b) why was my Mom’s death needless?

Mom died at 4:30 pm EST on Christmas Day 2015. Six months earlier (June 10, 2015) Mom had a biopsy on a large tumor near the top of her lung. The tumor was full of blood and had started to bleed into my Mom’s esophagus. When the surgeon came out of the operating room following her biopsy, the first thing he told me was Mom had Stage 4 Lung Cancer and that Mom was at risk of the tumor bursting and Mom choking on her own blood. The biopsy was at 11 am and the surgeon had already scheduled an appointment with an oncologist for 2 pm the same day.

Meeting with the oncologist, the doctor asked Mom a few preliminary questions and then asked “Bev, how much blood do you cough up at a time?” Mom held out the right palm of her hand, cupped it upwards, and said “about this much” …a handful of blood.

Mom went through the usual regime of chemo and radiation treatments during the month of July 2015 and was told to return on October 1st to meet again with the oncologist. Mom’s cancer didn’t improve over the months of August and September. Mom returned home to where the whole family cared for her until the last few days before her death on Christmas Day.

On Wednesday morning, December 23, 2015, my brother Brad scooped up our Mother in his arms, gently placed her in his SUV, and drove Mom to the Ian Anderson House, a beautiful hospice a short distance from the North shore of Lake Ontario in Oakville, Ontario. Mom died peacefully a few days later, on Christmas Day afternoon, surrounded by her family.

This is the story most people who knew Mom have been told. It’s factually correct. What’s missing from Mom’s story is that the bleeding and incessant coughing and clearing of her throat had started a year, maybe two years earlier. Mom had visited her general physician several times over the period but no further diagnosis or treatment or other follow-up took place (as far as we know).

During this time, Dad was not well. Dad’s kidneys were failing and he went to the renal clinic at Credit View Hospital 3 times a week, 3 hours per day. Mom drove Dad to dialysis every day and stayed with him until he was released each afternoon. Mom also cared for the 5 of us children. I was 58 years old at the time of Mom’s lung cancer diagnosis and my youngest brother Brad was 52. Each of us 5 kids had different challenges: divorce, health, and work issues, etc. Mom was quite literally run off her feet by her family as her (undiagnosed) lung cancer progressed and spread.

Mom had many retirement wishes that were never realized. With Dad being a retired Air Canada senior airline pilot and instructor, Mom especially looked forward to flying First Class and traveling abroad – Europe, in particular – because she had previously been unable to venture very far as a stay-at-home Mother with 5 kids. Mom especially wanted to go on one of those Rhine River cruises you see advertised on the television. None of this came to pass. The demands of her family (particularly healthcare issues in Dad’s case) resulted in Mom’s non-stop caring for her family to continue until the last 6 months of her life. Mom died at age 80.

What’s the note of caution to mothers? If you have sons or daughters that continue to demand your care, attention, and time – even into their adulthood (everyday tasks like cooking, cleaning, folding laundry, babysitting, etc.), resist the temptation.

Resist those maternal genes that kick in and make you feel obligated to put aside your personal happiness, personal aspirations, and personal desires. Your adult children will be able to figure things out on their own – it’s mandatory.

Live *your* life and live it to the fullest.

Best wishes for a long and happy life,
Michael

Leave a comment

Filed under Uncategorized

Web 7.0 DIDComm Agent Architecture Reference Model (DIDComm-ARM) 0.40 (December 18, 2022)

A Design Guide for Software Architects and Developers working on DIDComm Agent-based Software Systems

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

Web 7.0 is a unified software and hardware ecosystem for building resilient, trusted, decentralized systems using decentralized identifiers, DIDComm agents, and verifiable credentials.

Take what you need; leave the rest.

Michael Herman, Trusted Digital Web Project, Hyperonomy Digital Identity Lab, Parallelspace Corporation. January 2023.

This is the second public release of the Web 7.0 DIDComm-ARM whitepaper.

For a quick introduction, checkout the article Welcome to Web 7.0!.

Your comments and feedback on the DIDComm-ARM, its layered models, and Web 7.0 (seventh layer in the DIDComm-ARM) will be greatly appreciated.

You can find us on Twitter @ https://twitter.com/web7arch (hashtag #web7).

Download

Abstract

Figure 1. Web 7.0 High-Level Architecture Reference Model (WEB7-ARM)

The purpose of this document is to introduce and describe the DIDComm Agent Architecture Reference Model (DIDComm-ARM) and the DIDComm Notation. The latter is a graphical modeling language used to design and model DIDComm Agent-based software systems.

The goals for this document are three-fold:

  • Better understanding of the active components of DIDComm Agent-based software systems and how these components rely on and interact with each other,
  • Introduce a new graphical modeling language, DIDComm Notation, to aid architects and developers in visualizing new architectures and designs for DIDComm Agent-based software systems, and
  • Describe a layered architecture reference model, DIDComm-ARM, to help guide the design and creation of the broadest range of DIDComm Agent-based software systems possible.

DIDComm Notation contains elements for modeling:

  • Conventional REST/HTTP clients, agents, and services
  • DID Addressable REST/HTTP clients, agents, and services
  • DIDComm clients, agents, and services
  • DIDComm agents that utilize Verifiable Credential message attachments
  • DIDComm mesh networks
  • DIDComm user agents
  • Virtual web drives and keystores

Collectively, these categories of DIDComm Notation modeling elements (and their interrelationships) define the DIDComm Agent Architecture Reference Model (DIDComm-ARM). The DIDComm-ARM contains multiple layered architecture models:

  • Layer 0 REST/HTTP Agent Model
  • Layer 1 DID Addressable REST/HTTP Agent Model
  • Layer 2 DIDComm Agent Model
  • Layer 3 DIDComm Agent with Verifiable Credential Attachments Model
  • Layer 4 DIDComm Agent Mesh Network Model
  • Layer 5 DIDComm User Agent Model (Appendix A)
  • Layer 6 Web 7.0 DIDComm Agent Architecture Model (Appendix B)

The intended audience for this whitepaper is a broad range of professionals interested in furthering their understanding of DIDComm for use in software apps, agents, and services. This includes software architects, application developers, and user experience (UX) specialists; as well as people involved in a broad range of standards efforts related to decentralized identity, Verifiable Credentials, and secure storage.

The primary audience is software architects and developers designing and creating DIDComm Agent-based software systems[1].

This document is an independent work product produced by the author(s) and is neither a W3C, DIF, Sovrin Foundation, nor a ToIP work product – unofficial, official, or otherwise.

3 Comments

Filed under Uncategorized

Truth and Marketplace of Ideas

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

Also checkout: Facts, Opinions, and Folklore: A Preliminary Taxonomy

Research findings on the topics of:

  • Marketplace of Ideas
  • Facts, Opinions, and Folklore

1.  THE FACT/OPINION DISTINCTION: AN ANALYSIS OF THE SUBJECTIVITY OF LANGUAGE AND LAW

• The first, commonly associated with John Stuart Mill, 8 is that one receives a clearer perception of truth if it is the result of a “collision with error.”9 One can never be sure that an opinion which we seek to suppress is false.’0 To assume otherwise is to assume infallibility.” Hence, an individual who seeks truth must consider opposing opinions to sift the true from the false.'” The collision of adverse opinions is necessary in the search for truth.13

• These are the premises of the marketplace theory, in which the “consuming public in the marketplace of ideas,”19 ultimately determines which beliefs are true.20 Under this theory, “false ideas need not be suppressed, for the operation of the market ultimately will reject ideas that are in fact false.” 21

2. INSTITUTIONS IN THE MARKETPLACE OF IDEAS

• This Article brings them together, using the New Institutional Economics to describe the “speech institutions”—such as schools and universities—that play the same cost-reducing role in the marketplace of ideas as other institutions do in the market for goods and services.

• The market is an imperfect and frequently malfunctioning machine, and the costs of exchange add friction to its gears. This friction, which economists call “transaction costs,” includes the time and expenditure needed to find, evaluate, and obtain good ideas or products.9 And although Holmes’s metaphor does not account for them, these costs exist in the marketplace of ideas just as surely as they do in the economic market.

3. Abrams v. United States, 250 U.S. 616 (1919)

• [W]hen men have realized that time has upset many fighting faiths, they may come to believe even more than they believe the very foundations of their own conduct that the ultimate good desired is better reached by free trade in ideas—that the best test of truth is the power of the thought to get itself accepted in the competition of the market, and that truth is the only ground upon which their wishes safely can be carried out.

4. R.H. Coase, Advertising and Free Speech, 6 J. LEGAL STUD. 1, 27 (1977)

• “The rationale of the First Amendment is that only if an idea is subject to competition in the marketplace can it be discovered (through acceptance or rejection) whether it is false or not.”.

• Free speech, in Holmes’s framework, is worthy of constitutional protection precisely because—like the free flow of goods and services—it creates a competitive environment in which good ideas flourish and bad ideas fail.

5. The Fact/Opinion Distinction: An Analysis of the Subjectivity of Language and Law

• The collision of adverse opinions is necessary in the search for truth.13

• These are the premises of the marketplace theory, in which the “consuming public in the marketplace of ideas,”19 ultimately determines which beliefs are true.20 Under this theory, “false ideas need not be suppressed, for the operation of the market ultimately will reject ideas that are in fact false.” 21

• Under the First Amendment there is no such thing as a false idea. However pernicious an opinion may seem, we depend for its correction not on the conscience of judges and juries but on the competition of other ideas.

• The inherent indeterminacy of words makes any distinction between fact and opinion a subjective determination.

6. The taxonomy of evidence: experts, facts, opinions and the courts

• Opinion evidence is ordinarily inadmissible, but there is an exception when the person giving their opinion is an “expert”. An expert can give evidence of fact like anyone else, the only restriction being its relevance. A forensic pathologist (to use an example of Master Matthews) may give evidence about what they saw when they performed a post-mortem: blood here, lacerations there, discolouration everywhere. No permission is necessary for that sort of evidence. What they cannot give without permission is their expert opinion on the cause of death, for example (albeit the court may give permission because the expert, unlike most of us, has some useful qualification in doing so).

• Scots law identifies a third category of evidence which, we learn from Kennedy, requires a ruling as to admissibility. That is factual evidence, given by an expert, but which draws on their specialist knowledge or experience.

7. The Fact/Opinion Distinction: An Analysis of the Subjectivity of Language and Law

• Indeed, “[m]ost speech will contain some elements of fact, some of inference, some of emotion, and some of value judgment.’7 1 For example, assume a person observes a fellow classmate reading late on a Friday evening. The person then makes the statement, “John Doe is a diligent student.” This statement is neither purely fact nor purely opinion. The fact that the student was reading late on a Friday evening may be verified. However, the person has inferred from the fact of reading that the student was studying. The statement now includes some degree of opinion or belief. The student, in fact, could have been reading the latest science fiction best seller merely for pleasure. The statement may also reflect the person’s emotions toward, and judgments of, that student. Rather than characterizing the student as diligent, the observer could have described the student as “an egghead.” Both statements would have originated from the same verifiable fact of reading, however, both are inseparable from the observer’s opinion of that student.

3 Comments

Filed under Uncategorized

Welcome to Web 7.0! (overview)

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

Web 7.0 is a unified software and hardware ecosystem for building resilient, trusted, decentralized systems using decentralized identifiers, DIDComm agents, and verifiable credentials.

Take what you need; leave the rest.

Michael Herman, Trusted Digital Web Project, Hyperonomy Digital Identity Lab, Parallelspace Corporation. January 2023.
Figure 1. Welcome to Web 7.0!

Web 7.0 is being built using and is conformant with the DIDComm-ARM; more specifically, Layer 6 of the DIDComm-ARM (See Figure 2 below).

Figure 2. DIDComm Agent Architecture Reference Model (DIDComm-ARM): Layer 6 Web 7.0 DIDComm Agent Architecture Model

Layer 6 is one of the 7 layers in the DIDComm Agent Architecture Reference Model (DIDComm-ARM) (see Figure 3 below).

Figure 3. DIDComm Agent Architecture Reference Model (DIDComm-ARM): 7 Layer Model (Feature Matrix)

For the complete story, download the Web 7.0 DIDComm Agent Architecture Reference Model (DIDComm-ARM) whitepaper from here:

If you prefer to listen to a narrated version of the Web 7.0 DIDComm-ARM whitepaper, checkout this playlist:

No REST for the wicked!

APPENDIX A – Web 7.x Versions and DID-DOS Distributions

Figure 4. DID-DOS 7.0 Genealogy: 50 Years in the Making
Figure 5. DID-DOS 7.0 Roadmap Metamodel
Figure 6. Web 7.x Versions and DID-DOS Distributions
Figure 7. DID-DOS 7.0 Reference Distribution: Roadmap

APPENDIX B – Web 7.0 Body of Knowledge: Content Map

Figure 8. Web 7.0 Body of Knowledge: Content Map

APPENDIX C – Web 7.0 Technology Adoption Model

Figure 9. Web 7.0 Technology Adoption Model

Reference: https://www.linkedin.com/pulse/blockchain-foundational-technology-michael-herman/

APPENDIX D – “DIDFax” Windows Printer Driver Scenario

Figure 10. “DIDFax” Windows Printer Driver Scenario

2 Comments

Filed under Uncategorized

Web 7.0 DIDComm Agent Architecture Reference Model (DIDComm-ARM) 0.27

A Design Guide for Software Architects and Developers working on DIDComm Agent-based Software Systems

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

Your comments and feedback on the DIDComm-ARM, its layered models, and Web 7.0 (seventh layer in the DIDComm-ARM) will be greatly appreciated.

You can find us on Twitter @ https://twitter.com/web7arch (hashtag #web7).

UPDATED: The last version of the DIDComm-ARM whitepaper can be found here:

3 Comments

Filed under Uncategorized

Web 7.0 Application Note: “DIDFax” Windows Printer Driver Scenario

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

The purpose of this Web 7.0 application note is to describe the “DIDFax” Windows Printer Driver scenario within the context of a cardiac specialty physician’s clinical setting. The “DIDFax” Windows Printer Driver solution concept uses DIDComm Messages, DIDComm Message Attachments, and DIDComm Agents using Layer 6 of the Web 7.0 DIDComm-ARM model[1].

This document was produced to address the following goals:

  • Illustrate how a DIDComm Agent-based software system can deliver high business value by solving a communications problem within the healthcare ecosystem.
  • Illustrate how Web 7.0 DIDComm-ARM models and DIDComm Notation can be used to assist in the design and visualization of DIDComm Agent-based software systems.

NOTE: The solution concept (see Download below) is made possible by using DIDComm, DIDComm Messaging, and DIDComm Agents (as described in the DIDComm-ARM). The solution concept is not achievable using the classical notion of a digital identity wallet.

Download


[1] Web 7.0 DIDComm Agent Architecture Reference Model (DIDComm-ARM)

(https://hyperonomy.com/2022/12/07/web-7-0-didcomm-agent-architecture-reference-model-didcomm-arm/)

Leave a comment

Filed under Uncategorized