For a complete list of the 20+ technology adoption models, checkout: Technology Adoption Models: A Comprehensive Guide.
Category Archives: Uncategorized
Click here to download this Parallelspace Corporation Technical Note: PSN TN0028: SPS2003 XML Import-Export “Operation” Attribute
The technical note proposes the addition of an operation attribute to the XML emitted for each exported item by the SPS2003 Upgrade.exe tool. The schema for the operation attribute would include the following operations:
|operation Attribute Values||Description||Pre-delete Existing Item||Create New Item|
|operation=”delete”||Delete deletes an existing item imported into SPS2003 during a previous execution of the Import tool; or fails if the item doesn’t exist.||No||No|
|operation=”remove”||Delete deletes an existing item imported into SPS2003 during a previous execution of the Import tool, if it exists.||No||No|
|operation=”create”||Create creates a new instance of the exported item; or fails if the item already exists (see replace, update and add)||No||Yes|
|operation=”replace”||Replace replaces an existing item imported intoSPS2003 during a previous execution of the Import tool by executing a Delete followed by a Create; or fails if the item doesn’t exit.||Yes||Yes|
|operation=”add”||Add a) creates a new instance of the exported item if the item does *not* exist; or b) replaces an item if the item was imported into SPS2003 during a previous execution of the Import tool. This operation shouldn’t fail based on previous import operations||a) No b) Yes||a) Yes b) Yes|
|operation=”merge”||Add a) creates a new instance of the exported item if the item does *not* exist; or b) updates an item if the item was imported into SPS2003 during a previous execution of the Import tool. This operation shouldn’t fail based on previous import operations||a) No b) No||a) Yes b) No|
|operation=”update”||Update adds or replaces the values of selected attributes of an existing item imported intoSPS2003 during a previous execution of the Import tool; or fails if the item doesn’t exit.||No||No|
|operations=”ignore”||Processing for this item is skipped. The contents of the item are ignored.||n/a||n/a|
Secure Data Storage Working Group (sds-wg) Confidential Storage (CS): Functional Architecture Reference Models (CS-FARMs) 0.36 (whitepaper placeholder): Sample Diagrams
Almost 2 years ago when I developed and documented the Social Evolution models for Technology Adoption, I never dreamed that I would be writing an article with the above title.
Paraphrasing, the Social Evolution model states:
A #wanderer is someone who leaves their tribe to share their knowledge and wisdom with others; to later form a party of explorers to explore and conquer a common set of goals; and, even further on, create a clan, a band, a tribe, and a tribal society, a group of people who live and work together – a group of tribes organized around kinships.
The Social Evolution model was first documented (illustrated) here: Social Evolution and Technology Adoption. Later, the model was added to the list of what became 2of the 20+ models in the article: Technology Adoption Models: A Comprehensive Guide as:
- Model 2a: Social Evolution: Creation of Nation State, and
- Model 2b. Social Evolution: Defining Principles.
Model 2a appears below followed by Model 2b.
What I didn’t realize is that I was also defining a framework for a new political spectrum:
- True decentralization/self-sovereignty on the left
- Complete authoritarian centralization on the right
…and hence, a new Social Evolution model.
Is the Social Evolution model harmful? No, not at all …as long as it remains helpful in illuminating new concepts like the Self-Sovereignty Political Spectrum.
What is your self-sovereignty political affiliation?
- A decentralized/self-sovereign sheep (that needs to be protected by default), or
- An authoritarian centralizationist wolf (ready to devour your sheep mates)?
…or are you a centrist?
Have a great day.
“The mind once enlightened, cannot be darkened” – Thomas Paine
What is Self-Sovereign Identity (SSI)?
Self-Sovereign Identity, as a standalone phrase (or acronym), is a very confusing, overloaded, ambiguous term whose use should be avoided in all situations. In conversation, an article, or a standards document, it could mean any of the uncontracted terms in the following figure. The term Self-Sovereign Identity (or its acronym SSI) could refer to any or all of the uncontracted terms in the following figure – unless an author has taken care to be clear and precise with respect to every occurrence of the term and/or its acronym.
 The most recent example of SSI confusion is the Principles of SSI document published by the Sovrin Foundation (https://sovrin.org/principles-of-ssi/). The document makes no attempt to define SSI nor state what SSI is intended to be an acronym for. Princples of SSI has resulted in a lot of confudsion (https://hyperonomy.com/2018/12/18/definition-confuding/) in the decentralized identifer communities as different working groups try to apply the Principles in new domains without for descerning: a) precisely which definition/application of SSI should be used and b) the types or categories of principles being represented in the document. Without first having a clear and precise definition for (a), successfully achieving (b) is almost impossible.
Self-Sovereign Identity Personal Data Usage Licensing (SSI-PDUL) Model: Whitepaper [Review Draft 0.27]
Click here (to download the whitepaper):
- Version 0.27 – original preview draft version
Ahead of schedule, the first trusted web page was delivered today on the Trusted Digital Web – end-to-end – from a Trusted Digital Web – Data Registry service to a Trusted Digital Assistant client application – using didttp: (DID Trusted Transport Protocol).
The Trusted Digital Web Communication Protocols (include ddttp:) are described in Appendix E of the Trusted Digital Web: Whitepaper.
NOTE: The Trusted Digital Web is built on top of and relies on trusted, everyday Internet protocols, services, and specifications such as DNS (Domain Name Service). If you’re unfamiliar with DNS at a technical level, checkout DNS (Domain Name Service): A Detailed, High-level Overview.
Here’s some screenshots to document this significant event.
Trusted Digital Web – Data Registry Service
Create the did:foo DID method
Browse method did:foo
Create the did:foo:Home signed credential
Add a DIDTXT claim to the did:foo:Home signed credential
The DIDTXT claim will hold the contents of the index.html web page.
Trusted Digital Assistant Client Application
Start the Trusted Digital Assistant
Navigate to a conventional web page (e.g. http://www.hyperonomy.com).
Navigate to another web page using didttp: (DID Trusted Transport Protocol)
Click here: The Message is the Medium: Multiprocess Structuring of an Interactive Paint Program – Beach et. all
Daniel, regarding our discussion about the multi-process structuring of the Indy Ledger Node and how Anthropomorphic Design might be able to help, checkout the attached conference paper that describes a Paint application created by Eugene Fiume, a cohort of mine while we were in grad school together at the University of Waterloo. [Eugene is now Dean of Applied Sciences at Simon Fraser University.]
It’s an easy read …focus on page 279 and onwards: the concepts of Administrator, Overseer, Worker, Secretary, and Listener processes.
NOTE: The paper starts on page 277 of the proceedings. The paper is a total of 11 pages.
Credentials Community Group 2018 End of Year Survey Results (March 2019)
Click here to download a full copy of the Credentials Community Group 2018 End of Year Survey Results (March 2019) report.
The Report’s Key Findings
10 Real-Life Examples
- “…it’s not like we’re considering any of those topics for the first time.”
- “We may want to limit discussion if people that are new to the work, such as yourself, insist on rehashing things that we’ve already discussed.”
- “I know it will take time for you to trust that we’re trying to do the right thing for the community, Web, and Internet in general.”
- “Unfortunately, trust of that level takes months to years to develop and regular interaction and demonstrating over time that we have the best interests of the community at heart is all we can do to make you believe that we’re trying to do the right thing here.”
- “There are things that have strong consensus, such as dereferencing a DID gives you a DID Document.”
- “It’s incredibly difficult to navigate all of that if you haven’t been a part of the community since it’s beginning…”
- “There are discussions that keep coming up repeatedly that many in the community have explored multiple times and so rehashing those discussions is not useful if there is consensus on the topic.”
- “We’ve been having these topical discussions for a few years now and we’re probably through most of them.”
- “We need to be careful to not retread territory that we’ve already covered.”
- “You are also potentially re-opening discussions that we have consensus on, so we need to be careful not to do that because if we do that, lots of decisions that were finalized end up being reopened and we’ll waste a tremendous amount of time coming back to the same conclusion we came to many months/years ago.”