Commit 212ef032 authored by Maria Iliadi's avatar Maria Iliadi Committed by fmerg

Integration of terminology engine v1 to framework

parent 46fd4ad2
......@@ -2,5 +2,3 @@
id: essif-lab-glossary
title: eSSIF-Lab Glossary
---
to be generated.
# README for terminology-related files.
This document states the requirements for files in this directory, such that they can properly processed into useful and usable Docusaurus documentation.
## Filenames
All file MUST have the structure: `<scopeid>-<type>-<instanceid>.mdx`, where
- `<scopeid>` is the (all lowercase) identifier of an existing scope, i.e. the file `<scopeid>-1-scope.mdx` must exist.
- `<type>` MUST be any of the following:
- `1-scope`
- `2-pattern`
- `3-concept`
- `4-term`
- `5-glossary`
- `<instanceid>` MUST be a lowercase identifier that only uses characters `a`-`z` and `-`.
## Templates
The `terminology/templates` directory contains templates for each of the types. A template file has comments that hold, amongst others, requirements for the contents of instances of that template.
## Referring to terms in documentation files
Any term can be referred to in any documentation file, using the syntax `%%<termref>%%`, where `<termref>` is either the `<conceptid>` of a concept
- `<sometext>` is a text that will be displayed as if it were a term
---
id: essifLab-concept-party
title: Concept: Party (Scope: eSSIF-Lab)
scopeid: essifLab
termid: party
hoverText: "Entity that has knowledge about what exists, ways to reason with that knowledge, and ways for making decisions in a Self-Sovereign fashion."
id: essiflab-concept-party
title: Party (Scope essifLab)
---
## Criterion:
Entity that has knowledge about what exists, ways to reason[^1] with that knowledge, and ways for making decisions in a Self-Sovereign[^2] fashion.
## Examples:
People obviously qualify. Enterprises, governments, and other organizations also qualify as they can be seen as having their own knowledge (e.g. in their registrations, databases etc.), ways to reason with that knowledge (business rules, exercised by their employees or IT systems), and making decision.
People obviously qualify. Enterprises, governments, and other organizations also qualify as they can be seen as having their own knowledge (e.g. in their registrations, databases etc.), ways to reason with that knowledge (business rules, exercised by their employees or IT systems), and making decision.
Stones, pictures, ideas, etc. do not qualify. Also, electronic components do not qualify[^3].
......@@ -22,4 +19,4 @@ to be elaborated
[^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))
[^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.
\ No newline at end of file
[^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.
---
id: essifLab-glossary
title: Glossary of eSSIF-Lab
scopeid: essifLab
glossaryid: glossary
hoverText: "<Text that pops up when the user hovers over a reference to this eSSIF-Lab glossary>"
id: glossary-essiflab
title: Glossary eSSIF-Lab (Scope essiflab)
---
<!--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).-->
......
---
id: essifLab-scope
title: Scope: eSSIF-Lab
scopeid: essifLab
hoverText: "<essifLab-scope hovertext>"
id: scope-essif-lab
title: Scope eSSIF-Lab
---
## Governance
......
---
id: essifLabTerminology-concept-concept
title: Concept: Concept (Scope: essifLabTerminology)
scopeid: essifLabTerminology
termid: concept
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."
id: essiflabterminology-concept-concept
title: Concept (Scope essifLabTerminology)
---
## Short Description
......@@ -16,7 +13,7 @@ Working together is easier when you and your peers share the same ideas. We need
## Criteria
<!--REQUIRED--How is this concept different from related ideas? What are essential characteristics that must be true? This is where you specify the [intensional definition](https://en.wikipedia.org/wiki/Extensional_and_intensional_definitions) of the concept, i.e. the necessary and sufficient conditions for when the term should be used. This makes that the conceptomes crystal clear. In the case of nouns, this is equivalent to specifying the properties that an object needs to have in order to be counted as a referent of the term.-->
A (description/specification of a) Concept MUST be [intensionally defined](https://en.wikipedia.org/wiki/Extensional_and_intensional_definitions), i.e. associated with a criterion that can be used to determine whether or not someone or something qualifies as (an instance of) that Concept, and that has the property that it has been shown that the vast majority of contributors and other users apply it in the same manner in different situations (i.e. they arrive at the same conclusion as to whether or not someone or something qualifies under that criterion in any given situation).
A (description/specification of a) Concept MUST be [intensionally defined](https://en.wikipedia.org/wiki/Extensional_and_intensional_definitions), i.e. associated with a criterion that can be used to determine whether or not someone or something qualifies as (an instance of) that Concept, and that has the property that it has been shown that the vast majority of contributors and other users apply it in the same manner in different situations (i.e. they arrive at the same conclusion as to whether or not someone or something qualifies under that criterion in any given situation).
## Examples
<!--Provide a few sentences in which you give examples that obviously qualify as instances of `Concept`, and that do NOT obviously qualify. Also, provide examples that are not (so) obvious, but help users to better understand its intension.-->
......@@ -53,7 +50,7 @@ A (description/specification of a) Concept MUST be [intensionally defined](https
There is an important [distinction](https://simple.wikipedia.org/wiki/Concept) between concepts and the (multitude of) terms (names, labels) that we need to be able to talk and reason (argue) about them. Please consider that
* different terms are used in different contexts for the same concept
* in different contexts, a single term may refer to different concepts
* in different contexts, a single term may refer to different concepts
* to resolve terminological disputes, which usually are about the 'correct' meaning of a term, try to establish the criteria that the different participants use for the concept behind the term. That helps participants understand each others (different) positions, and provides a better basis for resolving the conflict.
---
......@@ -62,4 +59,4 @@ There is an important [distinction](https://simple.wikipedia.org/wiki/Concept) b
[^1]: WikiPedia has a concise [explanation of concepts](https://en.wikipedia.org/wiki/Concept). We use the term 'concept' as a [mental representation](https://en.wikipedia.org/wiki/Mental_representation).
[^2]: For the difference between 'Concept' and 'Term', see https://simple.wikipedia.org/wiki/Concept.
\ No newline at end of file
[^2]: For the difference between 'Concept' and 'Term', see https://simple.wikipedia.org/wiki/Concept.
---
id: essifLabTerminology-concept-glossary
title: Concept: Glossary (Scope: essifLabTerminology)
scopeid: essifLabTerminology
termid: glossary
hoverText: "an alphabetically sorted list of termsort) explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
id: essiflabterminology-concept-glossary
title: Glossary (Scope essifLabTerminology)
---
## Short Description
......@@ -39,4 +36,4 @@ The [eSSIF-Lab Glossary](essif-lab-glossary) contains the words that are defined
[^1]: the text for footnote [^1] goes here.
-->
\ No newline at end of file
-->
---
id: essifLabTerminology-concept-term
title: Term (Scope: essifLabTerminology)
scopeid: essifLabTerminology
termid: term
hoverText: "a word or phrase that is used in at least one scope/context to refer to a specific concept."
id: essiflabterminology-concept-term
title: Term (Scope essifLabTerminology)
---
## Short Description
......@@ -19,7 +16,7 @@ Understanding words or phrases uttered by others requires that we are able to 't
## Criteria
<!--How is this concept different from related ideas? What are essential characteristics that must be true? This is where you specify the [intensional definition](https://en.wikipedia.org/wiki/Extensional_and_intensional_definitions) of the concept, i.e. the necessary and sufficient conditions for when the term should be used. This makes that the conceptomes crystal clear. In the case of nouns, this is equivalent to specifying the properties that an object needs to have in order to be counted as a referent of the term.-->
A Term MUST be a word or phrase that is linked to at least one %%context|scope%% and refers to precisely one %%concept%%.
A Term MUST be a word or phrase that is linked to at least one %%context|scope%% and refers to precisely one %%concept%%.
## Examples
<!--Provide a few sentences in which you give examples that obviously qualify as instances of `Term`, and that do NOT obviously qualify. Also, provide examples that are not (so) obvious, but help users to better understand its intension.-->
......@@ -52,7 +49,7 @@ A Term MUST be a word or phrase that is linked to at least one %%context|scope%%
There is an important [distinction](https://simple.wikipedia.org/wiki/Concept) between concepts and the (multitude of) terms (names, labels) that we need to be able to talk and reason (argue) about them. Please consider that
* different terms are used in different contexts for the same concept
* in different contexts, a single term may refer to different concepts
* in different contexts, a single term may refer to different concepts
* to resolve terminological disputes, which usually are about the 'correct' meaning of a term, try to establish the criteria that the different participants use for the concept behind the term. That helps participants understand each others (different) positions, and provides a better basis for resolving the conflict.
---
......@@ -61,4 +58,4 @@ There is an important [distinction](https://simple.wikipedia.org/wiki/Concept) b
[^1]: WikiPedia has a concise [explanation of concepts](https://en.wikipedia.org/wiki/Concept). We use the term 'concept' as a [mental representation](https://en.wikipedia.org/wiki/Mental_representation).
[^2]: For the difference between 'Concept' and 'Term', see https://simple.wikipedia.org/wiki/Concept.
\ No newline at end of file
[^2]: For the difference between 'Concept' and 'Term', see https://simple.wikipedia.org/wiki/Concept.
---
id: essifLabTerminology-pattern-mental-model
title: Pattern: Mental Models (Scope: essifLabTerminology)
scopeid: essifLabTerminology
patternid: mental-model
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."
id: essiflabterminology-pattern-MentalModels
title: Pattern Mental Models (Scope essifLabTerminology)
---
## Purpose
......@@ -32,4 +29,4 @@ Different terms can be used to identify the same concept. Car and Automobile are
[^1]: the text for footnote [^1] goes here.
-->
\ No newline at end of file
-->
---
id: essifLabTerminology-scope
title: eSSIF-Lab Terminology
scopeid: essifLabTerminology
hoverText: "<essifLabTerminology-scope hovertext>"
id: scope-essifLabTerminology
title: Scope eSSIF-Lab Terminology
---
## Governance
......
---
id: essiflab-pattern-Party-action
title: Pattern Party-Action (Scope essifLab)
---
<!--A %%pattern%% capture a set of %%concepts:concept%%, 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.
This file documents a pattern called `<NewPattern>` within the scope of `<ExistingScope>`.
Before completing this template, please change every instance of
- `<ExistingScope>` into a text that refers to the %%scope%% within which the %%pattern%% is to be defiend;
- `<NewPattern>` into the name that will be used within `<ExistingScope>` to refer to that %%concept%%.
Then, provide contents for the sections as you wish. You MUST provide contents for the sections 'Scope' and 'Criteria'-->
## Scope
<!--REQUIRED--Short text (label, abbreviation) used to refer to the %%scope%% within which the %%concept%% is defined. The default is essifLab.-->
essifLab
## Purpose
<!--Concisely describe what can you do with the pattern that is (at least) harder if you didn't have it.-->
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.
## Introduction
<!--Gently introduce the pattern, by referring to real-world situations and using colloquial terms, so that when someone has read the text, (s)he knows what it is about, and is ready to delve into the specifics of the pattern-->
TL;DR: This pattern models that %%Parties:Party%% (humans, organizations) perform %%Actions:Action%% for the purpose of realizing their %%Objectives:Objective%%. %%Parties:Party%% are not considered to actually execute such %%Actions:Action%%; they have (human and non-human) %%Actors:Actor%% that work for them, execute such %%Actions:Action%%, using the %%Party%%’s %%Knowledge%% as the (authoritative) guidance for executing the %%Actions:Action%% (as well as any other relevant %%Knowledge%% they can access).
The essential characteristic of %%Parties:Party%% is their 1-1 link with %%Knowledge%%, which they continually update and use e.g. for reasoning, decision making, and determining e.g. what to do, when, and with whom. %%Knowledge%% not only includes (observable) facts, but also opinions, e.g. regarding the %%Entities:Entity%% it knows to exist, relations between them, and rules (constraints, [logic](https://en.wikipedia.org/wiki/Logic)[^1]) that can be used to classify and reasoning about them, and for making decisions.
Perhaps the most important idea in this pattern is that our %%Party%% concept is not considered to (be able to) act, and they need %%{{Actors:Actor%%:Actor}} (i.e. %%Entities:Entity%% that _can_ act) to act on their behalf and thus make them perform. This does, however, not preclude having %%Entities:Entity%% that are both %%Party%% and %%Actor%% - e.g. humans - and that such %%Entities:Entity%% can act on their ‘own’ behalf. And we can continue to use the commonly used form of speech in which a %%Party%% performs some %%Action%%, by realizing that this means that there is (at least) one %%Actor%% that is actually executing that %%Action%%.
In this pattern, %%Knowledge%% takes center stage. %%Knowledge%% contains %%Objectives:Objective%% to be realized and managed. This not only triggers all sorts of %%Actions:Action%% to be performed, but also guides their execution in terms of when an %%Action%% should start, when it terminates, which %%Actors:Actor%% qualify for executing it, etc. Everything that is specific for a %%Party%% is reflected in its %%Knowledge%%.
This works well for human beings, which are both a %%Party%% and an %%Actor%%. So a human being can act, implying itself as an %%Actor%%, and using its personal %%Knowledge%% as guidance. The model also works when a human being (as a %%Party%%) may hire someone else (as an %%Actor%%), e.g. to fill in his tax return form. This other is guided by the %%Knowledge%% of the human being that hired him, and uses its own %%Knowledge%% for the details of filling in the tax form.
It also works well for organizations, which are typically companies, enterprises, governments or parts thereof, i.e. groups of human beings and possibly other %%Actors:Actor%% that, as a group, fit the criteria for being a %%Party%%. This group of %%Actors:Actor%% would typically work to realize the organization’s %%Objectives:Objective%%, being guided by the organization’s %%Knowledge%% (registrations, policies, etc.). Like human beings, an organization may (have an appropriate %%Actor%%) decide to hire or fire %%Actors:Actor%% for longer or shorter periods.
%%Parties:Party%% set %%Objectives:Objective%% that they seek to achieve, the most basic of which perhaps is its mission, or its ‘raison d'être’, to the realization of which all of its %%Actions:Action%% are (ultimately) aimed. Every %%Objective%% is owned by a single %%Party%% (we do not consider ‘shared objectives’[^2]).
## Notations
<!--This (optional) section specifies the notations that are used, or refers to such a specification.-->
## <!-- any number of other sections, as is fit for describing the pattern -->
<!--text as appropriate for such a section -->
---
## Footnotes
<!--This (optional) section contains any footnotes that may have been specified in the text above.-->
[^1]: I.e. “logic is the analysis and appraisal of arguments (Gensler, Harry J. (2017) [2002]. "Chapter 1: Introduction". Introduction to logic (3rd ed.). New York: Routledge. p. 1. [doi:10.4324/9781315693361](https://doi.org/10.4324%2F9781315693361). [ISBN 9781138910591](https://en.wikipedia.org/wiki/Special:BookSources/9781138910591). OCLC [957680480](https://www.worldcat.org/oclc/957680480).)
[^2]: The Networked Risk Management (NRM) pattern deals with the setting and realizing of %%Objectives:Objective%%, the associated risk management etc., and explains the reasoning for not having shared %%Objectives:Objective%%.
\ No newline at end of file
---
id: essiflab-concept-objective
title: Objective (Scope essifLab)
---
## Scope
essifLab
## Criterion:
Something toward which effort is directed: an aim, goal, or end of action ([Merriam-Webster](https://www.merriam-webster.com/dictionary/objective))
## Examples:
Anything that, according to a %%Party%% c.q. its way of thinking, is important to be realized, qualifies as an Objective (and identifies its owner as that %%Party%%)
### Xxx:
The %%Knowledge%%/judgements of a %%Party%% are what makes something an %%Objectiv%%e (owned by that %%Party%%).
---
id: essiflab-term-Purpose
title: Purpose (Scope:essifLab)
---
## Scope
<!-- *REQUIRED* Short text (label, abbreviation) used to refer to the %%scope%% within which the %%term%% is defined. The default is essifLab.-->
essifLab
## Concept
<!--Specify the %%concept-file%% that serves as the definition of the %%concept%% to which `Purpose` will refer-->
objective
## Purpose
<!--State the purpose(s) for which it is necessary (or at least: desirable) to define `Purpose`.-->
The purpose of using 'purpose' as a synonym for 'objective' is none other than to test the software that generates the glossaries.
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
---
id: glossary-essiflabterminology
title: Glossary eSSIF-Lab Terminology (Scope essiflabterminology)
---
<!--A %%glossary%% is a list of %%terms:term%% with (short) explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s).-->
## Scope
<!-- *REQUIRED* Short text (label, abbreviation) that can be used within eSSIF-Lab (or beyond) to refer to the scope within which this glossary resides. The default is essifLab.-->
essifLab
## Purpose
<!--State the purpose(s) that this glossary aims to fulfill, in such a way that readers can easily determine whether or not it is useful for them to use it.-->
This glossary lists the basic concepts that are needed by the various stakeholders within the eSSIF-Lab project, ranging from governance, business, process, technology etc. The idea is that it defines at least the set of concepts that are often used in these varied domains, allowing a reader with a specific background to learn how the concept is used from other (valid) perspectives that may be alien to him/her.
## Sources
<!--Here, the sources should be identified from which the glossary entries (and their descriptions) are to be collected-->
### Include
<!--Specify the %%scope-files:scope-file%% that are to serve as a source for this glossary-->
* eSSIF-Lab
### Terms
<!--Specify the %%term-files:term-file%% that are to serve as a source for this glossary. If a term is defined in a scope as well as in a %%term-file%%, the latter takes precedence.-->
### Patterns
<!--Specify the %%pattern-files:pattern-file%% that are to serve as a source for this glossary. If a term is defined in a scope or as a term as well as in a %%pattern-file%%, the latter takes precedence.-->
### Concepts
<!--Specify the %%concept-files:concept-file%% that are to serve as a source for this glossary. If a term is defined in a scope, or as a term, or in a pattern as well as in a %%concept-file%%, the latter takes precedence.-->
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
---
id: scope-NewScope
title: Scope <NewScope>
---
<!--A %%scope%% is something within which %%concepts:concept%% can be associated with %%terms:term%%, thereby creating a vocabulary that can be used to meaningfully express ideas, arguments, etc.-->
## Scope
<!-- *REQUIRED* Short text (label, abbreviation) that can be used to refer to the scope. Scope identifiers/labels should be useable as prefix for terms, thus providing a mechanism to refer to terms defined in other scopes, and therefore should consist of lower-case characters [a-z0-9], preferably without `-` or `_` characters. For eSSIF-Lab, we use `essifLab`.-->
## Governance
<!--This section identifies the %%organizational body:Jurisdiction%% that governs the %%scope%%. Optionally, a reference to the governance framework/procedures may be made.-->
## Objectives/Issues
<!--State the purpose for having the scope in terms of objectives that are aimed for and/or issues that are to be addressed.-->
## Scope URI
<!--Optionally specify the URI by which this scope may be identified-->
## Inclusions
<!--This %%scope%% may include other scopes, which means that everything in that other scope is also considered part of this %%scope%%. In case of collisions, this %%scope%% MUST provide a means to resolve such conflicts without modifying anything in included scopes. For eSSIF-Lab, we include `essifLabTerminology`-->
## Notes
<!--Anything els that's worth mentioning.-->
## Tags
<!--Add hash tags here that allow us to group concepts in useful ways.-->
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
---
id: pattern-ExistingScope-NewPattern
title: Pattern <NewPattern> (Scope <ExistingScope>)
---
<!--A %%pattern%% captures a set of %%concepts:concept%%, 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.
This file documents a pattern called `<NewPattern>` within the scope of `<ExistingScope>`.
Before completing this template, please change every instance of
- `<ExistingScope>` into a text that refers to the %%scope%% within which the %%pattern%% is to be defiend;
- `<NewPattern>` into the name that will be used within `<ExistingScope>` to refer to that %%concept%%.
Then, provide contents for the sections as you wish. You MUST provide contents for the sections 'Scope' and 'Criteria'-->
## Scope
<!-- *REQUIRED* Short text (label, abbreviation) used to refer to the %%scope%% within which the %%concept%% is defined. The default is essifLab.-->
essifLab
## Purpose
<!-- Concisely describe what can you do with the pattern that is (at least) harder if you didn't have it.-->
## Introduction
<!-- Gently introduce the pattern, by referring to real-world situations and using colloquial terms, so that when someone has read the text, (s)he knows what it is about, and is ready to delve into the specifics of the pattern-->
## Notations
<!-- This (optional) section specifies the notations that are used, or refers to such a specification.-->
## <!-- any number of other sections, as is fit for describing the pattern -->
<!-- text as appropriate for such a section -->
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
\ No newline at end of file
---
id: concept-ExistingScope-NewConcept
title: Concept <NewConcept> (Scope <ExistingScope>)
---
<!--A %%concept%% tries to capture the idea behind a classification of %%entities:entity%%, 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 `<ExistingScope>` will be referred to using the %%term%% `<NewConcept>`.
Before completing this template, please change every instance of
- `<ExistingScope>` into a text that refers to the %%scope%% within which the %%concept%% is to be defiend;
- `<NewConcept>` into the %%term%% that will be used within `<ExistingScope>` to refer to that %%concept%%.
Then, provide contents for the sections as you wish. You MUST provide contents for the sections 'Scope' and 'Criteria'-->
## Scope
<!--REQUIRED--Short text (label, abbreviation) used to refer to the %%scope%% within which the %%concept%% is defined. The default is essifLab.-->
essifLab
## One-line Summary
<!--A single sentence that describe the %%concept%% to a layperson with reasonable accuracy. This line may be used to explain `Concept` in a glossary, or as a popover text when it is referred to in other documentation.-->
## Short Description
<!--REQUIRED--in 1-3 sentences that describe the %%concept%% to a layperson with reasonable accuracy.-->
## Purpose
<!--Describe why the %%concept%% is needed. What purposes does it serve? What can you do with it that you cannot do (as well) without it? What objectives does it help realize? Why is this %%concept%% relevant within its %%scope%% of definition?-->
## Criteria
<!--REQUIRED--How is this %%concept%% different from related ideas? What are essential characteristics that must be true? This is where you specify the [intensional definition](https://en.wikipedia.org/wiki/Extensional_and_intensional_definitions) of the %%concept%%, i.e. the necessary and sufficient conditions for when the term should be used. This makes that the %%concept%% becomes crystal clear. In the case of nouns, this is equivalent to specifying the properties that an object needs to have in order to be counted as a referent of the term.-->
## Examples
<!--Provide a few sentences in which you give examples that obviously qualify as instances of `<NewConcept>`, and that do NOT obviously qualify. Also, provide examples that are not (so) obvious, but help users to better understand its intension.-->
## Related Concepts
<!--Link to any %%concepts:concept%% that are similar but distinct, with a note about the relationship.-->
## Domains
<!--In which general knowledge ecosystems or mental model families does this %%concept%% play a role?-->
## Tags
<!--Add hash tags here that allow us to group concepts in useful ways.-->
## Use-cases
<!--This (optional) section specifies an (optional) introductory paragraph, and a level-3 (i.e. `###`) subsection for every use case it describes. Every such use-case SHOULD
- describe the situation/context of the use-case;
- show how to apply `<NewConcept>` to/in that situation;
- shows the relevance of having `<NewConcept>` for the use-case as opposed to not having it.-->
## Notes
<!--This (optional) section is the place to put anything for which there is no other good place to put it.-->
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
\ No newline at end of file
---
id: term-ExistingScope-NewTerm
title: Term <NewTerm> (Scope <ExistingScope>)
---
<!--A Term is a word or phrase that is used in at least one scope (context and/or for specific purposes) to refer to `<ExistingConcept>`, which is an existing %%concept%%.
Please change every instance of
- `<ExistingScope>` into a text that refers to an existing %%scope%%;
- `<ExistingConcept>` into a text that refers to an existing %%concept%%;
- `NewTerm` into the term that this file links to `<ExistingConcept` within `ExistingScope>`.
-->
## Scope
<!-- *REQUIRED* Short text (label, abbreviation) used to refer to the %%scope%% within which the %%term%% is defined. The default is essifLab.-->
essifLab
## Concept
<!-- *REQUIRED* Specify the %%concept-file%% that serves as the definition of the %%concept%% to which `NewTerm` will refer-->
## Purpose
<!--State the purpose(s) for which it is necessary (or at least: desirable) to define `NewTerm`.-->
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
\ No newline at end of file
---
id: glossary-ExistingScope-NewGlossary
title: Glossary <NewGlossary> (Scope <ExistingScope>)
---
<!--A %%glossary%% is a list of %%terms:term%% with (short) explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s).-->
## Scope
<!-- *REQUIRED* Short text (label, abbreviation) used to refer to the %%scope%% within which the %%glossary%% is defined. The default is essifLab.-->
essifLab
## Purpose
<!--State the purpose(s) that this glossary aims to fulfill, in such a way that readers can easily determine whether or not it is useful for them to use it.-->
## Sources
<!--This section specifies the sources from which the glossary entries (and their descriptions) are to be collected. All terms from all sources are included in the glossary. If that is too much, then you should revert to stating individual terms, patterns or concepts (see below).-->
### Terms
<!--Specify the %%term-files:term-file%% that are to be included in this glossary. If a term is defined in a scope as well as in a %%term-file%%, then both are included in the glossary (where the scope identifier is used to distinguish between them). -->
### Concepts
<!--Specify the %%concept-files:concept-file%% that are to serve as a source for this glossary. If a term is defined in a scope, or as a term, or in a pattern as well as in a %%concept-file%%, the latter takes precedence.-->
### Patterns
<!--Specify the %%pattern-files:pattern-file%% that are to serve as a source for this glossary. If a term is defined in a scope or as a term as well as in a %%pattern-file%%, then both are included in the glossary (where the scope identifier is used to distinguish between them).-->
### Glossaries
<!--Specify the %%glossary-files:glossary-file%% all %%term%%s of which are to be included in this glossary.-->
<!--
---
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
---
id: <ExistingScopeID>-conceptproposal-<NewTermID>
title: Concept proposal for: <NewTermID> (Scope: <Existing Scope>)
scopeid: <ExistingScopeID>
term: <NewTerm>
hoverText: "<Text that pops up when the user hovers over a reference to this concept>"
id: concept-ExistingScope-NewConcept
title: Concept proposal for <NewConcept> (Scope <ExistingScope>)
---
<!--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 `<ExistingScopeID>` will be referred to using <New Term>.
Please fill in the placeholders in this file as follows:
......@@ -67,4 +64,4 @@ Add hash tags here that allow us to group concepts in useful ways.
[^1]: the text for footnote [^1] goes here.
-->
\ No newline at end of file
-->
---
id: actor
title: Actor
hoverText: "An entity capable of performing formal actions (person, computer)"
---
## Scope
## Criterion
## Examples
---
id: agent
title: Agent
hoverText: "An actor who acts at some particular moment on behalf of a party"
---
## Scope
## Criterion
## Examples
---
id: party
title: Party
hoverText: "An entity capable of taking decisions in a self-sovereign fashion"
---
## Scope
essifLab
## Criterion
Entity that has knowledge about what exists, ways to reason[^1] with that knowledge, and ways for making decisions in a Self-Sovereign[^2] fashion.
## Examples
People obviously qualify. Enterprises, governments, and other organizations also qualify as they can be seen as having their own knowledge (e.g. in their registrations, databases etc.), ways to reason with that knowledge (business rules, exercised by their employees or IT systems), and making decision.
Stones, pictures, ideas, etc. do not qualify. Also, electronic components do not qualify[^3].
[^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.
[^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))
[^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.