Commit cd90b2a5 authored by Rieks Joosten's avatar Rieks Joosten Committed by fmerg
Browse files

making things work and rewriting some texts

parent 212ef032
---
id: terminology
title: eSSIF-Lab Concepts and Terminology
title: "eSSIF-Lab: Concepts and Terminology"
scopeid: essifLab
---
:::info **UNDER CONSTRUCTION**
*This (initial version of the) terminology chapter is currently under construction. If you feel like making a contribution, please contact [the editor](mailto:rieks.joosten@tno.nl)*
:::
The purpose of the eSSIF-Lab Terminology is to provide mental models that all of its stakeholders interpret in sufficiently the same way, so as to be able to talk, think and discuss about what it is we try to achieve and ways to achieve this.
The initial version of this terminology is still under construction.
......@@ -11,17 +16,41 @@ The initial version of this terminology is still under construction.
Contributors to and users of eSSIF-Lab come from various backgrounds. Their culture may not be Western. English may not be their native tongue. They may be experts in non-technological topics. Working with one another presumes a setting where participants have some level of shared understanding. Often, sharing one's understanding at a superficial level suffices. Other situations require that underlying concepts are shared in a more in-depth fashion. It's like cars: people buying, selling, or driving cars do not need in-depth shared knowledge about cars, whereas (maintenance or construction) engineers or liability lawyers need to share a deeper knowledge of how cars do (or do not) work.
We expect to see situations of "language confusion", i.e. in which people use words or phrases, the intension (not: intention) of which differs from the interpretation of some listeners/readers. Sometimes a casual glance at a dictionary or glossary is the solution. In other cases, deeper understanding matters, e.g. in when drafting specifications or contracts. Then [we need more than a set of definitions](https://www.sfu.ca/~swartz/definitions.htm).
This is far from trivial, and hence we expect to see situations of "language confusion", i.e. in which people use words or phrases, the intension ([not: intention](https://www.askdifference.com/intention-vs-intension/)) of which differs from the interpretation of some listeners/readers. Sometimes a casual glance at a dictionary or glossary is the solution. In other cases, deeper understanding matters, e.g. in when drafting specifications or contracts. Then [we need more than a set of definitions](https://www.sfu.ca/~swartz/definitions.htm).
This chapter reflects the learnings of eSSIf-Lab with respect to what such additional needs are, and provides the backgrounds of the methods, means and/or tools that may help to accommodate such needs. Here is a summary:
1. People that read a text may need help in understanding various words or phrases, particularly if they are not very familiar with the subject matter (they may be learning, and/or the text doesn't have an associated glossary), or come from another society. For such purposes, it helps to have an alphabetically sorted lists of words and phrases, each of which associated with one or more meanings or explanations that such words/phrases may have. We call this list a %%dictionary|dictionary%%. The eSSIF-Lab project intends to look into the possibility and necessity of generating a dictionary of SSI-related words and phrases based on the materials that are readily available; if it turns out this is beneficial, the eSSIF-Lab will contribute to the extent that is allowed by the project constraints.
2. Authors (e.g. of programming code, or articles of various kinds) that produce text on a particular topic, will want the words and phrases they use to be associated with a single meaning. This also holds for people that want to discuss a particular topic. For purposes such as these, it helps to have an alphabetically sorted lists of words and phrases, each of which associated with a single meaning or explanation that they can refer to. We call such lists %%glossaries|glossary%%. The eSSIF-Lab project intends to allow for the automated generation of such glossaries whenever a specific need for that exists.
3. People may find they need to better understand the ideas/concepts that terms refer to, e.g. because their thoughts keep running around in circles, they cannot get software to work in a generic fashion, etc. The eSSIF-Lab project intends to provide a (structured) repository where people can store texts that
- describe what we call a %%pattern|pattern%% or %%mental model|pattern%%, i.e. a coherent set of %%concepts|concepts%%, relations between these concepts, and rules/constraints that apply. A pattern also motivates its existence, and provides examples of when and how it can be used in a purposeful way;
- specify individual %%concepts|concept%% in a precise and in-depth manner, beyond what is possible by the texts used in patterns;
- specify how specific words or phrases (%%terms|term%%) are mapped onto such %%concepts|concept%% within specific scopes/contexts;
- specify a %%scope (or context)|scope%%, i.e. the extent of the area or subject matter within which we define patterns, concepts, terms and glossaries, allowing patterns to be used in a limited scope, terms to be have different meanings in different scopes, etc.
## Context
People use %%words and phrases (terms)|term%% to (tangibly) refer to the (intangible) %%ideas and thoughts (concepts)|concept%% they have, e.g. about what exists in the world, judgements they have, etc.<sup>[semantics]</sup> This mapping of terms and concepts, which we call '[semantics](wikipedia/semantics)', that is unique for each %%person or organization|party%%, enables them to reflect on their thoughts, and to convey such thoughts to others. Good communication however requires that the semantics of the communicating parties is sufficiently the same, so that the recipient of a communication will interpret it such that it means (sufficiently) the same to him as the communication means to its sender.
The Concepts and Terminology part of eSSIF-Lab aims helps eSSIF-Lab community participants understand one another at whatever level of precision they need. This chapter presents a number of aids we will develop/maintain to serve that purpose.
[semantics]: we use the term %%semantics|semantics%% to refer to the mapping between %%terms|term%% and %%concepts|concept%%. We use the term %%scope|scope%% ([OED](https://www.lexico.com/definition/scope)) to refer to the extent of the area or subject matter that a semantics is relevant and/or being used. From this definition, it seems obvious that every %%party|party%% has - and maintains - its own (subjective) semantics. The (erroneous) assumption that people (automatically) share a semantics is the cause of many misunderstandings.
## Concepts, Terminologies, Glossaries, Dictionaries, etc.
The Concepts and Terminology part of eSSIF-Lab aims helps eSSIF-Lab community participants understand one another at whatever level of precision they need.
Conveying one's thoughts is deciding which words or phrases to use for referring to the ideas or %%concepts|concept%% that one is thinking about. We will use the word %%Term%|term%% to refer to a word or phrase, that is used in some %%context (or: scope)|scope%% to refer to a specific concept. Hence, a Term can mean different things in different contexts. Examples are "localhost", or "mommy". Also, different Terms that are used in different contexts may still refer to the same concept. For example, the person referred to as "Rieks" in some contexts is known as "Mr. Joosten" in other contexts.
## Glossaries
Because of this, generally dealing with terminologies, i.e. sets of words or phrases with a presumed meaning, is a difficult topic, demonstrated e.g. by the work of Pfitzmann and Hansen who created a [terminology for talking about privacy by data minimization](https://dud.inf.tu-dresden.de/literatur/Anon_Terminology_v0.34.pdf) (2010), the development of which took over a decade, and has seen over 30 revisions.
The traditional tool for fostering common understanding is using glossaries, i.e. alphabetical lists of words relating to a specific subject, text, or dialect, with explanations; a brief dictionary ([OED](https://www.lexico.com/definition/glossary)). Examples include the [Sovrin Glossary](https://sovrin.org/library/glossary/) and the [NIST Glossary](https://csrc.nist.gov/glossary). Other initiatives attempt to provide more background, e.g. the [terminology for talking about privacy by data minimization](https://dud.inf.tu-dresden.de/literatur/Anon_Terminology_v0.34.pdf) by Pfitzmann and Hansen (2010), or the [EBSI Terminology (login required)](https://ec.europa.eu/cefdigital/wiki/display/EBP/EBSI+Terminology).
A commonly used tool for fostering common understanding are %%glossaries|glossary%%, i.e. an alphabetically sorted lists of words and phrases that relate to a specific subject (or text, dialect, ...) with explanations ([OED](https://www.lexico.com/definition/glossary)).
The eSSIF-Lab project will also develop a [Glossary](essif-lab-glossary).
Glossaries come in two basic flavors. One flavor, which we will call %%dictionary|dictionary%%, is a glossary where each term is associated with multiple meanings. An example is the [NIST Glossary](https://csrc.nist.gov/glossary). It allows people that hear or read about something to search for a meaning that is appropriate for the context of that communication.
However, since the use of such glossaries is limited to short explanations, we will also provide (a) mental model(s) that provide a more in-depth explanation of the concepts that underly the words listed in the [eSSIF-Lab Glossary](essif-lab-glossary).
The other flavor (for which we do not yet have a term to distinguish it from dictionaries), is a glossary that is about one specific topic/subject, and lists a set of terms that have a single meaning, that together form a coherent and consistent terminology, and serves one or more specific purposes regarding this topic/subject. An example is the [Sovrin Glossary](https://sovrin.org/library/glossary/). Such glossaries allow people e.g. to write code, or an article about the topic.
The eSSIF-Lab project will develop glossaries (of the second kind) as needed, and for specific purposes<sup>[1]</sup>. The idea is to just develop the specification of a glossary (specifying its purpose(s), the set of terms that are to be included, and the way in which the descriptions can be obtained), and then 'simply' generate the glossary. Doing so allows the automated generation and updating of glossaries.
[1]: Too often have we observed that people seem to think that the mere fact of having a glossary makes (many or all) terminological issues go away, and that in practice that is not the case. We seek to define glossaries only if they are demonstrably fit-for-(some)-purpose.
## Mental Models
......@@ -58,22 +87,41 @@ Basically, anything you (or anyone else) can think of qualifies. That includes p
Since there is nothing that you, or someone else, can come up with that does not satisfy the criterion, everything qualifies as an Entity. We need the term as a basis for creating intensional definitions.
### Definition
**Entity that comprises at a minimum**:
**Entity that comprises at a minimum:
- **a non-empty set of scopes in each of which specific objectives are being pursued;**
- **a criterion that specifies the necessary and sufficient conditions for being an instance of a named class;**
- **a set of arguments and/or use-cases (that SHOULD not be empty), and that show the relevance of making this distinction within the scope (and for its objectives);**
- **a name that is created and used within the scope that created the definition, for the purpose of referring to the class, or using it as a placeholder for its instances.**
- a non-empty set of scopes in each of which specific objectives are being pursued;
- a criterion that specifies the necessary and sufficient conditions for being an instance of a named class;
- a set of arguments and/or use-cases (that SHOULD not be empty), and that show the relevance of making this distinction within the scope (and for its objectives);
- a name that is created and used within the scope that created the definition, for the purpose of referring to the class, or using it as a placeholder for its instances.
**For the purposes of this document, the scope of every Definition is this Document (with its objectives that have been specified above).**
For the purposes of this document, the scope of every Definition is this Document (with its objectives that have been specified above).**
Note that this definition satisfies itself. Also note that a definition may be used in multiple scopes, where a scope that wants to use the definition that has been defined in another scope, may replace that name with one of its own choosing. This way the meaning expressed by the definition remains preserved.
### Concept
**A named set of entities that satisfy a criterion that specifies the necessary and sufficient conditions for being a member of that set**
### Relation
**A named set of entity-pairs (L,R), and a criterion C(SRC,TGT), where
- SRC and TGT are Concepts;
- L is an element of SRC and R is an element of TGT;
- the name of the relation combined with SRC and TGT identifies the set;
- C(L,R) is satisfied.**
For example, a relation could be defined by:
- name=‘is owner of’
- SRC=’Party’ and TGT=’Entity’ and
- C(SRC,TGT)=‘SRC is the owner of TGT’
This relation contains all pairs (X,Y) for which Party X is the owner of Y. The set of entity-pairs (L,R) is called the extension of the relation. The criterion C(L,R) is also referred to as the intension of the relation (as, together with this definition, it intensionally defines the relation)
### Rule (or Constraint)
**A Relation the intension of which consists of pairs that do not satisfy a specified expression that consists of concept (elements) and relations, and that can logically be evaluated.**
### Pattern
**A coherent set of Concepts, Relations between these Concepts, and Rules that are expressed in terms of these Concepts and Relations.**
** A coherent set of Concepts, Relations between these Concepts, and Rules that are expressed in terms of these Concepts and Relations.**
We need Patterns as a mechanism for ‘chopping up’ mental models, in order to accommodate for the human disability to consciously oversee and think about more than 7 +/- 2 Concepts (including attributes, Relations, and Rules).
Patterns may be associated with texts e.g. for motivating its existence, explaining its purpose, etc.
......@@ -85,9 +133,9 @@ Also, we capitalize words in mid-sentence whenever it is used in the meaning as
Patterns will be visualized in this document using a UML-like notation, as follows:
- a **rectangle** represents a (named) concept. Concepts serve as entity-classes. Their (operational) extensions, i.e. the respective sets of (runtime) instances, are disjunct.
- a **solid line with a closed arrowhead** represent a (named) relation/association between the two concepts it connects. The concept at the arrowhead is called the ‘target concept’ (TGT) for that relation. The concept at the other end is called the ‘source concept’ (SRC) for that relation. Names are chosen such that `<SRC> <relation name> <TGT>` is a phrase that suggests the intension(al definition) of that relation.
- a **dashed line** signifies that its intension is created by combination the intensions of other relations (it is a ‘shorthand’ for a path of other relations).
- an **open-ended arrow** is an ‘ISA’ relation, which can be read as `<SRC> ISA <TGT>`. It means that SRC is a specialization of TGT (which is a generalization of SRC). Thus, SRC must satisfy all constraints that TGT must satisfy, and has all attributes (including properties) that TGT has.
- **Multiplicities** use the [n..m] notation. When a multiplicity is omitted, [0..n] is intended.
- A **concept that is coloured red(dish)** represents a notion that is commonly used ‘in the wild’ (and hence needs not be defined here), relates to one or more concepts we need for the pattern, yet is not the same. We include such ‘red concepts’ to help readers identify and subsequently bridge gaps between commonly held thoughts and the (sometimes subtly) different meanings we need in our model.
- a rectangle represents a (named) concept. Concepts serve as entity-classes. Their (operational) extensions, i.e. the respective sets of (runtime) instances, are disjunct.
- a solid line with a closed arrowhead represent a (named) relation/association between the two concepts it connects. The concept at the arrowhead is called the ‘target concept’ (TGT) for that relation. The concept at the other end is called the ‘source concept’ (SRC) for that relation. Names are chosen such that `<SRC> <relation name> <TGT>` is a phrase that suggests the intension(al definition) of that relation.
- a dashed line signifies that its intension is created by combination the intensions of other relations (it is a ‘shorthand’ for a path of other relations).
- an open-ended arrow is an ‘ISA’ relation, which can be read as `<SRC> ISA <TGT>`. It means that SRC is a specialization of TGT (which is a generalization of SRC). Thus, SRC must satisfy all constraints that TGT must satisfy, and has all attributes (including properties) that TGT has.
- Multiplicities use the [n..m] notation. When a multiplicity is omitted, [0..n] is intended.
- A concept that is coloured red(dish) represents a notion that is commonly used ‘in the wild’ (and hence needs not be defined here), relates to one or more concepts we need for the pattern, yet is not the same. We include such ‘red concepts’ to help readers identify and subsequently bridge gaps between commonly held thoughts and the (sometimes subtly) different meanings we need in our model.
......@@ -8,14 +8,14 @@ This document states the requirements for files in this directory, such that the
## Filenames
All file MUST have the structure: `<termid>.mdx`, where <termid> is the (all lowercase) identifier of a term (including the term that is used when defining a concept). They MUST be a lowercase identifier that only uses charancters `a`-`z` and `-`.
All file MUST have the structure: `<termid>.mdx`, where `<termid>` is the (all lowercase) identifier of a term (including the term that is used when defining a concept). They MUST be a lowercase identifier that only uses charancters `a`-`z` and `-`.
## Templates
The `terms/templates` directory contains templates for each of the <type>s. A template file has comments that hold, amongst others, requirements for the contents of instances of that template.
The `terms/templates` directory contains templates for each of the `<type>`s. 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
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
- `<sometext>` is a text that will be displayed as if it were a term
---
id: essifLab-concept-actor
title: Concept: Actor (Scope: eSSIF-Lab)
title: "Concept: Actor (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: actor
hoverText: "Entity that can act (do things), e.g. people, machines, but not organizations."
......
---
id: essifLab-concept-agent
title: Concept: Agent (Scope: eSSIF-Lab)
title: "Concept: Agent (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: agent
hoverText: "Agent (of a Party): Actor that is currently working on behalf of a Party."
......
---
id: essifLab-concept-jurisdiction
title: Concept: Jurisdiction (Scope: eSSIF-Lab)
title: "Concept: Jurisdiction (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: jurisdiction
hoverText: "<Text that pops up when the user hovers over a reference to this concept>"
......
---
id: essifLab-concept-objective
title: Concept: Objective (Scope: eSSIF-Lab)
title: "Concept: Objective (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: objective
hoverText: "Something toward which effort is directed: an aim, goal, or end of action"
......
---
id: essifLab-concept-organization
title: Concept: Organization (Scope: eSSIF-Lab)
title: "Concept: Organization (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: organization
hoverText: "popuptext for Organization tbd"
......
---
id: essifLab-concept-owner
title: Concept: Owner (Scope: eSSIF-Lab)
title: "Concept: Owner (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: owner
hoverText: "a Party that has the legal or rightful title to control something."
......
---
id: essiflab-concept-party
title: Party (Scope essifLab)
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."
---
## Criterion:
......
---
id: essifLab-concept-trd
title: Concept: TRD - Transaction Result Dispatcher (Scope: eSSIF-Lab)
title: "Concept: TRD - Transaction Result Dispatcher (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: trd
hoverText: "<Text that pops up when the user hovers over a reference to this concept>"
......
---
id: essifLab-concept-tve
title: Concept: TVE - Transaction Validation Engine (Scope: eSSIF-Lab)
title: "Concept: TVE - Transaction Validation Engine (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: tve
hoverText: "<Text that pops up when the user hovers over a reference to this concept>"
......
---
id: essifLab-pattern-jurisdictions
title: Pattern: Jurisdictions (Scope: eSSIF-Lab)
title: "Pattern: Jurisdictions (Scope: eSSIF-Lab)"
scopeid: essifLab
patternid: jurisdictions
hoverText: "<Text that pops up when the user hovers over a reference to this pattern>"
......
---
id: essifLab-pattern-party-action
title: Pattern: Party-Action (Scope: eSSIF-Lab)
title: "Pattern: Party-Action (Scope: eSSIF-Lab)"
scopeid: essifLab
patternid: party-action
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."
......@@ -14,7 +14,7 @@ This pattern captures the foundational concepts and relations that we need for t
<!--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|party%%’s %%Knowledge|knowledge%% as the (authoritative) guidance for executing the %%Actions|Action%% (as well as any other relevant %%Knowledge|knowledge%% they can access).
<Image src=pattern-Party-action.png />
`<image src=pattern-Party-action.png />`
The essential characteristic of %%Parties|Party%% is their 1-1 link with %%Knowledge|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|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.
......
---
id: scope-essif-lab
title: Scope eSSIF-Lab
id: essifLab-scope
title: "Scope: eSSIF-Lab"
scopeid: essifLab
hoverText: "<essifLab-scope hovertext>"
---
## Governance
......
---
id: essifLab-term-peer-agent
title: Term: Peer Agent (Scope: eSSIF-Lab)
title: "Term: Peer Agent (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: peer-agent
conceptref: essifLab:Agent
......
---
id: essifLab-term-peer-party
title: Term: Peer Party (Scope: eSSIF-Lab)
title: "Term: Peer Party (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: peer-party
conceptref: essifLab:party
......
---
id: essifLab-term-peer-agent
title: Term: Peer Agent (Scope: eSSIF-Lab)
title: "Term: Peer Agent (Scope: eSSIF-Lab)"
scopeid: essifLab
termid: peer-agent
conceptref: essifLab:Agent
......
---
id: essiflabterminology-concept-concept
title: Concept (Scope essifLabTerminology)
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."
---
## Short Description
......
---
id: essiflabterminology-concept-glossary
title: Glossary (Scope essifLabTerminology)
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)."
---
## Short Description
......
---
id: essiflabterminology-concept-term
title: Term (Scope essifLabTerminology)
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."
---
## Short Description
......
---
id: essiflabterminology-pattern-MentalModels
title: Pattern Mental Models (Scope essifLabTerminology)
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."
---
## Purpose
......
---
id: <ExistingScopeID>-concept-<NewTermID>
title: Concept: <New Term> (Scope: <Existing Scope>)
id: ExistingScopeID-concept-NewTermID
title: "Concept: <New Term> (Scope: <Existing Scope>)"
scopeid: <ExistingScopeID>
termid: <NewTermID>
hoverText: "<Text that pops up when the user hovers over a reference to this concept>"
......
---
id: <ExistingScopeID>-term-<NewTermID>
title: Term: <New Term> (Scope: <Existing Scope>)
id: ExistingScopeID-term-NewTermID
title: "Term: <New Term> (Scope: <Existing Scope>)"
scopeid: <ExistingScopeID>
termid: <NewTermID>
conceptref: <ExistingConceptScopeID>:<ExistingTermID>
......
---
id: <ExistingScopeID>-concept-<NewTermID>
title: Concept: <New Term> (Scope: <Existing Scope>)
id: ExistingScopeID-concept-NewTermID
title: "Concept: <New Term> (Scope: <Existing Scope>)"
scopeid: <ExistingScopeID>
termid: <NewTermID>
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>)
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>"
---
<!--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:
......
---
id: <ExistingScopeID>-dictionary
id: ExistingScopeID-dictionary
title: Dictionary for <ExistingScopeID>
scopeid: <ExistingScopeID>
hoverText: "<Text that pops up when the user hovers over a reference to this Dictionary>"
......
---
id: <ExistingScopeID>-glossary-<NewGlossaryID>
title: Glossary: <NewGlossary> (Scope: <Existing Scope>)
id: ExistingScopeID-glossary-NewGlossaryID
title: "Glossary: <NewGlossary> (Scope: <Existing Scope>)"
scopeid: <ExistingScopeID>
glossaryid: <NewGlossaryID>
hoverText: "<Text that pops up when the user hovers over a reference to this glossary>"
......
---
id: <ExistingScopeID>-pattern-<NewPatternID>
title: Pattern: <New Pattern> (Scope: <Existing Scope>)
id: ExistingScopeID-pattern-NewPatternID
title: "Pattern: <New Pattern> (Scope: <Existing Scope>)"
scopeid: <ExistingScopeID>
patternid: <NewPatternID>
hoverText: "<Text that pops up when the user hovers over a reference to this pattern>"
......
---
id: <NewScopeID>-1-scope
title: Scope: <New Scope>
id: NewScopeID-1-scope
title: "Scope: <New Scope>"
scopeid: <NewScopeID>
hoverText: "<Text that pops up when the user hovers over a reference to this item>"
---
......
---
id: <ExistingScopeID>-term-<NewTermID>
title: Term: <New Term> (Scope: <Existing Scope>)
id: ExistingScopeID-term-NewTermID
title: "Term: <New Term> (Scope: <Existing Scope>)"
scopeid: <ExistingScopeID>
termid: <NewTermID>
conceptref: <ExistingConceptScopeID>:<ExistingTermID>
......
---
id: terminology
title: eSSIF-Lab Concepts and Terminology
title: "eSSIF-Lab: Concepts and Terminology"
---
The purpose of the eSSIF-Lab Terminology is to provide mental models that all of its stakeholders interpret in sufficiently the same way, so as to be able to talk, think and discuss about what it is we try to achieve and ways to achieve this.
......
---
id: terminology
title: eSSIF-Lab Concepts and Terminology
scopid: essifLab
title: "eSSIF-Lab: Concepts and Terminology"
scopeid: essifLab
---
The purpose of the eSSIF-Lab Terminology is to provide mental models that all of its stakeholders interpret in sufficiently the same way, so as to be able to talk, think and discuss about what it is we try to achieve and ways to achieve this.
:::info
*The terminology chapter is currently under construction. If you feel like making a contribution, please contact [the editor](mailto:rieks.joosten@tno.nl)*
:::info **UNDER CONSTRUCTION**
*This (initial version of the) terminology chapter is currently under construction. If you feel like making a contribution, please contact [the editor](mailto:rieks.joosten@tno.nl)*
:::
The purpose of the eSSIF-Lab Terminology is to provide mental models that all of its stakeholders interpret in sufficiently the same way, so as to be able to talk, think and discuss about what it is we try to achieve and ways to achieve this.
## Introduction
Contributors to and users of eSSIF-Lab come from various backgrounds. Their culture may not be Western. English may not be their native tongue. They may be experts in non-technological topics. Working with one another presumes a setting where participants have some level of shared understanding. Often, sharing one's understanding at a superficial level suffices. Other situations require that underlying concepts are shared in a more in-depth fashion. It's like cars: people buying, selling, or driving cars do not need in-depth shared knowledge about cars, whereas (maintenance or construction) engineers or liability lawyers need to share a deeper knowledge of how cars do (or do not) work.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment