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

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

Michael Herman, Blockchain Developer, Enterprise Architect and Data Scientist: #Graphitization Inventor

COPYRIGHT © 2016-2017 by Michael Herman, Seattle, Washington and Toronto, Canada. All rights reserved.

Michael Herman is an expert when it comes to the mathematical modeling, analysis, and visualization of almost everything:

  • Large enterprise organizations,
  • Commercial, global-scale, cloud services platforms,
  • Organization principles and belief systems,
  • Human platforms,
  • Aircraft engines, and
  • Muscle cars.

Michael is the inventor of the #Graphitization Continous Transformation Model – a closed-closed loop feedback process for the ingestion, modeling, analysis, visualization, systems optimization, and life cycle management of any type of strategy, system, asset, architecture, or process.

progressive-ea-model-1-0-11-peam4-operational-data-chasm

Figure 1. #Graphitization Continuous Transformation Model

A key concept of #Graphitization is the implementation of Transformative Changes that result in positive increases in business value in the system being modeled.

#Graphitization

What is #Graphitization?

#Graphitization is a data science and enterprise architecture framework and process model for modeling, ingesting, organizing, analyzing, and visualizing any domain of endeavor by using graphs – networks of connected objects and relationships with each object and relationship annotated with additional descriptive information (metadata).

The primary applications of #Graphitization are:

  • System optimization,
  • Systems life cycle management, and
  • Transformative Change in resulting in positive increases in business value for the system being studied.

A system is defined as any collection of strategies, system components, assets, architectures or processes.

References

#Graphitization Continuous Transformation Model

The #Graphitization general model is described in Figure 2. as it applies to the design and optimization of large enterprise organizations.

progressive-ea-model-1-0-11-peam4-operational-data-chasm

Figure 2. #Graphization Continuous Transformation Model: Large Enterprise Organizations

The same model can also be used to improve the design and operation of many different types of systems:

  1. Large scale enterprise organizations (public and private sector)
  2. Aircraft engines, muscle cars, and other high-performance engine systems
  3. Commercial, global-scale, cloud services platforms
  4. Automated service composition of cloud services-based data systems
  5. Large collaborative ecosystems: employee groups, business partners, social networks
  6. Large ecosystems of competing or competitive business organizations
  7. Organization principles and belief systems
  8. Conventions software applications and architectures: desktop, server, and web apps
  9. International standards for visual modeling languages
  10. Parallelspace ModelMate
  11. Enterprise Data Management
  12. Internet of Things (IoT)
  13. Architecture Reference Models

Standards

NEO Enhancement Proposal (NEP) Standards Author

Projects and Publications

0. SerentityData Graph

Model-based off-chain and on-chain (blockchain) graph data creation, migration, visualization, and analysis

Abstract

SerentityData Graph is an entity-relationship modeling, serialization, and graph analysis solution that supports development of traditional full-stack and blockchain smart contract applications. SerentityData features tight Neo4j integration for on-chain & off-chain graph data visualization and analysis.

Description

SerentityData Graph is an open source, entity-relationship modeling, serialization, and graph data visualization and analysis solution that supports the development of traditional full-stack, blockchain-based smart contract, and Neo4j graph database applications.

Starting from a single data model, SerentityData supports the automatic code generation of entities and relationships that support symmetric development of: (a) off-chain data in traditional multi-tier full-stack applications, (b) on-chain data management for blockchain-based distributed ledger technology apps (dApps), and (c) Neo4j enterprise graph applications.

SerentityData features complete life-cycle integration with Neo4j for on-chain and off-chain graph data creation, migration, visualization, and analysis. Live code walk-throughs and demonstrations will enable you to begin using SerenityData and Neo4j immediately. Github: https://github.com/mwherman2000/serentitydata-compiler

Resources

My blog: https://hyperonomy.com/

