essiflab-1-scope.mdx 2.99 KB
Newer Older
1
2
3
4
5
6
7
import Term from '../src/components/Term'

---
id: scope-essif-lab
title: Scope: eSSIF-Lab
---

8
## Scope
Rieks Joosten's avatar
Rieks Joosten committed
9
<!-- *REQUIRED* Short text (label, abbreviation) that can be used to refer to the scope. Scope identifiers/labels should be useable as prefix for terms, thus providing a mechanism to refer to terms defined in other scopes, and therefore should consist of lower-case characters [a-z0-9], preferably without `-` or `_` characters. For eSSIF-Lab, we use `essifLab`.-->
10
11
essifLab

12
## Governance
13
<!--This section identifies the %%organizational body:Jurisdiction%% that governs the %%scope%%. Optionally, a reference to the governance framework/procedures may be made.-->
14
15
16
17
18
19
20
21
22
23
24
25
26
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.-->
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.

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 URI
<!--Optionally specify the URI by which this scope may be identified-->

27
28
29
30
## 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

31
32
33
34
35
36
37
38
39
## Notes
<!--Anything els that's worth mentioning.-->

## Tags
<!--Add hash tags here that allow us to group concepts in useful ways.-->

<!--
---
## Footnotes
40
41
42
43
44
45

[//]: # This (optional) section contains any footnotes that may have been specified in the text above.

[^1]: the text for footnote [^1] goes here.

-->