Commit 9a190a42 authored by Rieks Joosten's avatar Rieks Joosten Committed by fmerg

integrated new work that i did in the meantime

parent 54509263
......@@ -4,6 +4,7 @@ title: "Action"
scopeid: essifLab
type: concept
typeid: action
stage: draft
hoverText: "something that is done by an actor"
---
......
......@@ -4,6 +4,7 @@ title: "Actor"
scopeid: essifLab
type: concept
typeid: actor
stage: draft
hoverText: "Entity that can act (do things), e.g. people, machines, but not organizations."
---
......
......@@ -4,6 +4,7 @@ title: "Agent"
scopeid: essifLab
type: concept
typeid: agent
stage: draft
hoverText: "Agent (of a Party): Actor that is currently working on behalf of a Party."
---
......
......@@ -4,6 +4,7 @@ title: "eSSIF-Glue"
scopeid: essifLab
type: concept
typeid: eSSIFGlue
stage: draft
hoverText: "eSSIFGlue"
---
......
......@@ -4,6 +4,7 @@ title: "Entity"
scopeid: essifLab
type: concept
typeid: entity
stage: draft
hoverText: "something that is done by an actor"
---
......
......@@ -4,6 +4,7 @@ title: "Pattern-file"
scopeid: essifLab
type: concept
typeid: pattern-file
stage: draft
hoverText: "pattern-file popover"
---
......
......@@ -4,6 +4,7 @@ title: "Concept"
scopeid: essifLabTerminology
type: concept
typeid: concept
stage: draft
hoverText: "A Concept tries to capture the idea behind a classification of entities, allowing us to reason about everything in the class as if it were one thing."
---
......
......@@ -4,6 +4,7 @@ title: "Dictionary"
scopeid: essifLabTerminology
type: concept
typeid: dictionary
stage: draft
hoverText: "an alphabetically sorted list of terms and explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
---
......
......@@ -4,6 +4,7 @@ title: "Entity"
scopeid: essifLab
type: concept
typeid: entity
stage: draft
hoverText: "something that is done by an actor"
---
......
......@@ -4,6 +4,7 @@ title: Glossary of eSSIF-Lab Terminology
scopeid: essifLabTerminology
type: glossary
typeid: essifLabTerminology
stage: draft
hoverText: "essifLabTerminology-glossary - popuptext tbd"
---
......
......@@ -4,6 +4,7 @@ title: "Glossary (Concept)"
scopeid: essifLabTerminology
type: concept
typeid: glossary
stage: draft
hoverText: "an alphabetically sorted list of terms explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
---
......
---
id: concept-file
title: "Concept-file"
id: pattern-file
title: "Pattern-file"
scopeid: essifLab
type: concept
typeid: concept-file
hoverText: "concept-file popover"
type: pattern
typeid: pattern-file
stage: draft
hoverText: "a file that defines/specifies a pattern"
---
## Short Description
A **pattern-file** is a file that describes a %%pattern|pattern%%. To faciliate authors, a self-explanatory [template file](terminology/templates/pattern-file.md) is available.
## Purpose
Describing %%patterns|pattern%% enable users/readers to get a good idea of how related %%concepts|concept%% work together as a coherent and consistent whole. Mature patterns are generally simple, and make it much easier to think about the described concepts for someone that applies the pattern than it is for people that do not.
## Criterion:
## Examples:
a file that defines/specifies a %%pattern|pattern%.
......@@ -4,6 +4,7 @@ title: "Pattern: Mental Models"
scopeid: essifLabTerminology
type: pattern
typeid: mental-model
stage: draft
hoverText: "This pattern captures the foundational concepts and relations that we need for creating, maintaining and using (decentralized) vocabularies (terminologies) that groups of people can use for the specific purposes they pursue."
---
......
......@@ -4,6 +4,7 @@ title: "Pattern"
scopeid: essifLab
type: concept
typeid: pattern
stage: draft
hoverText: "pattern popover text"
---
......
......@@ -4,6 +4,7 @@ title: "Scope-file"
scopeid: essifLab
type: concept
typeid: scope-file
stage: draft
hoverText: "scope-file popover"
---
......
......@@ -4,6 +4,7 @@ title: "Scope: eSSIF-Lab Terminology"
scopeid: essifLabTerminology
type: scope
typeid: essifLabTerminology
stage: draft
hoverText: "scope essifLabTerminology - popuptext tbd"
---
......
......@@ -2,6 +2,7 @@
id: scope
title: "Scope: essifLabTerminology"
scopeid: essifLabTerminology
stage: draft
hoverText: "essifLabTerminology - popuptext t.b.d"
---
......
......@@ -4,6 +4,7 @@ title: "Concept: Concept (Scope: essifLabTerminology)"
scopeid: essifLabTerminology
type: concept
typeid: semantics
stage: draft
hoverText: "semantics popover"
---
......
......@@ -4,6 +4,7 @@ title: "Term-file"
scopeid: essifLab
type: concept
typeid: term-file
stage: draft
hoverText: "term-file popover"
---
......
......@@ -4,6 +4,7 @@ title: "Term"
scopeid: essifLabTerminology
type: concept
typeid: term
stage: draft
hoverText: "a word or phrase that is used in at least one scope/context to refer to a specific concept."
---
......
......@@ -4,6 +4,7 @@ title: Glossary of eSSIF-Lab
scopeid: essifLab
type: glossary
typeid: essifLab
stage: draft
hoverText: "essifLab-glossary - popuptext tbd"
---
<!--A glossary is a list of terms with (short) explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s).-->
......
......@@ -4,6 +4,7 @@ title: "Jurisdiction"
scopeid: essifLab
type: concept
typeid: jurisdiction
stage: draft
hoverText: "jurisdiction - popuptext t.b.d."
---
......
......@@ -4,6 +4,7 @@ title: "Knowledge"
scopeid: essifLab
type: concept
typeid: knowledge
stage: draft
hoverText: "knowledge popover text"
---
......
......@@ -4,6 +4,7 @@ title: "Objective"
scopeid: essifLab
type: concept
typeid: objective
stage: draft
hoverText: "Something toward which effort is directed: an aim, goal, or end of action"
---
......
......@@ -4,6 +4,7 @@ title: "Organization"
scopeid: essifLab
type: concept
typeid: organization
stage: draft
hoverText: "popuptext for Organization tbd"
---
......
......@@ -4,6 +4,7 @@ title: "Owner"
scopeid: essifLab
type: concept
typeid: owner
stage: draft
hoverText: "a Party that has the legal or rightful title to control something."
---
......
......@@ -4,6 +4,7 @@ title: "Party"
scopeid: essifLab
type: concept
typeid: party
stage: draft
hoverText: "Entity that has knowledge about what exists, ways to reason with that knowledge, and ways for making decisions in a Self-Sovereign fashion."
---
......
......@@ -4,6 +4,7 @@ title: "Pattern: Jurisdictions (Scope: eSSIF-Lab)"
scopeid: essifLab
type: pattern
typeid: jurisdictions
stage: draft
hoverText: "jurisdiction pattern - popuptext t.b.d."
---
<!-- A pattern captures/describes a set of concepts, relations between them, and rules or constraints that (instances) thereof comply with. As such, it is a concise and possibly formal description of a coherent set of ideas, a mental model if you will, that can be used to facilitate one's thinking about/with these concepts.
......
......@@ -4,6 +4,7 @@ title: "Pattern: Mental Models"
scopeid: essifLabTerminology
type: pattern
typeid: mental-model
stage: draft
hoverText: "This pattern captures the foundational concepts and relations that we need for creating, maintaining and using (decentralized) vocabularies (terminologies) that groups of people can use for the specific purposes they pursue."
---
......
......@@ -4,6 +4,7 @@ title: "Pattern: Party-Action (Scope: eSSIF-Lab)"
scopeid: essifLab
type: pattern
typeid: party-action
stage: draft
hoverText: "This pattern captures the foundational concepts and relations that we need for thinking about people (human beings), organizations, and how they interact with one another in a decentralized, self-sovereign way - which means that each of them decides for itself whether or not to interact with others, how to conduct such interactions, etc., thereby only taking external influences into account if they want, or have some need to do so."
---
......
......@@ -4,6 +4,7 @@ title: "Pattern: eSSIF-Lab Terminology Corpus"
scopeid: essifLab
type: pattern
typeid: terminology
stage: draft
hoverText: "pattern-terminology - hovertext"
---
<!-- A pattern captures/describes a set of concepts, relations between them, and rules or constraints that (instances) thereof comply with. As such, it is a concise and possibly formal description of a coherent set of ideas, a mental model if you will, that can be used to facilitate one's thinking about/with these concepts.
......
......@@ -5,6 +5,7 @@ scopeid: essifLab
type: term
typeid: peer-agent
conceptref: essifLab:Agent
stage: draft
hoverText: "(Peer Agent of a Agent): the other Agent with whom this Agent is communicating in the context of a transaction."
---
......
......@@ -5,6 +5,7 @@ scopeid: essifLab
type: term
typeid: peer-party
conceptref: essifLab:party
stage: draft
hoverText: "(Peer Party of a Party): the other Party that is a participant in a transaction of that Party."
---
......
---
id: essifLabTerminology-scope
title: eSSIF-Lab Terminology
scopeid: essifLabTerminology
hoverText: "essifLabTerminology - popuptext t.b.d"
id: essifLab-scope
title: "Scope: eSSIF-Lab"
scopeid: essifLab
type: scope
typeid: essifLab
stage: draft
hoverText: "scope essifLab - popuptext tbd"
---
## Governance
......
......@@ -5,6 +5,7 @@ scopeid: essifLab
type: term
typeid: ssi-agent
conceptref: essifLab:Agent
stage: draft
hoverText: "Agent that provides SSI services."
---
......
......@@ -4,6 +4,7 @@ title: "Transaction Result Dispatcher"
scopeid: essifLab
type: concept
typeid: transaction-result-dispatcher
stage: draft
hoverText: "hovertext for transaction-result-dispatcher"
---
......
......@@ -4,6 +4,7 @@ title: "transaction-validation-engine"
scopeid: essifLab
type: concept
typeid: transaction-validation-engine
stage: draft
hoverText: "transaction-validation-engine"
---
......
......@@ -4,6 +4,7 @@ title: "TRD - Transaction Result Dispatcher"
scopeid: essifLab
type: concept
typeid: trd
stage: draft
hoverText: "trd - popuptext t.b.d."
---
......
......@@ -4,6 +4,7 @@ title: "TVE - Transaction Validation Engine"
scopeid: essifLab
type: concept
typeid: tve
stage: draft
hoverText: "tve - popuptext t.b.d."
---
......
---
id: readme-generator-extensions
title: "Creating Terminology Artifact Generators"
stage: draft
stage: draft
stage: draft
stage: draft
hoverText: "Various terminological artifacts are generated. Click to see how you can create your own."
---
......
---
id: readme-making-contributions
title: Making Contributions to the Terminology Corpus
stage: draft
hoverText: "Click on the text to navigate to the instructions on how to contribute to the terminology."
---
......
......@@ -4,6 +4,7 @@ title: "<New Term>"
scopeid: <existing-scopeID>
type: concept
typeid: <new-termID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this concept>"
---
<!--A concept tries to capture the idea behind a classification of entities, allowing us to reason about everything in the class as if it were one thing. This file specifies the idea(s) that, within the scope of `<existing-scopeID>` will be referred to using <New Term>.
......
......@@ -4,6 +4,7 @@ title: "Title text for this dictionary"
scopeid: <existing-scopeID>
type: dictionary
typeid: <new-dictionaryID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this Dictionary>"
---
<!--A dictionary is an alphabetically sorted list of terms with associated meanings that originate from multiple scopes.
......
......@@ -4,6 +4,7 @@ title: "Title text for this glossary"
scopeid: <existing-scopeID>
type: glossary
typeid: <new-glossaryID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this glossary>"
---
<!--A glossary is an alphabetically sorted list of terms with (short) explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s).
......
......@@ -4,6 +4,7 @@ title: "Pattern: <name of the pattern>"
scopeid: <existing-scopeID>
type: pattern
typeid: <new-patternID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this pattern>"
---
<!-- A pattern captures/describes a set of concepts, relations between them, and rules or constraints that (instances) thereof comply with. As such, it is a concise and possibly formal description of a coherent set of ideas, a mental model if you will, that can be used to facilitate one's thinking about/with these concepts.
......
......@@ -4,6 +4,7 @@ title: "Scope: <New Scope>"
scopeid: <existing-scopeID>
type: scope
typeid: <new-subscopeID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this item>"
---
<!--A scope is something within which concepts can be associated with terms, thereby creating a vocabulary that can be used to meaningfully express ideas, arguments, etc.
......
......@@ -4,6 +4,7 @@ title: "<title of rendered document>"
scopeid: <scopeID>
type: <type>
typeid: <typeID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this document>"
---
<!--This template specifies the docusaurus attribtues that must be in place for the terminology-plugin to function properly. For specific generators, additional content may be required. That should be specified in the individual templates that specify the artifacts that such generators create.
......
......@@ -5,6 +5,7 @@ scopeid: <existing-scopeID>
type: term
typeid: <new-termID>
conceptref: <ExistingConceptScopeID>:<ExistingtermID>
stage: draft
hoverText: "<Text that pops up when the user hovers over a reference to this term>"
---
<!--A Term is a word or phrase that is used in at least one scope (context and/or for specific purposes) to refer to some concept.
......
......@@ -63,6 +63,7 @@ and it needs to consist of the following structure:
---
id: term
title: Term page
stage: draft
hoverText: This hover text will appear in the documentation page that you reference this term
---
......
......@@ -4,11 +4,26 @@ title: "Action"
scopeid: essifLab
type: concept
typeid: action
hoverText: "something that is done by an actor"
stage: draft
hoverText: "something that is actually done/executed by a single actor (as a single operation) for some party within a specific context"
---
## Short Description
An **Action** is something that is actually done/executed by a %%actor|actor%% in some context (i.e. in a specific place, at a specific time). During the time interval in which the action is executed, the actor may still execute other actions in other execution-contexts (multi-tasking). An action is executed for, or on behalf of, a specific %%party|party%%, which means that the primary guidance for executing the action, e.g. how to execute it, boundary conditions within which the execution must take place, etc., comes from the %%knowledge|knowledge%% of that party. The actor is assumed to have appropriate access to the knowledge of that party. In order to properly execute the action, the executing actor may also use additional knowledge(s) to which it has access.
## Purpose
The ability to distinguish between (non)actions allows one to determine which (kinds of) %%actors|actor%% are capable of executing actions (e.g. by establishing that they have the competences required by the party), and as a consequence may be permitted and/or required to execute them. Also, this ability enables parties to determine the execution-policy, i.e. the set of rules and other guidance that actors should obey or comply with when exeucting an action on its behalf.
## Criterion:
An **Action** is something that is done by an actor, can be considered a single operation, and is performed in a specific context, for or on behalf of a specific party, i.e. in accordance with the policy rules that this party has established for such actions.
## Examples:
- filling in a form and submitting it.
- cleaning a car.
## Related Concepts
<!--Link to any concepts that are similar but distinct, with a note about the relationship.-->
- OED defines Action as the fact or process of doing something, typically to achieve an aim ([OED](https://www.lexico.com/definition/action)), which is too generic for our purposes.
### Background:
## Background:
The %%party-action pattern|pattern-party-action%% provides an overview of how this concept fits in with related concepts.
\ No newline at end of file
......@@ -4,23 +4,25 @@ title: "Actor"
scopeid: essifLab
type: concept
typeid: actor
stage: draft
hoverText: "Entity that can act (do things), e.g. people, machines, but not organizations."
---
## Criterion:
Entity that is capable of acting (doing things).
## Examples:
People obviously qualify, as do robots and other machines. Stones, pictures, ideas, etc. do not qualify.
## Short Description
An **Actor** is someone or something that can actually do things, such as people or machines. Actors will generally do things, i.e. execute %%actions|action%% in different ways, depending on the context, or the %%party|party%% for whom they do this.
We specifically note that enterprises, governments, and other organizations do not qualify.
## Purpose
The ability to distinguish between (non)actors allows one to determine which (kinds of) actors are capable of executing which (kinds of) %%actions|action%%, specifically since %%organizations|organization%% do not qualify as an actor (they need actors to get things done).
### Background:
further background on this concept is provided by the ['Party-Action' pattern|pattern-party-action]
## Criterion:
Entity that is capable of actually executing %%actions|action%% (acting, doing things).
---
[^1]: Reasoning means: inferring conclusions from data, regardless of the kind of logic that is being used, or whether the reasoning is coherent, or consistent.
## Examples:
[^2]: This means that the party can do this all by itself. For humans, the rights for this are laid down e.g. in the [ECHR](https://www.echr.coe.int "European Convention of Human Rights") ([ECHR articles 9-11](https://www.echr.coe.int/Documents/Convention_ENG.pdf))
- People (human beings) obviously qualify, as do robots and other machines.
- Stones, pictures, ideas, etc. do not qualify.
- Software applications qualify, provided they are actually running on hardware. An app that is just sitting e.g. on a mobile phone but isn't executed does not qualify.
- Enterprises, governments, and other %%organizations|organization%% do not qualify.
[^3]: While the case can be made that (some) electronic components can reason, they do not do so in a self-sovereign fashion as intended by this definition. We do not want to discuss AI-equipment here.
## Background:
The %%party-action pattern|pattern-party-action%% provides an overview of how this concept fits in with related concepts.
......@@ -4,14 +4,19 @@ title: "Agent"
scopeid: essifLab
type: concept
typeid: agent
hoverText: "Agent (of a Party): Actor that is currently working on behalf of a Party."
stage: draft
hoverText: "An actor that is (at that point in time) executing an action for, or on behalf of a Party."
---
## Short Description
An %%Actor|actor%% that is executing on action on behalf of some %%Party|party%%, which means that the execution of that action is subject to the conditions and other guidance set by that Party, then we say the Actor acts as an Agent of that Party. A Person, that is both an Actor and a Party can hence be seen as its own Agent. Agency is further detailed in the ['Party-Action' pattern|pattern-party-action].
%%Actors|actor%% execute %%actions|action%% for, or on behalf of some %%party|party%%, because parties are not considered to be capable of acting.[^1] Agents must act in accordance with the party for which they execute such actions, which means that for every kind of action, such parties must provide the proper guidance for their agents, e.g. in terms of policies (rules), working instructions, programs etc. We use the term %%digital agent|digital-agent%%
## Purpose
The ability to distinguish between (non)agents is relevant in many situations, including:
- electronic communication: the agent
## Criterion:
%%Actor|actor%% that is momentarily executing an action on behalf of a %%Party|party%%.
a property that is attributed to an %%Actor|actor%% whenever it is executing an action for, or on behalf of some %%party|party%%.
## Examples:
......@@ -22,3 +27,6 @@ An %%Actor|actor%% that is executing on action on behalf of some %%Party|party%%
- A company that makes cars may use robots that weld parts of a car together; these robots acts as Agents for that company.
- A (running) webserver that accepts product orders for a retailer acts as a (digital) Agent for that retailer.
- A wallet app that runs on a phone and that is exclusively used by a single person acts as a (digital) Agent for that person.
## Background:
The %%party-action pattern|pattern-party-action%% provides an overview of how this concept fits in with related concepts.