Related blog posts

  1. Michael Herman, Blockchain Developer, Enterprise Architect and Data Scientist: #Graphitization Inventor https://hyperonomy.com/2017/05/18/michael-herman-inventor-of-graphitization/
  2. #Graphitization of the Enterprise https://hyperonomy.com/2017/01/02/graphitization-of-the-enterprise/
  3. Tokenize Every Little Thing (ELT) https://hyperonomy.com/2018/01/24/tokenization-of-every-little-thing-elt/
  4. #Graphitization of .NET Applications: Marrying Open EA Data with Graph Databases https://hyperonomy.com/2016/10/19/crossing-the-ea-chasm-marrying-open-ea-data-with-graph-databases/
  5. #Graphitization of Ray Dalio’s Principles: Iteration 1 https://hyperonomy.com/2016/12/29/graphitization-of-ray-dalios-principles/
  6. #Graphitization of Ray Dalio’s Principles: Iteration 2 https://hyperonomy.com/2016/12/30/graphitization-of-ray-dalios-principles-iteration-2/
  7. Crossing the EA Chasm: #Graphitization of ArchiMate 3.0 – Iteration 1 https://hyperonomy.com/2017/01/17/crossing-the-ea-chasm-graphitization-of-archimate-3-0/
  8. Crossing the EA Chasm: #Graphitization of ArchiMate 3.0 – Iteration 2 https://hyperonomy.com/2017/02/08/crossing-the-ea-chasm-graphitization-of-archimate-3-0-iteration-2/
  9. Crossing the EA Chasm: Automating Enterprise Architecture Modeling #1 https://hyperonomy.com/2016/10/22/crossing-the-ea-chasm-automating-enterprise-architecture-modeling/
  10. Crossing the EA Chasm: Automating Enterprise Architecture Modeling #2 https://hyperonomy.com/2016/11/04/crossing-the-ea-chasm-automating-enterprise-architecture-modeling-2/
  11. Crossing the EA Chasm: ArchiMate “Keep Calm and Have IT Your Way” https://hyperonomy.com/2016/11/17/crossing-the-ea-chasm-archimate-have-it-your-way/
  12. Crossing the EA Chasm: Open Repository Strategies for Enterprise Architecture https://hyperonomy.com/2016/10/04/the-ea-chasm-open-repository-strategies-for-enterprise-architecture/
  13. Crossing the EA Chasm: Enterprise Architecture Diagrams Your Grandmother (and CIO) Will Love https://hyperonomy.com/2016/10/13/archimate-diagrams-your-grandmother-and-cio-will-love/
  14. #Graphitization of ArchiMate: Getting MMOR from ArchiMate using the ModelMate Master Online Repository https://hyperonomy.com/2017/02/10/crossing-the-ea-chasm-how-to-use-the-modelmate-online-repository-mmor/
  15. #Graphitization of the Amazon Leadership Principles (introducing Personal Leadership Principle Maps) – Iteration 1 https://hyperonomy.com/2017/05/08/amazons-principles/
  16. What are the differences between improving the design (and operation) of an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale? https://hyperonomy.com/2017/04/10/whats-the-difference-between-improving-the-design-and-operation-of-an-aircraft-engine-a-muscle-car-a-large-enterprise-and-a-commercial-global-cloud-services-platform/

Live Neo4j Models

  1. http://hobby-icgaeohcoeaggbkeabhldpol.dbs.graphenedb.com:24789/browser/ Userid: ModelMate_Master_Datasets10 Password: YqeZAH4ODEJqglkEsK5p

YouTube Channel: https://www.youtube.com/playlist?list=PLU-rWqHm5p46bIDXPNf4c2JP_AOkopnV5

  1. 12. NEO Persistable Classes (NPC) Platform 2.1: Preview https://www.youtube.com/watch?v=N-jiJOZwiFg&list=PLU-rWqHm5p46bIDXPNf4c2JP_AOkopnV5&index=5
  2. NEO Persistable Classes (NPC) Platform 2.0: Deep Dive https://www.youtube.com/watch?v=Nj4-m2o94VE&list=PLU-rWqHm5p46bIDXPNf4c2JP_AOkopnV5&index=6
  3. NEO Persistable Classes 1.0: Deep Dive (Video 2 of 3) [Update 1] https://www.youtube.com/watch?v=qwteL1BiCjM&list=PLU-rWqHm5p46bIDXPNf4c2JP_AOkopnV5&index=7
  4. NEO Persistable Classes Platform 2.2: Structured Storage & Reusable, Indexed, Non-Fungible Entities https://www.youtube.com/watch?v=vnAxyCAZ1ec&list=PLU-rWqHm5p46bIDXPNf4c2JP_AOkopnV5&index=10

Related Github Projects

  1. SerentityData Entity Compiler (serentitydata-compiler) https://github.com/mwherman2000/serentitydata-compiler/blob/master/README.md
  2. NEO Persistable Classes (NPC) Compiler 2.1 (npcc) – Compiler for the NEO Persistable Classes (NPC) Platform 2.1 https://github.com/mwherman2000/neo-npcc2
  3. NEO Persistable Classes V1.0 – An Efficient Object-Oriented Framework for C#.NEO Smart Contract Development (ORIGINAL) – https://github.com/mwherman2000/neo-persistibleclasses

Recognition

  1. NeoDraw – NEO Persistable Classes Platform 2.0: NEO-Microsoft dApp Competition (4th place prize – USD$15,000) – https://neo.org/blog/details/3074 and https://neo.org/awards.html

Keywords

  • blockchain on-chain data modeling symmetric programming data management .NET C# NEO Stratis Ethereum Technical Case Study Developer Best Practices

1. Large scale enterprise organizations (public and private sector)

The first applications of #Graphitization were in the field of traditional enterprise architecture modeling and analysis:

  • Business Architecture
  • Application Architecture
  • Technology/Infrastructure Architecture

References

  1. #Graphitization of the Enterprise
  2. Crossing the Chasm: Progressive Enterprise Architecture Model (PEAM)
  3. Progressive Enterprise Architecture Maps – Update 2
  4. Using ArchiMate 2.1 to Model Product or Service Markets
  5. ArchiMate 3.0: What is the preferred way to model a Server Farm?
  6. Crossing the EA Chasm: Enterprise Architecture Diagrams Your Grandmother (and CIO) Will Love
  7. Crossing the EA Chasm: Annotating Your EA Models with RACI Roles
  8. Crossing the EA Chasm: Automating Enterprise Architecture Modeling #1
  9. Crossing the EA Chasm: Automating Enterprise Architecture Modeling #2
  10. Crossing the Enterprise Architecture Chasm
  11. ModelMate Architecture Reference Model
  12. What are the differences between improving the design (and operation) of an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale?
  13. Modeling a Company and Its Locations, Markets, Employees, Investors & Roles: Proposals, Wishes & Dreams

2. Aircraft engines, muscle cars, and other high-performance engine systems

