Skip to content
GitLab
Commit 63f89407 authored by Rieks Joosten's avatar Rieks Joosten
Browse files

updated terminology files to use %% rather than {{ ... }}; also, templates... 

updated terminology files to use %% rather than {{ ... }}; also, templates have been moved to their own dir
parent f782f562
Pipeline #14216 failed with stage
in 1 minute and 40 seconds
Hide whitespace changes
Inline Side-by-side
docs/terminology/concepts/concept-objective.mdx → docs/terminology/concepts and terms/concept-essifLab-objective.mdx
View file @ 63f89407
import Term from '../src/components/Term'
---
id: concept-objective
title: Concept: Objective
id: concept-essifLab-objective
title: Objective (Scope: essifLab)
---
## Scope
eSSIF-Lab
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}})
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}}).
The %%Knowledge%%/judgements of a %%Party%% are what makes something an %%Objectiv%%e (owned by that %%Party%%).
docs/terminology/concepts/concept-party.mdx → docs/terminology/concepts and terms/concept-essifLab-party.mdx
View file @ 63f89407
import Term from '../src/components/Term'
---
id: concept-party
title: Party
id: concept-essifLab-party
title: Party (Scope: essifLab)
---
## Scope
eSSIF-Lab
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.
......
docs/terminology/concepts/concept-concept.mdx → docs/terminology/concepts and terms/concept-essifLabTerminology-concept.mdx
View file @ 63f89407
import Term from '../src/components/Term'
---
id: concept-concept
title: Concept
id: concept-essifLabTerminology-concept
title: Concept (Scope: essifLabTerminology)
---
## Scope
eSSIF-Lab
<!--REQUIRED--Short text (label, abbreviation) used to refer to the %%scope%% within which the %%concept%% is defined. The default is essifLab.-->
essifLabTerminology
## One-line Summary
<!--A single sentence that describe the {{concept}} to a layperson with reaonable 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.-->
<!--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.-->
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.
## Short Description
<!--in 1-3 sentences that describe the {{concept}} to a layperson with reaonable accuracy.-->
A Concept tries to capture the idea behind a classification of entities[^1], allowing us to reason about everything in the class as if it were one thing. For example, the ideas ([mental representations](https://en.wikipedia.org/wiki/Mental_representation)) you have when processing the sentences "I can drink beer from a beer glass' and 'I can drink beer from a coffee mug' shows that the concepts that are behind 'beer glass' and 'coffee mug' differ.
<!--REQUIRED--in 1-3 sentences that describe the %%concept%% to a layperson with reasonable accuracy.-->
A Concept tries to capture the idea behind a classification of entities[^1], allowing us to reason about everything in the class as if it were one thing. For example, the ideas ([mental representations](https://en.wikipedia.org/wiki/Mental_representation)) you have when processing the sentences "I can drink beer from a beer glass' and 'I can drink beer from a coffee mug' shows that the concepts that are behind 'beer glass' and 'coffee mug' differ. Note that in order to communicate about this idea, we also need a word or phrase (i.e.: a %%term%%) that we can use to refer to (instances of) this idea.
## 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?-->
<!--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?-->
Working together is easier when you and your peers share the same ideas. We need a way to test and ensure, that you and your peers _actually_ have the same understanding, for the purpose of making cooperation easier. Doing so is expected to not only reduce the number of terminological discussions, but also improve the efficiency and effectiveness of the remaining discussions.
## 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 {{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.-->
<!--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.-->
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 NewTerm, and that do NOT obviously qualify. Also, provide examples that are not (so) obvious, but help users to better understand its intension.-->
<!--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.-->
## Related Concepts
<!--Link to any {{concepts|concept}} that are similar but distinct, with a note about the relationship.-->
* {{Term}} is a label that is used in some context to refer to a {{Concept}}[^2], the set of entities that satisfy the concept's criteria, or an arbitrary element of that set. Different contexts may use different terms to refer to a single concept. In a single context, a single term should be used to refer to an individual concept.
<!--Link to any %%concepts:concept%% that are similar but distinct, with a note about the relationship.-->
* %%Term%% is a label that is used in some context to refer to a %%Concept%%[^2], the set of entities that satisfy the concept's criteria, or an arbitrary element of that set. Different contexts may use different terms to refer to a single concept. In a single context, a single term should be used to refer to an individual concept.
* Concept ... ("Scope") is related in several ways. First, there is (precisely, or at most one) Scope that governs the definition/specification of the Concept. Second, there may be (any number of) Scopes that use the Concept, i.e. within which Terms are defined that refer to the Concept
* Concept ... ("Conceptual Model") is a collection of concepts, relations between such concepts, and constraint rules that (elements of) such concepts and relations must satisfy. Such [models](https://en.wikipedia.org/wiki/Conceptual_model) are used to help people know, understand, or simulate a subject the model represents.
## Domains
<!--In which general knowledge ecosystems or mental model families does this {{concept}} play a role?-->
* eSSIF-Lab
<!--In which general knowledge ecosystems or mental model families does this %%concept%% play a role?-->
* essifLab
* ToIP
* Sovrin
* DIF
......@@ -50,8 +52,8 @@ A (description/specification of a) Concept MUST be [intensionally defined](https
## 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 `NewTerm` to/in that situation;
- shows the relevance of having `NewTerm` for the use-case as opposed to not having it.-->
- show how to apply ``Concept`` to/in that situation;
- shows the relevance of having ``Concept`` 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.-->
......
docs/terminology/concepts/concept-glossary.mdx → docs/terminology/concepts and terms/concept-essifLabTerminology-glossary.mdx
View file @ 63f89407
import Term from '../src/components/Term'
---
id: concept-glossary
title: Concept: Glossary
id: concept-essifLabTerminology-glossary
title: Glossary (Scope: essifLabTerminology)
---
## Scope
eSSIF-Lab Terminology
<!--REQUIRED--Short text (label, abbreviation) used to refer to the %%scope%% within which the %%concept%% is defined. The default is essifLab.-->
essifLabTerminology
## Summary
in 1-3 sentences the concept to a layperson with reaonable accuracy
## 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.-->
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 of definition
Identify a (single) scope within which the concept is to be defined. The scope you identify SHOULD have a Scope Description, or you should make one. `eSSIF-Lab` is the 'universal' scope, `Terminology` is the scope for discussions and topics related to the creation of glossaries, concept-definitions, etc.
## Short Description
<!--REQUIRED--in 1-3 sentences that describe the %%concept%% to a layperson with reasonable accuracy.-->
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). However, a glossary may also be created for the purpose of being included in other glossaries (as a construction aid to such glossaries), or for still other purposes.
* (scope identifier)
## 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?-->
A glossary may serve various purposes, the most important one of which would be to help people understand texts around a certain (set of) topic(s) in some context(s).
## Criterion
<!--This (required) section specifies the [intensional definition](https://en.wikipedia.org/wiki/Extensional_and_intensional_definitions#Intensional_definition) definition of `Glossary`, which is a specification of the necessary and sufficient conditions for when Glossary should be used. In other words: you specify a criterion that readers can use to determine whether or not something is an instance of Glossary.-->
## 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.-->
an alphabetical list of words with (short) explanations, that exists for the purpose of helping people to get a first understanding of the meaning of these words in at least one specific context.
## Examples
<!--This (optional) section contains examples, both of what satisfies the definition (and hence qualifies as an instance of Glossary), ans what does not. If you can think of examples for which the criterion may not (always) work, then describe them, too, and inform the reader why this hasn't affected the definition (yet) - e.g. because such cases are irrelevant to the scope within which the term is defined.-->
Examples include the [eSSIF-Lab Glossary](essif-lab-glossary), the [Sovrin Glossary](https://sovrin.org/library/glossary/), the [Glossary of Internet Terms](https://www.internetsociety.org/internet/glossary-internet-terms/), the glossary of the [NIST Computer Security Resource Center](https://csrc.nist.gov/glossary), and glossaries for Legal Terms, e.g. of the [US](https://www.uscourts.gov/glossary), [Singapore](https://www.supremecourt.gov.sg/services/self-help-services/glossary-of-terms), the [UK](https://www.copfs.gov.uk/involved-in-a-case/glossary-of-legal-terms).
<!--## Summary
This (optional) section summarizes the backgrounds of the chosen definition/criterion. It is the TL;DR version of the `Description` section. Apart from serving its own purposes, this section may serve the purposes that a `Description` section would have served if it hadn't been omitted.-->
<!--## Description
This (optional) section explains the backgrounds of the chosen definition/criterion. It may contain links to media (diagrams, audio, video). It SHOULD contain links to all patterns that use this concept.-->
<!--## Related Concepts from other terminologies
This (optional) section lists words/phrases that are encountered in other contexts that have the same or a sufficiently similar meaning as Glossary. In this section you may point out the (subtle) differences between Glossary and this related terminology. This helps readers better/deeper understand Glossary, and how it may be used to relate to existing texts. Ideally, such references are accompanied with links to (preferredly authoritative) sources.-->
## Related Concepts
<!--This (optional) section lists words/phrases that are encountered in other contexts that have the same or a sufficiently similar meaning as Glossary. In this section you may point out the (subtle) differences between Glossary and this related terminology. This helps readers better/deeper understand Glossary, and how it may be used to relate to existing texts. Ideally, such references are accompanied with links to (preferredly authoritative) sources.-->
- Dictionary - this is more extensive; it may include e.g. information on pronunciation, etymology, usage, example sentences,synonyms, etc. See [askdifference.com](https://www.askdifference.com/dictionary-vs-glossary/)
- Vocabulary - this is a body of words used in a particular language or field of expertise. A Glossary can (alphabetically) list such words.
<!--## 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 `Glossary` to/in that situation;
- shows the relevance of having `Glossary` 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.-->
## Notes
<!--This (optional) section is the place to put anything for which there is no other good place to put it.-->
The [eSSIF-Lab Glossary](essif-lab-glossary) contains the words that are defined within the scope of the [eSSIF-Lab framework](introduction).
<!--
---
## Footnotes
This (optional) section contains any footnotes that may have been specified in the text above.-->
## Meta
<!--This (required) section specifies attributes that are needed for generating/adapting other documents, such as glossaries, concept-files, etc.-->
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
DefScope = eSSIF-Lab <!--this is a required line, that specifies an identifier for the scope into which the term is being defined.-->
<!--Popuptext = This (optional) text specifies what is shown whenever a person hovers over a reference to this term.-->
-->
\ No newline at end of file
docs/terminology/concepts and terms/concept-essifLabTerminology-term.mdx 0 → 100644
View file @ 63f89407
import Term from '../src/components/Term'
---
id: concept-essifLabTerminology-term
title: Term (Scope: essifLabTerminology)
---
<!--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
<!--Short text (label, abbreviation) used to refer to the %%scope%% within which the %%concept%% is defined. The default is essifLab.-->
essifLabTerminology
## 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.-->
A Term is a word or phrase that is used in at least one context (and/or for specific purposes) to refer to a specific %%concept%%.
## Short Description
<!--in 1-3 sentences that describe the %%concept%% to a layperson with reasonable accuracy.-->
A Term is a word or phrase that is used in at least one context (and/or for specific purposes) to refer to a specific %%concept%%.As a concequence:
- the meaning of a Term may vary across contexts. For example, in the context of a buty-salon, the term 'nail' has a different meaning than in the context of constructing buildings.
- different terms (in different contexts) may refer to the same %%concept%% ([synonymity](https://en.wikipedia.org/wiki/Synonym)).
## 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?-->
Understanding words or phrases uttered by others requires that we are able to 'translate' them terms into terms that we habitually use. While this is mostly an automatism, and it often is not necessary to be all that precise, this may be different when they relate to stuff we find important. The ability to refer to a specific %%concept%% with a specific text or phrase, where this 'linking' is limited to a specific (or several) context(s) helps us to better interpret the intentsion of what others convey in spoken or written language.
## 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 %%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.-->
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.-->
## 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?-->
* eSSIF-Lab
* ToIP
* Sovrin
* DIF
* NIST
* ...
## Tags
<!--Add hash tags here that allow us to group concepts in useful ways.-->
* Terminology
## 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 ``Term`` to/in that situation;
- shows the relevance of having ``Term`` 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.-->
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
* 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.
---
## Footnotes
<!--This (optional) section contains any footnotes that may have been specified in the text above.-->
[^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
docs/terminology/concepts and terms/term-essiflab-purpose.mdx 0 → 100644
View file @ 63f89407
import Term from '../src/components/Term'
---
id: term-essifLab-Purpose
title: Purpose (Scope:essifLab)
---
## Scope
<!--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.
-->
docs/terminology/concepts/template-concept-file.mdx deleted 100644 → 0
View file @ f782f562
import Term from '../src/components/Term'
---
id: concept-NewConcept
title: NewConcept
---
<!--Replace 'NewConcept' with the name for the concept you want to define. Then, provide contents for the sections as you wish. You MUST provide contents for the sections 'Scope of definition', 'Short Description' and 'Criteria'-->
## Scope
eSSIF-Lab
## One-line Summary
<!--A single sentence that describe the {{concept}} to a layperson with reaonable 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
<!--in 1-3 sentences that describe the {{concept}} to a layperson with reaonable 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
<!--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 NewTerm, 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 `NewTerm` to/in that situation;
- shows the relevance of having `NewTerm` 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.-->
\ No newline at end of file
docs/terminology/glossaries/glossary-essif-lab.mdx → docs/terminology/glossaries/glossary-essiflab.mdx
View file @ 63f89407
......@@ -4,7 +4,11 @@ import Term from '../src/components/Term'
id: essif-lab-glossary
title: eSSIF-Lab Glossary
---
<!--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).-->
<!--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
<!--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.-->
......@@ -13,20 +17,25 @@ This glossary lists the basic concepts that are needed by the various stakeholde
## Sources
<!--Here, the sources should be identified from which the glossary entries (and their descriptions) are to be collected-->
### Scopes
<!--Specify the {{scope-files|scope-file}} that are to serve as a source for this glossary-->
### 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.-->
<!--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.-->
<!--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.-->
<!--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.-->
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
docs/terminology/patterns/pattern-concepts-terminology.mdx → docs/terminology/patterns/pattern-essifLabTerminology-MentalModels.mdx
View file @ 63f89407
import Term from '../src/components/Term'
---
id: pattern-concepts-terminology
title: Pattern: Concepts-Terminology
id: pattern-essifLabTerminology-MentalModels
title: Pattern: Mental Models (Scope: essifLabTerminology)
---
<!--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'-->
This pattern captures the foundational concepts and relations that we need for creating, maintaining and using vocabularies (terminologies) that groups of people can use for the specific purposes they pursue. Alternatively, we need these concepts to allow people to use 'decentralized vocabularies' that {{parties|party}} may create, maintain and use in a self-sovereign fashion - which means that each of them decides for itself what terms to use in what meaning, yet be able to communicate with other such {{parties|party}} in such a way that a correct understanding of what the other means, can more or less be guaranteed.
## 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 creating, maintaining and using vocabularies (terminologies) that groups of people can use for the specific purposes they pursue. Alternatively, we need these concepts to allow people to use 'decentralized vocabularies' that %%parties:party%% may create, maintain and use in a self-sovereign fashion - which means that each of them decides for itself what terms to use in what meaning, yet be able to communicate with other such %%parties:party%% in such a way that a correct understanding of what the other means, can more or less be guaranteed.
## 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: .
A concept is an idea that is applied to all objects in a group. It is the way people see and understand something. The name used to identify a concept (the concept's label) is a "term". For example, the word "Dog" is the term to identify the concept of what a dog is. Everything that a person knows about a dog is the concept of the term dog.
Different terms can be used to identify the same concept. Car and Automobile are synonyms for the same concept. Different languages have different terms for the same concept. This is what makes translation possible. The terms may be different in each language, but the concept is the same. The concept of jumping is the same to a person from England and a person from Italy, but one person uses the term "Jump" to mean the concept and the other person uses "Salto".
## 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:
## Footnotes
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
## Meta
<!--This (optional) section specifies attributes that are needed for generating/adapting other documents, such as glossaries, concept-files, etc.-->
[^1]:
\ No newline at end of file
Popuptext = <!--This (optional) text specifies what is shown whenever a person hovers over a reference to this term.-->
docs/terminology/patterns/pattern-essiflab-party-action.mdx 0 → 100644
View file @ 63f89407
import Term from '../src/components/Term'
---
id: pattern-essiflab-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).
<Image src=pattern-Party-action.png />
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
docs/terminology/patterns/pattern-party-action.mdx deleted 100644 → 0
View file @ f782f562
import Term from '../src/components/Term'
---
id: pattern-Party-action
title: Pattern: Party-Action
---
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
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).
<Image src=pattern-Party-action.png />
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]).
---
Footnotes:
[^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
docs/terminology/scopes/scope-essif-lab.mdx → docs/terminology/scopes/scope-essifLab.mdx
View file @ 63f89407
......@@ -5,8 +5,12 @@ id: scope-essif-lab
title: Scope: eSSIF-Lab
---
## Scope
<!--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`.-->
essifLab
## Governance
<!--This section identifies the {{organizational body|Jurisdiction}} that governs the {{scope}}. Optionally, a reference to the governance framework/procedures may be made.-->
<!--This section identifies the %%organizational body:Jurisdiction%% that governs the %%scope%%. Optionally, a reference to the governance framework/procedures may be made.-->
The [eSSIF-Lab project](https://essif-lab.eu/) governs the terminology within this scope, according to the procedures mentioned in the [eSSIF-Lab Framework](https://essif-lab.pages.grnet.gr/framework/docs/terminology/).
## Objectives/Issues
......@@ -17,13 +21,13 @@ We expect to see situations of "language confusion", i.e. in which people use wo
The Concepts and Terminology part of eSSIF-Lab aims helps eSSIF-Lab community participants understand one another at whatever level of precision they need.
## Scope identifier
<!--State a short text or abbreviation that can be used within eSSIF-Lab (or beyond) 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-->
eSSIF-Lab
## 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`-->
essifLabTerminology
## Notes
<!--Anything els that's worth mentioning.-->
......@@ -33,4 +37,9 @@ eSSIF-Lab
<!--
---
## Footnotes
This (optional) section contains any footnotes that may have been specified in the text above.-->
[//]: # This (optional) section contains any footnotes that may have been specified in the text above.
[^1]: the text for footnote [^1] goes here.
-->
docs/terminology/scopes/scope-essifLabTerminology.mdx 0 → 100644
View file @ 63f89407
import Term from '../src/components/Term'
---
id: scope-essifLabTerminology
title: Scope: eSSIF-Lab Terminology
---
## Scope
<!--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`.-->
essifLabTerminology
## Governance
<!--This section identifies the %%organizational body:Jurisdiction%% that governs the %%scope%%. Optionally, a reference to the governance framework/procedures may be made.-->
The [eSSIF-Lab project](https://essif-lab.eu/) governs the terminology within this scope, according to the procedures mentioned in the [eSSIF-Lab Framework](https://essif-lab.pages.grnet.gr/framework/docs/terminology/).
## 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.-->