From 0a2c75dbcda933d6e15e135fa3869108356803ad Mon Sep 17 00:00:00 2001 From: Rieks Date: Fri, 8 Dec 2023 06:05:22 +0100 Subject: [PATCH] updates in pattern statuses Signed-off-by: Rieks --- docs/glossaries/mrg.essiflab.all-patterns.yaml | 11 ++++++----- docs/glossaries/mrg.essiflab.ctext.yaml | 7 ++++--- docs/glossaries/mrg.essiflab.default.yaml | 7 ++++--- docs/glossaries/mrg.essiflab.documentation.yaml | 7 ++++--- docs/glossaries/mrg.essiflab.latest.yaml | 7 ++++--- docs/glossaries/mrg.essiflab.stable-patterns.yaml | 1 - docs/glossaries/mrg.essiflab.terms.yaml | 7 ++++--- docs/glossaries/mrg.essiflab.yaml | 7 ++++--- docs/terms/pattern-decentralized-GRC.md | 6 +++--- docs/terms/pattern-decentralized-risk-management.md | 4 ++++ docs/terms/pattern-decision-making.md | 7 ++++--- docs/terms/pattern-duties-and-rights.md | 9 +++++---- docs/terms/pattern-governance-and-management.md | 6 +++++- docs/terms/pattern-guardianship.md | 4 ++-- docs/terms/pattern-identification.md | 6 +++--- docs/terms/pattern-identifier.md | 6 +++--- docs/terms/pattern-identity.md | 6 +++++- docs/terms/pattern-jurisdiction.md | 4 ++-- docs/terms/pattern-mandates-delegation-hiring.md | 8 ++++---- docs/terms/pattern-party-actor-action.md | 4 +--- docs/terms/pattern-party-representation.md | 7 ++++--- docs/terms/pattern-semantics.md | 8 ++++++-- docs/terms/pattern-terminology.md | 6 +++++- docs/terms/pattern-trust.md | 8 ++++---- 24 files changed, 90 insertions(+), 63 deletions(-) diff --git a/docs/glossaries/mrg.essiflab.all-patterns.yaml b/docs/glossaries/mrg.essiflab.all-patterns.yaml index 8b26b92ad..d5ce953d5 100644 --- a/docs/glossaries/mrg.essiflab.all-patterns.yaml +++ b/docs/glossaries/mrg.essiflab.all-patterns.yaml @@ -44,6 +44,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -84,7 +86,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -244,7 +246,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -294,7 +296,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' @@ -330,7 +331,7 @@ entries: termType: 'pattern' term: 'semantics' formPhrases: null - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Semantics Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the relations between the (intangible) [concepts](@) (and other [semantic units](@)) that are part of a [party''s](@) [knowledge](@), and how they are (tangibly) represented by [terms](@), [attributes](@), etc.' @@ -375,7 +376,7 @@ entries: termType: 'pattern' term: 'trust' formPhrases: 'trust' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Trust Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain how the concept of [trust](@) relates to [parties](@) that do the trusting, and other concepts that express what it is that these [parties](@) trust.' diff --git a/docs/glossaries/mrg.essiflab.ctext.yaml b/docs/glossaries/mrg.essiflab.ctext.yaml index c2f354e45..efd7a9d4f 100644 --- a/docs/glossaries/mrg.essiflab.ctext.yaml +++ b/docs/glossaries/mrg.essiflab.ctext.yaml @@ -720,6 +720,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -910,7 +912,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -1659,7 +1661,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -1986,7 +1988,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/glossaries/mrg.essiflab.default.yaml b/docs/glossaries/mrg.essiflab.default.yaml index 5e1927c57..8709edceb 100644 --- a/docs/glossaries/mrg.essiflab.default.yaml +++ b/docs/glossaries/mrg.essiflab.default.yaml @@ -724,6 +724,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -914,7 +916,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -1663,7 +1665,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -1990,7 +1992,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/glossaries/mrg.essiflab.documentation.yaml b/docs/glossaries/mrg.essiflab.documentation.yaml index 5e1927c57..8709edceb 100644 --- a/docs/glossaries/mrg.essiflab.documentation.yaml +++ b/docs/glossaries/mrg.essiflab.documentation.yaml @@ -724,6 +724,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -914,7 +916,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -1663,7 +1665,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -1990,7 +1992,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/glossaries/mrg.essiflab.latest.yaml b/docs/glossaries/mrg.essiflab.latest.yaml index 5e1927c57..8709edceb 100644 --- a/docs/glossaries/mrg.essiflab.latest.yaml +++ b/docs/glossaries/mrg.essiflab.latest.yaml @@ -724,6 +724,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -914,7 +916,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -1663,7 +1665,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -1990,7 +1992,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/glossaries/mrg.essiflab.stable-patterns.yaml b/docs/glossaries/mrg.essiflab.stable-patterns.yaml index 5b36615c2..5a70e67c5 100644 --- a/docs/glossaries/mrg.essiflab.stable-patterns.yaml +++ b/docs/glossaries/mrg.essiflab.stable-patterns.yaml @@ -67,7 +67,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/glossaries/mrg.essiflab.terms.yaml b/docs/glossaries/mrg.essiflab.terms.yaml index 5e1927c57..8709edceb 100644 --- a/docs/glossaries/mrg.essiflab.terms.yaml +++ b/docs/glossaries/mrg.essiflab.terms.yaml @@ -724,6 +724,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -914,7 +916,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -1663,7 +1665,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -1990,7 +1992,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/glossaries/mrg.essiflab.yaml b/docs/glossaries/mrg.essiflab.yaml index 5e1927c57..8709edceb 100644 --- a/docs/glossaries/mrg.essiflab.yaml +++ b/docs/glossaries/mrg.essiflab.yaml @@ -724,6 +724,8 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-decentralized-risk-management' headingids: - 'decentralized-(networked)-risk-management-(nrm)' + - 'introduction' + - 'purpose' - 'traditional-risk-management-and-nrm' - 'scope,-context,-criteria' - 'risk-assessment' @@ -914,7 +916,7 @@ entries: termType: 'pattern' term: 'duties-and-rights' formPhrases: 'duties-and-rights' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Duties and Rights Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld''s theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@).' @@ -1663,7 +1665,7 @@ entries: termType: 'pattern' term: 'mandates-delegation-hiring' formPhrases: 'mandates-delegation-hiring' - status: 'draft' + status: 'idea' grouptags: null glossaryTerm: 'Mandates, Delegation and Hiring Pattern' glossaryText: 'a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations.' @@ -1990,7 +1992,6 @@ entries: navurl: 'https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action' headingids: - 'parties,-actors-and-actions' - - 'summary' - 'purpose' - 'introduction' - 'formalized-model' diff --git a/docs/terms/pattern-decentralized-GRC.md b/docs/terms/pattern-decentralized-GRC.md index fcbc5b471..83fc85384 100644 --- a/docs/terms/pattern-decentralized-GRC.md +++ b/docs/terms/pattern-decentralized-GRC.md @@ -13,12 +13,12 @@ hoverText: "The Decentralized GRC (Governance, Risk Management, and Compliance) date: 20210601 --- -# Decentralized Risk Management, Governance and Compliance - import useBaseUrl from '@docusaurus/useBaseUrl' +# Decentralized Risk Management, Governance and Compliance + :::info Editor's note -This is work that is being envisaged, and needs a good deal of work. +This is work that is in its early drafting stage. If you have suggestions, please [raise an issue](https://github.com/essif-lab/framework/issues/new). ::: :::info Editor's note diff --git a/docs/terms/pattern-decentralized-risk-management.md b/docs/terms/pattern-decentralized-risk-management.md index f11caeb48..ee70d34d8 100644 --- a/docs/terms/pattern-decentralized-risk-management.md +++ b/docs/terms/pattern-decentralized-risk-management.md @@ -25,12 +25,16 @@ This is work in progress. This work needs to be compared with and integrated with (or separated from) the contents of the [Decentralized GRC pattern](pattern-decentralized-grc@) ::: +## Introduction + Traditional [risk management](@) (RM) frameworks, such as [ISO 31000](https://www.iso.org/obp/ui/#iso:std:iso:31000:ed-2:v1:en), [COSO](https://www.coso.org/Pages/default.aspx), or [NIST 800-30](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-30r1.pdf) have emerged in a time where [centralized organizational leadership](authority@) and auditing, and cyclic ([PDCA](https://en.wikipedia.org/wiki/PDCA)) processes for [risk management](@), were prevalent. Most (large) enterprises have adopted (a mix of) them, and many have been certified (e.g. against [ISO 9001](https://www.iso.org/iso-9001-quality-management.html) or [ISO 27001](https://www.iso.org/isoiec-27001-information-security.html)) thereby demonstrating they [govern](governance@) and run the associated [risk management](@) processes as intended, and are [compliant](compliance@) with such standards and often also with applicable regulations. While useful, these [frameworks](normative-framework@) don't provide actual/practical guidance for all situations. For example, it is well-known that SMEs or other parties that do not have the required (expert) knowledge, time and other resources to setup and run elaborate processes for [managing](management@) [their risks](risk-owner@), are pretty much left to their own devices. Also, larger organizations that use these [frameworks](normative-framework@) need additional mechanisms to ensure that the [risk objectives](risk-objective@) set out by the board are actually realized in the 'operational cellars' of the organization.[^1] We provide another way of thinking about [risks](@). It is based on the postulate that [parties](@) are autonomous [entities](@), that pursue their [owns](@) [objectives](@), that perceive the associated [risks](@), and set [risk objectives](risk-objective@) to ensure these [risks](@) are [managed](risk-management@). While this may not seem to be all that different from what traditional RM [frameworks](normative-framework@) do at a first glance, there is a big difference between [parties](@) that realize what it means to be a [party](@) and how that limits their [scope of control](@), and parties that do not. It's about their realization where they can exercise their autonomy and where they can - at best - exercise influence. +## Purpose + Decentralized Risk Management (also called Networked Risk Management (NRM)) is a [risk-management](@) process that has been designed for [parties](@) that are aware of their autonomy and its limitations, which implies they are committed to use the parts of the [eSSIF-Lab terminology](/docs/essifLab-glossary) that are relevant here (the terms that are emphasized and come with popups in this document). They can use it to [manage](management@) their [risks](@), i.e. the [risks](@) associated with their [owns](@) [objectives](@), regardless of whether it is consciously or unconsciously aware of them (we assume that most of them are of the 'unconscious' kind). NRM is decentralized because every [party](@) runs it on its own, within its [owns](@) [scope of control](@). In an [organization](@) that is a hierarchy of sub-organizations, such as departments, it is typical that every sub-organization (e.g. the board, the finance department, the security department, divisions, etc.) manages its [owns](@) [risks](@), and none other than these. We will see that this setup is capable of producing the result that all [risks](@) in the [organization](@) are properly mitigated, and the overall residual [risks](@) are acceptable. diff --git a/docs/terms/pattern-decision-making.md b/docs/terms/pattern-decision-making.md index e2273cce9..0b2577b84 100644 --- a/docs/terms/pattern-decision-making.md +++ b/docs/terms/pattern-decision-making.md @@ -13,13 +13,14 @@ hoverText: "The Decision Making pattern captures the Concepts and relations that date: 20210804 --- -# Decision Making - import useBaseUrl from '@docusaurus/useBaseUrl' +# Decision Making + :::info Editor's note -This is work that is being envisaged. +This is work that is in its early drafting stage. If you have suggestions, please [raise an issue](https://github.com/essif-lab/framework/issues/new). ::: + ### Purpose The **Decision making pattern** captures the [concepts](@) and relations that explain how [parties](@) would, could, or should reason in order to reach good conclusions and make good decisions. This can be used as a basis for understanding the information needs of [parties](@) as they need to decide e.g. whether or not to commit to a [transaction](@) proposal, or whether or not data is [valid](validate@) for some purpose. This pattern is based on [Toulmin's use of arguments](https://www.cambridge.org/core/books/uses-of-argument/26CF801BC12004587B66778297D5567C) (of which a pragmatical text can be found [here](https://owl.purdue.edu/owl/general_writing/academic_writing/historical_perspectives_on_argumentation/toulmin_argument.html)). diff --git a/docs/terms/pattern-duties-and-rights.md b/docs/terms/pattern-duties-and-rights.md index f35d6f9af..639b0e0ad 100644 --- a/docs/terms/pattern-duties-and-rights.md +++ b/docs/terms/pattern-duties-and-rights.md @@ -5,7 +5,7 @@ scopetag: essifLab termType: pattern term: duties-and-rights formPhrases: duties-and-rights -status: draft +status: idea grouptags: glossaryTerm: Duties and Rights Pattern glossaryText: "a set of [concepts](@) and other [semantic units](@) that can be used to explain what a generic duties and rights consists of (based on [Hofeld's theories](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst)), and relates it to [jurisdictions](@), [parties](@) and [legal entities](@)." @@ -13,13 +13,14 @@ hoverText: "The Duties and Rights pattern captures the Concepts and relations th date: 20210601 --- -# Duties and Rights - import useBaseUrl from '@docusaurus/useBaseUrl' +# Duties and Rights + :::info Editor's note -This is work that is being envisaged. +This is work that is still an idea. If you want to help, do so by telling us [in a new issue](https://github.com/essif-lab/framework/issues/new). ::: + ### Purpose The **Duties-and-rights pattern** captures the concepts and relations that explain what (generic) duties and rights are, thereby following the [theory of Hohfeld](https://plato.stanford.edu/entries/rights/#FormRighHohfAnalSyst), which is not only the basis of [legal systems](legal-system@) (in [jurisdictions](@)), but can be used to generically model duties and rights. diff --git a/docs/terms/pattern-governance-and-management.md b/docs/terms/pattern-governance-and-management.md index ea5409705..9d5fbaac6 100644 --- a/docs/terms/pattern-governance-and-management.md +++ b/docs/terms/pattern-governance-and-management.md @@ -13,9 +13,13 @@ hoverText: "The Governance and Management pattern explains how Parties organize date: 20210830 --- +import useBaseUrl from '@docusaurus/useBaseUrl' + # Governance and Management -import useBaseUrl from '@docusaurus/useBaseUrl' +:::info Editor's note +This is work in progress, and needs to be reviewed. If you want to comment, please [raise an issue](https://github.com/essif-lab/framework/issues/new). +::: ### Purpose diff --git a/docs/terms/pattern-guardianship.md b/docs/terms/pattern-guardianship.md index d9b107404..5353e97aa 100644 --- a/docs/terms/pattern-guardianship.md +++ b/docs/terms/pattern-guardianship.md @@ -13,10 +13,10 @@ hoverText: "The Guardianships pattern captures the Concepts and relations that e date: 20210601 --- -# Guardianship - import useBaseUrl from '@docusaurus/useBaseUrl' +# Guardianship + ### Purpose The **Guardianship pattern** captures the concepts and relations that explain how generic guardianships work, and can be constructed. It shows that [guardianship arrangements](guardianship-arrangement@) are embedded in a [jurisdiction](@) that govern such arrangements. diff --git a/docs/terms/pattern-identification.md b/docs/terms/pattern-identification.md index b0aefe316..b23789fca 100644 --- a/docs/terms/pattern-identification.md +++ b/docs/terms/pattern-identification.md @@ -13,12 +13,12 @@ hoverText: "The eSSIF-Lab Identification Pattern describes mechanisms that a Par date: 20210803 --- -# Identification Pattern - import useBaseUrl from '@docusaurus/useBaseUrl' +# Identification Pattern + :::info Editor's note -This is work in progress and needs discussion. +This is work in progress, and needs to be reviewed. If you want to comment, please [raise an issue](https://github.com/essif-lab/framework/issues/new). ::: ### Purpose diff --git a/docs/terms/pattern-identifier.md b/docs/terms/pattern-identifier.md index c99fcd9a2..92cff3596 100644 --- a/docs/terms/pattern-identifier.md +++ b/docs/terms/pattern-identifier.md @@ -13,12 +13,12 @@ hoverText: "The eSSIF-Lab Identifier Pattern describes how Identifiers are defin date: 20210830 --- -# Identifier Pattern - import useBaseUrl from '@docusaurus/useBaseUrl' +# Identifier Pattern + :::info Editor's note -This is work in progress and needs discussion. +This is work in progress, and needs to be reviewed. If you want to comment, please [raise an issue](https://github.com/essif-lab/framework/issues/new). ::: ### Purpose diff --git a/docs/terms/pattern-identity.md b/docs/terms/pattern-identity.md index 7d48138c8..ae188e6b8 100644 --- a/docs/terms/pattern-identity.md +++ b/docs/terms/pattern-identity.md @@ -13,9 +13,13 @@ hoverText: "The eSSIF-Lab Identity Pattern shows how digital identities work, ho date: 20210803 --- +import useBaseUrl from '@docusaurus/useBaseUrl' + # Identity Pattern -import useBaseUrl from '@docusaurus/useBaseUrl' +:::info Editor's note +This is work in progress, and needs to be reviewed. If you want to comment, please [raise an issue](https://github.com/essif-lab/framework/issues/new). +::: ### Purpose diff --git a/docs/terms/pattern-jurisdiction.md b/docs/terms/pattern-jurisdiction.md index e837c083f..950815cee 100644 --- a/docs/terms/pattern-jurisdiction.md +++ b/docs/terms/pattern-jurisdiction.md @@ -13,10 +13,10 @@ hoverText: "The Jurisdictions pattern captures the Concepts and relations that e date: 20210601 --- -# Jurisdictions - import useBaseUrl from '@docusaurus/useBaseUrl' +# Jurisdictions + ### Purpose The **Jurisdiction pattern** captures the concepts and relations that explain how one can perceive a generic [jurisdiction](@), how it works, and how it can be put to use in [SSI contexts](self-sovereign-identity@). diff --git a/docs/terms/pattern-mandates-delegation-hiring.md b/docs/terms/pattern-mandates-delegation-hiring.md index 88310d17c..dda94357d 100644 --- a/docs/terms/pattern-mandates-delegation-hiring.md +++ b/docs/terms/pattern-mandates-delegation-hiring.md @@ -5,7 +5,7 @@ scopetag: essifLab termType: pattern term: mandates-delegation-hiring formPhrases: mandates-delegation-hiring -status: draft +status: idea grouptags: glossaryTerm: Mandates, Delegation and Hiring Pattern glossaryText: "a set of [concepts](@) and other [semantic units](@) that can be used to explain the ideas behind Mandating, Delegating, Hiring and their relations." @@ -13,12 +13,12 @@ hoverText: "The Mandates, Delegation and Hiring pattern (which remains to be doc date: 20210601 --- -# Mandates, Delegation and Hiring - import useBaseUrl from '@docusaurus/useBaseUrl' +# Mandates, Delegation and Hiring + :::info Editor's note -This is work that is being envisaged. +This is work that is still an idea. If you want to help, do so by telling us [in a new issue](https://github.com/essif-lab/framework/issues/new). ::: The idea here is to observe that: diff --git a/docs/terms/pattern-party-actor-action.md b/docs/terms/pattern-party-actor-action.md index 340fe1dbc..e6d37ebfc 100644 --- a/docs/terms/pattern-party-actor-action.md +++ b/docs/terms/pattern-party-actor-action.md @@ -13,11 +13,9 @@ hoverText: "The Parties, Actors and Actions pattern captures the foundational co date: 20210602 --- -# Parties, Actors and Actions - import useBaseUrl from '@docusaurus/useBaseUrl' -## Summary +# Parties, Actors and Actions This pattern captures the essence of how things are done. It answers questions such as: "Who/what does things?", "How are their [actions](@) being guided/[controlled](controller@)?", "Who [controls](controller@) whom/what?", "Who/what may be held accountable?". These questions need to have a precise answer if you want to design or implement systems where [actors](@) can be anything, ranging from programs/apps running on computers as well as [humans](human-being@). This pattern provides a way of looking at [organizations](@), [people](human-being@), and non-human [actors](@). It shows how they interact with one another, and how they may or may not work for one another. The pattern describes how [parties](@) are '[(self) sovereign](self-sovereignty@)' as they construct their own world view, reason with that, and make their (subjective) decisions autonomously. It also shows how this [knowledge](@) is used, where it is used, and also: where it is not used. The latter implies that [parties](@) have a limited [scope of control](@), which gives rise to their need to work together with other [parties](@), that have their own sovereignty. Such interactions with others, however, are outside the scope of this pattern. diff --git a/docs/terms/pattern-party-representation.md b/docs/terms/pattern-party-representation.md index a9ddba95e..af1c8e54a 100644 --- a/docs/terms/pattern-party-representation.md +++ b/docs/terms/pattern-party-representation.md @@ -13,12 +13,12 @@ hoverText: "The Party Representation pattern captures the foundational concepts date: 20210601 --- -# Party Representation - import useBaseUrl from '@docusaurus/useBaseUrl' +# Party Representation + :::info Editor's note -This pattern is still under development +This is work that is in its early drafting stage. If you have suggestions, please [raise an issue](https://github.com/essif-lab/framework/issues/new). ::: ### Summary @@ -30,6 +30,7 @@ This pattern captures the essence of how [parties](@) can be represented in vari Within the context of [SSI](self-sovereign-identity@), we are interested in coming to grips with (answering) questions such as 'in what ways can [parties](@) be represented?', 'what kind(s) of [entities](@) can represent [parties](@)', 'how can we deal with representation constraints, i.e. provide guarantees that the represented [party](@) isn't completely at the mercy of the one representing it?'. This model attempts to provide answers to such questions. + ### Introduction There are very many different forms of representation. [Claims](assertion@), for example, represent characteristics attributed to [entities](@), [Terms](@) represent (intangible) [concepts](@), [legal entities](legal-entity@) are represented in the [knowledge](@) of a [jurisdiction](@), [agents](@) represent [parties](@) as they execute [actions](@), and so on. We specifically focus on diff --git a/docs/terms/pattern-semantics.md b/docs/terms/pattern-semantics.md index 91af198cf..0e7f10a16 100644 --- a/docs/terms/pattern-semantics.md +++ b/docs/terms/pattern-semantics.md @@ -5,7 +5,7 @@ scopetag: essifLab termType: pattern term: semantics formPhrases: -status: draft +status: idea grouptags: glossaryTerm: Semantics Pattern glossaryText: "a set of [concepts](@) and other [semantic units](@) that can be used to explain the relations between the (intangible) [concepts](@) (and other [semantic units](@)) that are part of a [party's](@) [knowledge](@), and how they are (tangibly) represented by [terms](@), [attributes](@), etc." @@ -13,9 +13,13 @@ hoverText: "The Semantics pattern describes the relations between the (intangibl date: 202120607 --- +import useBaseUrl from '@docusaurus/useBaseUrl' + # Semantics Pattern -import useBaseUrl from '@docusaurus/useBaseUrl' +:::info Editor's note +This is work that is still an idea. If you want to help, do so by telling us [in a new issue](https://github.com/essif-lab/framework/issues/new). +::: ### Purpose diff --git a/docs/terms/pattern-terminology.md b/docs/terms/pattern-terminology.md index d7aaf5882..ccea9139d 100644 --- a/docs/terms/pattern-terminology.md +++ b/docs/terms/pattern-terminology.md @@ -13,9 +13,13 @@ hoverText: "a set of Concepts and other Semantic units that one can use to expla date: 20211101 --- +import useBaseUrl from '@docusaurus/useBaseUrl' + # Terminology Pattern -import useBaseUrl from '@docusaurus/useBaseUrl' +:::info Editor's note +This is work in progress, and needs to be reviewed. If you want to comment, please [raise an issue](https://github.com/essif-lab/framework/issues/new). +::: This pattern describes how [terms](@) are [scoped](scope@) (which software engineers call 'namespaces'), how parties govern such scopes/namespaces, and that if you use criteria to define/specify terms, people can test if they have the same understanding of a term by making sure that everyone reaches the same conclusions as they evaluate such criteria in various relevant use-cases. diff --git a/docs/terms/pattern-trust.md b/docs/terms/pattern-trust.md index 2074accab..b79593621 100644 --- a/docs/terms/pattern-trust.md +++ b/docs/terms/pattern-trust.md @@ -5,7 +5,7 @@ scopetag: essifLab termType: pattern term: trust formPhrases: trust -status: draft +status: idea grouptags: glossaryTerm: Trust Pattern glossaryText: "a set of [concepts](@) and other [semantic units](@) that can be used to explain how the concept of [trust](@) relates to [parties](@) that do the trusting, and other concepts that express what it is that these [parties](@) trust." @@ -13,12 +13,12 @@ hoverText: "The eSSIF-Lab Trust Pattern describes how the concept of Trust relat date: 20210830 --- -# Trust Pattern - import useBaseUrl from '@docusaurus/useBaseUrl' +# Trust Pattern + :::info Editor's note -This is work in progress and needs discussion. +This is work that is still an idea. If you want to help, do so by telling us [in a new issue](https://github.com/essif-lab/framework/issues/new). ::: ### Purpose