It turns out that the modeling and analysis of any complex system is an ideal candidate for #Graphitization.

References

  1. What are the differences between improving the design (and operation) of an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale?

3. Commercial, global-scale, cloud services platforms

One particularly important application is the modeling and analysis of very large, commercial, global-scale, cloud services platforms.

References

  1. What are the differences between improving the design (and operation) of an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale?

4. Automated service composition of cloud services-based data systems

Call the solution “Expedia for Microsoft Azure/AWS/SFDC/…” or whatever you prefer, today’s commercial cloud services platforms are still a pain in the ass to use for creating non-trivial applications.  Left, right, and center you have to hand-code a myriad of worker processes simply to reformat and pass data around.

#Graphitization is an optimal approach for modeling the underlying cloud services platform services catalog.

References

  1. MS Azure is a bit of a bucket of bolts …very good bolts …but relative to the other IoT vendors, a bucket of bolts.
  2. What are the differences between improving the design (and operation) of an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale?
  3. Microsoft Azure Stack POC Architecture Reference Model (ARM): ArchiMate Model – version 1-0-7 – April 30, 2016

5. Large collaborative ecosystems: employee groups, business partners, social networks

Project “Boston” is named after some potential business partners and the embryo for the idea coming from my months as a founding Groove Networks business partner (including many of my most important relationships that I still maintain today).

6. Large ecosystems of competing or competitive business organizations

Modeling of large ecosystems of competing/competitive business organizations is a straightforward #Graphitization use case.

7. Organization principles and belief systems

On the surface, the #Graphitization of principle and belief-based frameworks is pretty straightforward but this is because the basic #Graphitization serves as the substrate for many advanced data ingestion, analysis, and visualization projects.

Below are the results of the  #Graphitization of two principle and belief-based frameworks:

  • Bridgewater Associates: Ray Dalio’s Principles
  • Amazon: Jeff Bezos’ Amazon Leadership Principles

References

  1. #Graphitization of Ray Dalio’s Principles: Iteration 1
  2. #Graphitization of Ray Dalio’s Principles: Iteration 2
  3. #Graphitization of the Amazon Leadership Principles (introducing Personal Leadership Principle Maps) – Iteration 1

8. Conventional software applications and architectures: desktop, server, and web apps

Modeling of complex, multi-language, multiple runtime software environments is a use case that is an ideal application of #Graphitization.

References

  1. #Graphitization of .NET Applications: Marrying Open EA Data with Graph Databases
  2. Pinc-A Tool For Maintaining Configurable Software in Pascal1
  3. Pinc-A Tool For Maintaining Configurable Software in Pascal2
  4. Pinc-A Tool For Maintaining Configurable Software in Pascal3
  5. Pinc-A Tool For Maintaining Configurable Software in Pascal4
  6. Pinc-A Tool For Maintaining Configurable Software in Pascal5

9. International standards for visual modeling languages

A significant investment has been made in applying #Graphitization to language modeling; specifically, languages for enterprise architecture like ArchiMate.

ArchiMate References

  1. Using ArchiMate 2.1 to Model Product or Service Markets
  2. ArchiMate 3.0: What is the preferred way to model a Server Farm?
  3. How do I model “X” using ArchiMate?
  4. Crossing the EA Chasm: ArchiMate “Keep Calm and Have IT Your Way”
  5. Crossing the EA Chasm: ArchiMate Art
  6. Crossing the EA Chasm: Re-visioning the ArchiMate Specification
  7. Crossing the EA Chasm: Reflections on the Current State of ArchiMate
  8. Crossing the EA Chasm: Re-visioning ArchiMate 3.0 Relations as Verbs
  9. Crossing the EA Chasm: Re-visioning ArchiMate 3.0 Elements as Adjectives [WIP]
  10. Crossing the EA Chasm: #Graphitization of ArchiMate 3.0 – Iteration 1
  11. Crossing the EA Chasm: #Graphitization of ArchiMate 3.0 – Iteration 2 (long but meaty)
  12. #Graphitization of ArchiMate: Getting MMOR from ArchiMate using the ModelMate Master Online Repository

10. Enterprise Data Management

Modeling and analyzing enterprise data structures and stores is a common application of #Graphitization; including the modeling of taxonomies and master data.

References

  1. RE: Managing Master Data With ArchiMate

11. Parallelspace ModelMate

Parallelspace ModelMate is an approach (platform and language framework) for creating domain specific languages (DSLs) for enterprise architecture.  It is realized using #Graphitization and the ArchiMate enterprise architecture modeling language.

References

  1. Crossing the Enterprise Architecture Chasm
  2. Crossing the EA Chasm: Open Repository Strategies for Enterprise Architecture
  3. ModelMate Architecture Reference Model

12. Internet of Things (IoT)

IoT is an interesting beast.  It is a reference to an application service for processing raw events from a device or dynamically generated events from a software system.  IoT also defines a conceptual software and data flow architecture that can also be used for the dynamic creating and maintenance of complex systems such as large enterprise architectures.

References

  1. Subject: MS Azure Services: Is there an overarching architectural vision?
  2. MS Azure is a bit of a bucket of bolts …very good bolts …but relative to the other IoT vendors, a bucket of bolts.
  3. Crossing the EA Chasm: “Where does IoT [Internet of Things] fit in?”

13. Architecture Reference Models (ARMs)

An ARM is easily modeled (and analyzed) using #Graphitization.  SharePoint and Azure Stack are two good examples.

References

  1. ARMs for Model-Driven LOB apps: SharePoint 2013/SharePoint 2016 [Oct. 24, 2016]
  2. Microsoft Azure Stack POC Architecture Reference Model (ARM): ArchiMate Model – version 1-0-7 – April 30, 2016

General References

  1. Continuous Transformation and Transformative Change are key principles of the Total Enterprise Architecture Model (TEAM) (click here)
  2. To dig deeper, check out Graphitization of the Enterprise (click here)
  3. [Enterprise Architecture, Big Data, CRM, ERP, …] Tools and Methods Don’t Generate Business Value (click here)
  4. Crossing the EA Chasm: The Surveyor

Best regards,

Michael Herman
Enterprise Architect and Data Scientist
Parallelspace Corporation
M: 416 524-7702
E: mwherman@parallelspace.net
B: http://hyperonomy.com
L: https://www.linkedin.com/in/mwherman/recent-activity/posts/
Skype: mwherman2000

Living at the intersection of Enterprise Architecture, Enterprise Knowledge, and Data Science

  • ArchiMate is registered trademark of The Open Group.

1 Comment

Filed under ArchiMate, Architecture Reference Models, Automated Application Architecture Analysis, Automated Enterprise Architecture Modeling, Graphitization, How do we think, Microsoft Azure, ModelMate Information Architecture for ArchiMate, ModelMate Information Architecture for Languages

What are the differences between improving the design (and operation) of a smart city, an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale?

COPYRIGHT © 2016-2017 by Michael Herman, Toronto, Canada. All rights reserved. [Updated June 16, 2018]

Question: What are the differences between improving the design (and operation) of:

  • a smart city,
  • an aircraft engine,
  • a muscle car,
  • a large enterprise, and/or
  • an integrated commercial global cloud services platform
  • …all running at hyperscale?

Answer: None.

Scroll down to see the use cases; then the list of resources at the bottom of this article.

Use Case 1: Aircraft engine, and
Use Case 2: 
Muscle car

Continuous Transformation 2

Figure 1. Continuous Transformation Model: Aircraft Engines and Muscle Cars

Use Case 3: Smart city,
Use Case 4: Large enterprise operating at hyperscale, and
Use Case 5: 
Integrated commercial global cloud services platform operating at hyperscale

Continuous Transformation 1.png

Figure 2. Continuous Transformation Model: Smart Cities, Large Enterprises, and Cloud Services Platforms

Diving Deeper: #Graphitization

To go deeper, checkout #Graphitization of the Enterprise (click here) as well as the list of references below.

progressive-ea-model-1-0-9-peam3-ea-chasm-auto-dots

Figure 3. #Graphitization Continuous Transformation Model

 

progressive-ea-model-1-0-11-peam5-1010

Figure 4. Continuous Transformation Framework: Process Groups and Activities

References

  1. Michael Herman, Blockchain Developer, Enterprise Architect and Data Scientist: #Graphitization Inventor  (click here)
  2. Continuous Transformation and Transformative Change are key principles of the Total Enterprise Architecture Model (TEAM) (click here)
  3. To dig deeper, check out Graphitization of the Enterprise (click here)
  4. [Enterprise Architecture, Big Data, CRM, ERP, …] Tools and Methods Don’t Generate Business Value (click here)

Best regards,

Michael Herman
Enterprise Architect and Data Scientist
Parallelspace Corporation
M: 416 524-7702
E: mwherman@parallelspace.net
B: http://hyperonomy.com
L: https://www.linkedin.com/in/mwherman/recent-activity/posts/
Skype: mwherman2000

Living at the intersection of Enterprise Architecture, Enterprise Knowledge, and Data Science

1 Comment

Filed under ArchiMate, Architecture Reference Models, Crossing the EA Charm, Data Science, Enterprise Architecture, Graphitization, How do we think, IoT, Space Flight

Michael Herman: Award-winning Author, Invited Speaker, Illustrator, and Trainer

COPYRIGHT © 2016-2017 by Michael Herman, Toronto, Canada. All rights reserved.

Feel free to contact me at:

PARTIAL PORTFOLIO

All of the publications below are full-length white papers or technical notes – unless noted otherwise (e.g. presentations, training materials, online product help).

Microsoft Live Communications Server

Client: Microsoft Corporation Live Communications Server Product Group / Microsoft IT Showcase

Microsoft SharePoint Products and Technologies

Client: Microsoft Corporation SharePoint Product Group / Microsoft IT Showcase

Microsoft Exchange Server

Client: Microsoft Corporation Exchange Server Product Group / Microsoft IT Showcase

Metalogix Replicator for SharePoint

Client: Metalogix, market leading provider of solutions to move, manage and protect content within enterprise collaboration platforms in the cloud and on-premises.

Microsoft “Alchemy”

Client: Microsoft Web Services Product Group / Microsoft IT Showcase

Parallelspace Vulture

Client: Parallelspace Corporation

Tzunami K-Wise Deployer

Client: Tzunami

Leave a comment

Filed under ArchiMate, Architecture Reference Models, Crossing the EA Charm, Enterprise Architecture, Enterprise Architecture Chasm, Graphitization, How do we think, ModelMate Information Architecture for ArchiMate, ModelMate Information Architecture for Languages

#Graphitization of the Enterprise

COPYRIGHT © 2016-2017 by Michael Herman, Toronto Canada. All rights reserved. [Updated June 16, 2018]

