Commit 1def61a3 authored by Rieks Joosten's avatar Rieks Joosten
Browse files

terminology updates

parent 129f0fc6
Pipeline #15812 passed with stage
in 1 minute and 30 seconds
......@@ -14,13 +14,15 @@ A word in mid-sentence that is capitalized is a %%term|term%% that has a %%defin
:::note
We are working towards deprecating this convention, as we now have better ways of referring to words that are defined in the eSSIF-Lab Corpus..
:::
### Pattern diagram notations
%%Pattern|pattern%% diagrams 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 **solid line with a closed arrowhead** represent a (named) relation/association between the two concepts it connects. We may refer to the concept at the arrowhead as the ‘target concept’ (TGT) for that relation. Similarly, the concept at the other end will be referred to as 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 **green name** at either end of a relation/association is what UML calls 'role'; this name may be used to refer to (an instance of) the concept at which the name is placed as it performs its/this role in this 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.
......
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: concept
typeid: action
stage: draft
hoverText: "Action: something that is actually done/executed by a single actor (as a single operation) for some party within a specific context."
hoverText: "Action: something that is actually done/executed by a single Actor (as a single operation) for some Party within a specific context."
---
### Short Description
......@@ -26,4 +26,4 @@ An **Action** is something that is done by an actor, can be considered a single
- OED defines Action as the fact or process of doing something, typically to achieve an aim ([OED](https://www.lexico.com/definition/action)), which is too generic for our purposes.
### Background
The %%party-action pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
\ No newline at end of file
The %%Parties, Actors and Actions pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
\ No newline at end of file
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: concept
typeid: actor
stage: draft
hoverText: "Actor: Entity that can act (do things), e.g. people, machines, but not organizations."
hoverText: "Actor: Entity that can act (do things), e.g. people, machines, but not Organizations."
---
### Short Description
......@@ -25,4 +25,4 @@ Entity that is capable of actually executing %%actions|action%% (acting, doing t
- Enterprises, governments, and other %%organizations|organization%% do not qualify.
### Background
The %%party-action pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
The %%Parties, Actors and Actions pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
......@@ -5,11 +5,11 @@ scopeid: essifLab
type: concept
typeid: agent
stage: draft
hoverText: "Agent: An actor that is (at that point in time) executing an action for, or on behalf of a Party (the Principal of that actor)."
hoverText: "Agent (of a Party): an Actor that is (at that point in time) executing an Action for, or on behalf of a Party (the Principal of that Actor)."
---
### Short Description
%%Actors|actor%% execute %%actions|action%% for, or on behalf of some %%party|party%% (the %%principal|principal%% of that agent), because parties are not considered to be capable of acting.[^1] Agents must act in accordance with their %%principal|principal%%, which means that for every kind of action, the principal must provide the proper guidance for their agents, e.g. in terms of policies (rules), working instructions, programs etc. We use the term %%digital agent|digital-agent%% to refer to agents that operate in a digital domain.
%%Actors|actor%% execute %%actions|action%% for, or on behalf of some %%party|party%% (the %%principal|principal%% of that agent), because parties are not considered to be capable of acting. Agents must act in accordance with their %%principal|principal%%, which means that for every kind of action, the principal must provide the proper guidance for their agents, e.g. in terms of policies (rules), working instructions, programs etc. We use the term %%digital agent|digital-agent%% to refer to agents that operate in a digital domain.
### Purpose
The ability to distinguish between (non)agents is relevant in many situations, including:
......@@ -29,4 +29,4 @@ a property that is attributed to an %%Actor|actor%% whenever it is executing an
- A wallet app that runs on a phone and that is exclusively used by a single person acts as a (digital) Agent for that person.
### Background
The %%party-action pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
The %%Parties, Actors and Actions pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: concept
typeid: colleague
stage: draft
hoverText: "Colleague (of an Agent): An actor that is an Agent for the same Principal."
hoverText: "Colleague (of an Agent): any other Agent that has the same Principal (i.e. Party on whose behalf they exeucte Actions)."
---
:::info Editor's note
......
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: concept
typeid: concept-file
stage: draft
hoverText: "Concept-file: a file that defines/specifies a concept."
hoverText: "Concept-file: a file that defines/specifies a Concept."
---
### Short Description
......
......@@ -5,7 +5,7 @@ scopeid: essifLabTerminology
type: concept
typeid: corpus
stage: draft
hoverText: "Corpus (of Terminology): the documentation that describes the knowledge around a set of terms and concepts."
hoverText: "Corpus (of Terminology): the documentation that describes the Knowledge around a set of Terms and Concepts."
---
:::info Editor's note
......
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: concept
typeid: credential
stage: draft
hoverText: "Credential: data, representing a set of statements made by one party (the author of the credential)."
hoverText: "Credential: data, representing a set of statements made by one Party (the author of the credential)."
---
:::info Editor's note
......
......@@ -5,7 +5,7 @@ scopeid: essifLabTerminology
type: concept
typeid: definition
stage: draft
hoverText: "Definition: A Definition is a text that helps parties truely understand the meaning of a term."
hoverText: "Definition: a text that helps Parties deeply/truly understand the meaning of a Term."
---
### Short Description
......
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: dictionary
typeid: dictionary-file
stage: draft
hoverText: "Dictionary-file: a file that specifies the contents of a dictionary."
hoverText: "Dictionary-file: a file that specifies the contents of a Dictionary."
---
### Short Description
......
......@@ -5,7 +5,7 @@ scopeid: essifLabTerminology
type: concept
typeid: dictionary
stage: draft
hoverText: "Dictionary: an alphabetically sorted list of terms and explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
hoverText: "Dictionary: an alphabetically sorted list of Terms and explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
---
### Short Description
......
......@@ -6,7 +6,7 @@ type: term
typeid: digital-actor
conceptref: ":Actor"
stage: draft
hoverText: "Digital Actor: an actor in the digital world (e.g. a running app, or a web-server)."
hoverText: "Digital Actor: an Actor in the digital world (e.g. a running app, or a web-server)."
---
### Purpose
......
......@@ -6,11 +6,10 @@ type: term
typeid: digital-agent
conceptref: ":Agent"
stage: draft
hoverText: "Digital Agent: an actor in the digital world (e.g. a running app, or a web-server) that executes actions for a specific party (the Principal of the digital agent)."
hoverText: "Digital Agent: an Actor in the digital world (e.g. a running app, or a web-server) that is executing an Action for a specific Party (its Principal)."
---
### Purpose
<!--State the purpose(s) for which it is necessary (or at least: desirable) to define <New Term>.-->
The ability to distinguish between (non)digital agents allows us to exclusively talk about software/hardware agents.
See also: %%agent|agent%%.
\ No newline at end of file
......@@ -6,11 +6,10 @@ type: term
typeid: digital-colleague
conceptref: ":Colleague"
stage: draft
hoverText: "Digital Colleague (of an Agent): a digital actor that is an agent of the same principal."
hoverText: "Digital Colleague (of an Agent): any (other) Digital Agent that has the same Principal (i.e. Party on whose behalf they exeucte Actions)."
---
### Purpose
<!--State the purpose(s) for which it is necessary (or at least: desirable) to define <New Term>.-->
The ability to distinguish between (non)digital colleagues allows us to reason and communicate about the set of %%digital actors|digital-actor%% that are %%agents|agent%% for a single **principal|principal%%.
See also: %%colleague|colleague%%.
......@@ -6,7 +6,7 @@ type: concept
typeid: digital-policy
conceptref: ":Policy"
stage: draft
hoverText: "Digital Policy: a machine-readable document that contains rules, working instructions or other guidance for digital agents so as to enable them to execute actions on behalf of the author of that policy."
hoverText: "Digital Policy: a machine-readable Policy (i.e. document that contains rules, working instructions or other guidance for Agents that can interpret such documents, so as to enable them to execute Actions on behalf of the Policy's author)."
---
### Short Description
......
---
id: employee
title: "Employee"
scopeid: essifLab
type: concept
typeid: employee
stage: draft
hoverText: "Employee (of a Party): an Actor for whom/which it is realistic that it might execute Actions on behalf of that Party."
---
:::info Editor's note
TNO to provide the content of this file.
:::
### Background
The %%Parties, Actors and Actions pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
### Related Concepts
---
id: employer
title: "Employer"
scopeid: essifLab
type: concept
typeid: employer
stage: draft
hoverText: "Employer (of an Actor): a Party on whose behalf this Actor might execute Ations."
---
:::info Editor's note
TNO to provide the content of this file.
:::
### Background
The %%Parties, Actors and Actions pattern|pattern-party-actor-action%% provides an overview of how this concept fits in with related concepts.
### Related Concepts
......@@ -5,7 +5,7 @@ scopeid: essifLab
type: glossary
typeid: glossary-file
stage: draft
hoverText: "Glossary-file: a file that defines/specifies a glossary."
hoverText: "Glossary-file: a file that defines/specifies a Glossary."
---
### Short Description
......
......@@ -5,12 +5,12 @@ scopeid: essifLabTerminology
type: concept
typeid: glossary
stage: draft
hoverText: "Glossary: an alphabetically sorted list of terms explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
hoverText: "Glossary: an alphabetically sorted list of Terms with explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s)."
---
### Short Description
<!--REQUIRED--in 1-3 sentences that describe the concept to a layperson with reasonable accuracy.-->
A glossary is an alphabetically sorted list of terms and explanations, usually aimed to help people understand texts around a certain (set of) topic(s) in some context(s). 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.
A **glossary** is an alphabetically sorted list of %%terms|term%% with 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.
### 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 conceptevant within its scope of definition?-->
......@@ -18,7 +18,7 @@ A glossary may serve various purposes, the most important one of which would be
### 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.-->
an alphabetical list of words or phrases with (short) explanations, that exists for the purpose of helping people to get a first understanding of the meaning of each word in the scope/context for which the glossary is created.
A **glossary** is an alphabetical list of words or phrases with (short) explanations, that exists for the purpose of helping people to get a first understanding of the meaning of each word in the scope/context for which the glossary is created.
### 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.-->
......
---
id: holder-policy
title: "Holder Policy"
scopeid: essifLab
type: concept
typeid: holder-policy
stage: draft
hoverText: "Holder Policy: a Digital Policy that enables an operational Holder component to function according to the rules of its Policy Governor."
---
:::info Editor's note
TNO to provide the content of this file.
:::
### Related Concepts
- %%Digital Policy|digital-policy%%
- %%Policy Governor|policy-governor%%
- %%Holder|holder%%
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