This article is the first in a series on #Graphitization. Click here to explore the other articles in this series.

Reprinted from #Graphitization of the Enterprise on LinkedIn.

Move beyond digitalization of the enterprise to graphitization of the enterprise. Here’s a great diagram that explains this concept. (click on the diagram to enlarge it)

graphitization-new-world-of-it
Figure 1. The New Model of IT

Graphitization of not only all of your corporate information assets across all of your constituencies and stakeholders – at the data, application entity, and business object level – but also the graphitization of all of the interconnections between every business process, application system, infrastructure component, cloud service, vendor/service provider, and business role that uses, manages, or stores corporate information (Crossing the EA Chasm: Automating Enterprise Architecture Modeling #2).

Use graphitization to make your existing corporate information more available, more usable, and more informative. Graphitization enables you to “Keep Calm and Have IT Your Way“.

What is #Graphitization?

#Graphitization is a data science and enterprise architecture-inspired framework and process model for modeling, ingesting, organizing, analyzing, and visualizing any domain of endeavor by using graphs – networks of connected objects and relationships with each object and relationship annotated with additional descriptive information (metadata).

The primary applications of #Graphitization are:

  • System optimization,
  • Systems life cycle management, and
  • Transformative Change in resulting in positive increases in business value for the system being studied.

A system is defined as any collection of strategies, system components, assets, architectures or processes.

Using #Graphitization

Use graphitization of your organization to help close both the Enterprise Architecture Chasm and the Operational Data Chasm. See below.

progressive-ea-model-1-0-11-peam4-operational-data-chasm
Figure 2. Continuous Transformation Framework: Enterprise Architecture Chasm and Operational Data Chasm

progressive-ea-model-1-0-11-peam5-1010
Figure 3. Continuous Transformation Framework: Process Groups and Activities

To learn more about other applications of graphitization, check out the following articles:

Best regards and best wishes for the New Year,

Michael Herman (Toronto)
Parallelspace Corporation
mwherman@parallelspace.net

6 Comments

Filed under continuous transformation, Crossing the EA Charm, Data Science, Digital Transformation, Enterprise Architecture, Enterprise Architecture Chasm, Graphitization, ModelMate, Operational Data Chasm, Progressive Enterprise Architecture Map (PEAM)

Mapping the Web 7.0 DIDComm/HTTP Architecture Reference Model to the TOIP Trust Spanning Layer Framework

Copyright (c) 2022-2023 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.

Leave a comment

Filed under Uncategorized

Web 7.0 DIDComm-ARM vs. TBD Web5 DWP Stack

Here’s a link to the voice-over/narrative for the following slides: https://youtu.be/1XnPWmpkGro?t=630s

Copyright (c) 2022-2023 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.

Leave a comment

January 18, 2023 · 11:56 am

DIDComm Message Attachment Types

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

Here’s a sampling…

NOTE: Verifiable credentials are an obvious DIDComm Message Attachment Type. For this reason, VCs are missing from the following list.

Leave a comment

Filed under Uncategorized

One’s Journey to the Grave – Hunter S. Thompson

“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!”

― Hunter S. Thompson, The Proud Highway: Saga of a Desperate Southern Gentleman, 1955-1967

Leave a comment

Filed under Uncategorized

Hyperledger Identity Implementers WG – January 12, 2023

Mission

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.

Other Web 7.0 Resources

Also check out Welcome to Web 7.0 (including a link to the whitepaper): https://hyperonomy.com/2022/12/12/welcome-to-web-7-0/

Today’s Presentation

Click here to download the presentation:

Leave a comment

Filed under Uncategorized

Unification

Suppose you have 3 football teams:

  1. Buffalo Bills NFL football team
  2. Machester United UK football team
  3. Local high school football team

What does it mean to unify these 3 organizations? Is it possible? What would it take to unify these 3 organizations?

Let’s start with a common cause/purpose/vision/mission. Without these, the goal of unification is impossible to attain.

Leave a comment

Filed under Uncategorized

DIDComm Agents vs. Identity Wallets: Litmus Test

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

Application Scenario

How would you create a #unified #decentralized software system whose scope includes:

a. Global Air Traffic Control #ATC

b. Aircraft Crew Scheduling #CrewSched

c. Baggage Handling, and Tracking #BagBash

d. Passenger Ticketing, Seating, and Credentialing #PTSC

e. Food and Beverage Management #FoodBev

…using decentralized technologies like:

  • Decentralized Identifiers
  • DIDComm Agents
  • Verifiable Credentials

Meet Freddy…

Leave a comment

Filed under Uncategorized

Which design represents the smarter choice?

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

Figure 1. Which design represents the smarter choice?

Anyone who has owned a phone and a wallet knows the answer.

Leave a comment

Filed under Uncategorized

My Favorite Microsoft Stories

0. Alias Upfront for Windows

What are your favorite Microsoft stories? Here’s my zero’th favorite… (#0 in my #FavoriteMicrosoftStories series)

#THT – Alias #Upfront for Windows – “The most innovative new graphics product for Windows 3.0” – Bill Gates, CEO, Microsoft.

YouTube: https://www.youtube.com/watch?v=Ihisz51Qiew

[Alias] seized the opportunity to purchase the Spacemaker technology and launched UpFront, a low-cost 3D Mac and Windows based package for architects. Alias achieved a major coup by impressing Bill Gates, who mentioned Upfront during a major Microsoft conference as a particularly innovative application under Windows. “In the graphics area, I picked Upfront from Alias Research. It is really an incredible tool for making sure the design is exactly right”, said the Chairman of Microsoft.

James Boritz and I and Ming Mah and Richard Brath and Dan Whitely and Jon Steinberg are the team that brought Alias Upfront for Windows to life – in a back room on the 3rd floor. We also used the same code base to build Alias Upfront for the Mac. Upfront didn’t generate a lot of revenue ($2 million? …or was it $200,000?) but it was Alias Research’s very first desktop software product. We were and are very proud of what we accomplished.

Other members of the cast: Alistair Banks Bill Gates Sara Spalding.

1. IE4 and the Java Jam

What are your favorite Microsoft stories? Here’s one of my mine… (#1 in my #FavoriteMicrosoftStories series)

One of my favorite MS stories involves IE4 and one of the largest banks in Canada, one of Microsoft’s largest customers headquartered here in Toronto, around Spring 1997 – maybe ’96 (May 15th actually …I’ll never forget that date). The bank had committed themselves to using server-side Java before there was any hint of server-side Java apps, J2EE, etc. They were using the IE4 Java VM at a time when we (MS) were happy to have the VM running “dancing elephants” in IE for 24 hours without a crash. We never thought of using the MS VM to run what was at the time “the world’s largest server-side Java application”.

The bank’s Java app would crash again and again. The bank blamed our VM because our VM was the only one that would run the app at all (not the IBM Hersley VM, not the VM from Sun Microsystems).

CharlesF and I ended up going head-to-head on this …for me it was all about what support is MS willing to provide MS’s largest enterprise customers; Charles’ job was to work for BradSi and, among other responsibilities, deflect any distractions that would delay shipping IE4 …remember the days of “The Browser Wars”?

We each chose our teams. Bill Gates was already down the throats and backs of BradSi and Charles to not work on this. SteveB came to Toronto and got a huge strip torn off him – up one side and down the other – by an ex-IBM bank VP whose husband at the time was the IBM account executive for the same bank. SteveB was instantly on my team.

At the MGS in Orlando a few months later, Bill was walking around making himself available for the MS field people that were there (an MS internal WW sales conference). I started to walk up to Bill and to explain my role in the “Java Jam” as we called it and had only gotten a couple words out when SteveB pounced on Bill in front of dozens of MS people – his pointer fingers high up in the air pointing down at Bill – virtually yelling at him to listen to the story I had and to learn what it means to be passionate about our enterprise customers.

Later that evening, I got a call to meet with SteveB in his hotel suite. Just me and him …and PaulMa, CharlesF and the MS Java VM team on the other end of a conference phone. Steve was on one side of an L-shaped couch when I arrived eating cashews or almonds from a can. I sat on the other side of the couch. The phone was in the middle on the coffee table. The call was already in progress.

The best thing about this meeting was that everyone was on the same page. We just needed someone to make a damn decision: yes or no, are we going to fix this problem?

Steve started by asking Paul two questions: 1) “Is what the bank doing on-strategy or off-strategy?” Paul replied “It’s not off strategy”. Then Steve asked question 2: “OK then, what are we doing to help the bank?”

Almost immediately PaulMa offered to call the VP at the bank. I gestured to Steve sitting across from me – no further than 2-3 feet away – and said “We’ve already had a lot of people talking to the bank”. “What we need is a decision. A yes or a no. Are we going to fix this problem or not? That’s all they want to hear”.

Steve immediately leaned over to me and whispered “If Paul is going to call, Paul is going to fix this”. We agreed Paul would call the VP as soon as they could synchronize their schedules.

Afterwards Steve said “If something like this ever happens again, call me right away. Call me directly. Don’t let it happen again”. We shook hands and I left.

The bug (a multi-threading sync data structure being overwritten) was fixed by the end of the following weekend …in time for PaulMa’s concall with the bank’s VP on the Tuesday afternoon.

After that, it used to freak people out in the Canadian sub when SteveB would high-five me in the hallway. It wasn’t worth trying to explain unless you knew the whole story.

What’s your Microsoft story?

Other members of the cast: Bill Gates Charles Fitzgerald Steve Wild Oliver Sharp.

Related: https://www.justice.gov/atr/reply-brief-petitioner-united-states-america-us-v-microsoft-corp

2. Cancellation of the Local Web Storage System (LWSS) Project

What are your favorite Microsoft stories? Here’s my second favorite… (#2 in my #FavoriteMicrosoftStories series)

Who remembers what famous Microsoft event happened on December 17, 2000?

How about the cancellation of the Local Web Storage System (LWSS) project? …preventing it from shipping with “Outlook 10” (aka Office XP).

I remember it well because the next day I was asked to present at the MS Collaboration Partner Advisory Council meeting at the Atlantis Hotel in Nassau. Not a bad gig except about every 45 minutes Robert Ginsberg would start to shake his head and shout out “How could you Microsoft do this to us?”. This went on for the full 2-day event – before and after every presentation.

Robert was right to be upset. Being the cofounder of one of the leading Exchange Server WSS development shops in the world, Robert, and his business partner Andy Sakalian, had invested enormous amounts of time and effort learning about LWSS – inside and out – and had built several tools to help prospective LWSS ISVs build custom solutions on top of LWSS and “Outlook 10”.

Schitt happens – everywhere – but it was always more fun when it happened at Microsoft.

p.s. You’d like an upbeat ending? Andy introduced me to a jeweler from Montreal who taught me how to play Black Jack “the real way” and what finer venue than sitting at the tables at the Altantis Casino. I made USD$900 that evening. I had to stay up until 4am but I did clear $900. ..that’s about $75/hour. Back then there were a lot easier ways to make $900/day …a lot easier.

What’s your Microsoft story?

Other members of the cast: Robert Ginsburg.

Related: http://windowsitpro.com/exchange-server/office-designer-and-local-web-storage-system-absent-office-10-release

3. PDC 2001: Unified Storage Strategy

What are your favorite Microsoft stories? Here’s my third favorite… (#3 in my #FavoriteMicrosoftStories series)

There was a series of events I often attended (before and) after I left the mothership in 2001: the Microsoft Professional Developer Conferences (PDC). They have since gone away. …the conferences I mean. (I think there are still lots of professional Microsoft developers.)

Mary-Jo Foley, an excellent journalist, writer and research analyst, would also attend these events. Disclosure: Mary-Jo Foley is also a friend on Facebook (currently) but we really don’t know each other that well.

At these events, Mary-Jo would often be first in line at the microphones during the Bill Gates executive Q&A session. One of her favorite questions was to ask Bill how Microsoft was progressing with its unified storage strategy based on SQL Server …especially the following question: When was Exchange Server going to ship using a SQL Server-based storage system? Bill always had a good answer.

This was also one of my favorite BillG questions and, unknown to Mary-Jo as far as I know, it became a race for me to try and ask the unified storage question before she could. If I asked it first, she would mention me and my affiliation in her coverage. It worked once. It was bit of game where I was the only knowing player.

What’s your Microsoft story?

4. Microsoft Exchange Server .NET Whitepaper

What are your favorite Microsoft stories? Here’s another one of my favorites… (#4 in my #favoriteMicrosoftStories series)

This story starts in the Fall of 2000 – the very, very early days of .NET/.net/.Net …yes, the days when, even inside Microsoft, there wasn’t a consistent .NET messaging and positioning framework and every product group spelled .NET differently. 🙂 How many different ways can you spell a 3-letter word that doesn’t meaning anything? We used them all until…

Internally at Microsoft, we had the “.NET police force” who swooped down unexpectedly on presenters, content authors and writers to make sure that whichever way we chose to spell .NET, we had to change it!

And who was the .NET police chief? …none other than my good colleague from the “IE4 Java Jam”: Charles Fitzgerald. (For more information, read https://www.facebook.com/mwherman/posts/10153044551595932)

In the Fall of 2000, I moved into the EC3 team (Enterprise Connectivity Competency Center), a specialty team within MCS Canada formed as part of the acquisition of Linkage, a Toronto ISV who had an entire library of Exchange 5.5. connectors …but I digress.

The nicest thing about EC3 is that we were one of the only MCS practices that figured out how to subcontract ourselves back into the corp product groups. My first assignment was to write a .NET/.net/.Net strategy whitepaper for Thomas Rizzo when he was still on the Exchange Server team (pre SQL Server, pre SharePoint, pre Local Web Storage System). Like the Internet Wave, the .NET wave meant every product group needed to craft some sort of .NET developer story (aka strategy). My task was not only to document the Exchange Server .NET strategy in a whitepaper but I also had to make it up! 🙂 “Those were the days my friend…”

I started by interviewing a lot of cool folks inside and outside the Exchange Server team: Gordon Mangione, Alex Hopmann, Brent Ingraham, Harry Katz, Keith McCall, Chris Vanden Berg, Thomas Rizzo, Lyle Curry, Jeff Wierer, and Kevin Hunter.

From there, I crafted a fairly compelling story (I mean strategy, sorry!). The whitepaper ended up being 15-20 pages.

I can’t find an original version of the “Developing Microsoft .NET Collaboration Solutions” whitepaper but you can still find the German version on the Microsoft web site: https://msdn.microsoft.com/de-de/library/cc405536.aspx . Google will do a pretty good job helping you translate from German to English.

And what about the .NET police force? Back then, there was no one who knew how to push content faster to the Microsoft.com web site than Tom Rizzo. He litrerally had the Exchange Server .NET whitepaper published overnight. When the .NET police came to our doors, we just smilled. We had already moved on to something else. 🙂

What’s your Microsoft story?

Related: https://learn.microsoft.com/de-de/previous-versions/technical-content/cc405536(v=msdn.10)

Members of the cast: Charles Fitzgerald, Gordon Mangione, Alex Hopmann, Brent Ingraham, Harry Katz, Keith McCall, Chris Vanden Berg, Thomas Rizzo, Lyle Curry, Jeff Wierer, and Kevin Hunter.

5. Windows SDK version 0.989

What are your favorite Microsoft stories? Here’s another one of my favorites… (#5 in my #FavoriteMicrosoftStories series)

The one isn’t really very juicy …more of an early milestone. Thank you goes to Bill Vaughn for helping with some of the names and dates.

It was the Spring of 1986. I worked for a Toronto research company/ISV (Optical Recording Corporation) where we were trying to use the very early versions of Windows to create (don’t laugh) an optical disc-based document storage and management system. …and I mean, very, very early versions of Windows: Windows SDK version 0.989, Windows 1.01, Windows 1.02, etc.

Later in the Fall of 1987 (I think), I attended my first Microsoft Windows developer event (MS used a small ‘d’ back then ;-)). It was in a simple Santa Clara hotel meeting room. 5-6 rows of chairs. Less than 100 people. SteveB was the MC and John Butler was the main technical guy as I remember. I remember John for his ponytail. He later went on to play a key role in creating Microsoft University (who remembers that?).

As a giveaway, we received a white cotton book bag with the pale blue Windows logo on it. It had a copy of the Windows “runtime environment” and the SDK in it. Maybe be a copy of the Microsoft C compiler. The entire library of Microsoft “small d” developer documentation was at most 3 small beige PC binders.

What’s your Microsoft story?

6. Orthogonal Defect Classification at Microsoft

What are your favorite Microsoft stories? Here’s another one of my favorites… (#6 in my #FavoriteMicrosoftStories series)

In the Fall of1997, I was honored to present to Billg, Nathan Myhrvold, and about 30 development managers at the Billg Fall 1997 Retreat: Improving the Software Development Processes at Microsoft. My topic was…

Related: https://hyperonomy.com/2021/03/20/orthogonal-defect-classification-odc4msft/

Leave a comment

Filed under Uncategorized

Brief History of Microsoft’s Disconnected Technology Strategies – circa 2005

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

Office conference wrapup
https://jonudell.net/udell/2005-02-04-office-conference-wrapup.html

Herman: It’s nice to see Microsoft consolidating around a smaller set of core technologies, but when it comes to electronic forms, Word and Excel have their own point solutions, Outlook has its own point solution, InfoPath has its own point solution, Access has its own point solution. In the developer platform you have ASP.NET and WebForms. We’re constantly in the situation where we’re trying to guess which ones are strategic. Can you give us some insight?

Why does Microsoft have so many eforms technologies? …which ones are strategic? Billg and StevenSi offer some answers
https://web.archive.org/web/20051216034728/http://dotnetjunkies.com:80/WebLog/mwherman2000/archive/2005/02/14/54401.aspx

AUDIENCE QUESTION: Michael Herman, from Parallelspace Corporation. It’s nice to see Microsoft consolidating around a smaller set of core technologies. But, when it comes to electronic forms, Word and Excel have their own point solution. Outlook has its own point solution. InfoPath has its own point solution. Access has its own point solution. In the developer platform, you have ASP.NET and WinForms. We’re constantly in a situation we’re trying to guess which ones are strategic. Can you give us some insight?

Microsoft’s varied collaboraboration platform strategies: More comments from Billg and StevenSi
https://web.archive.org/web/20060903014934/http://www.dotnetjunkies.com:80/WebLog/mwherman2000/archive/2005/02/14/54405.aspx

A question from Mark Moore (formerly of KPMG and an early SPS 2001 adopter)…

AUDIENCE QUESTION: A number of us have been on the collaboration path with Microsoft for a long time starting with Outlook and Exchange. A couple of us probably remember a team productivity update. Then SharePoint 2001, SharePoint 2003, Digital Dashboard was in there. In going from point- milestone to milestone on this path, there hasn’t been a lot to leverage moving from one point to the other. Today, in the Whidbey talk I was gratified to hear that the Whidbey Web Parts were going to be backward compatible. I’m hoping that you can assure us that those of us who have been on the path with you for a while, that this cycle of creative destruction is coming to an end.

PDC 05: Are the PDC silos going to present a disconnected view of the Microsoft developer platform?
https://web.archive.org/web/20060211002512/http://dotnetjunkies.com:80/WebLog/mwherman2000/archive/2005/07/14/131275.aspx

For example, in the description for sesssion “Choosing the Right Presentation Technology: Avalon, Windows Forms, ASP.NET, IE, and More”, there is no mention of InfoPath “12” and the forms server demonstrated at TechEd 2005.

I would encourage everyone attending this session to rate it a 1 of 5 if the new InfoPath forms and forms server is not included in the analysis.

Is Microsoft going to present an integrated view of the Microsoft platform or a disconnected one?

Is the PDC going to be one large Microsoft “technology fair” with no strategic intent other than giving each product group a venue to promote their own technology bits? …leaving developers to guess what is strategic and what is not. (50% probability)

Pre-blogging the PDC
https://jonudell.net/udell/2005-08-02-pre-blogging-the-pdc.html

As Microsoft gears up for its annual Professional Developers Conference, Michael Herman — CTO and founder of Parallelspace — is asking some probing questions about the agenda:

Is the PDC going to be one large Microsoft “technology fair” with no strategic intent other than giving each product group a venue to promote their own technology bits? …leaving developers to guess what is strategic and what is not. (50% probability) [Michael Herman: Are the PDC silos going to present a disconnected view of the Microsoft platform?]


Michael asked similar questions at the Office Developers Conference I attended in February. I transcribed one of them — about Microsoft’s hydra-headed electronic forms strategy — in this blog item. Michael blogged the same exchange, and he also zeroed in on another set of questions and answers about unified storage that I transcribed from the February conference.
These questions are interesting, but I find the process itself even more so. The PDC tends to be ahistorical, focusing on futures more than follow-through. In the hallways you see attendees reading the entrails and trying to divine which futures will be strategic, at a level more granular than the grand themes: Windows, NT, Win95, the Internet, tablet PC, .NET, Hailstorm, WinFX.

Leave a comment

Filed under Uncategorized