template-scope-file.mdx 1.71 KB
Newer Older
1
2
3
import Term from '../src/components/Term'

---
Rieks Joosten's avatar
Rieks Joosten committed
4
5
id: scope-<NewScope>
title: Scope: <NewScope>
6
7
8
9
---
<!--A %%scope%% is something within which %%concepts:concept%% can be associated with %%terms:term%%, thereby creating a vocabulary that can be used to meaningfully express ideas, arguments, etc.-->

## Scope
Rieks Joosten's avatar
Rieks Joosten committed
10
<!-- *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`.-->
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

## Governance
<!--This section identifies the %%organizational body:Jurisdiction%% that governs the %%scope%%. Optionally, a reference to the governance framework/procedures may be made.-->

## Objectives/Issues
<!--State the purpose for having the scope in terms of objectives that are aimed for and/or issues that are to be addressed.-->

## Scope URI
<!--Optionally specify the URI by which this scope may be identified-->

## Inclusions
<!--This %%scope%% may include other scopes, which means that everything in that other scope is also considered part of this %%scope%%. In case of collisions, this %%scope%% MUST provide a means to resolve such conflicts without modifying anything in included scopes. For eSSIF-Lab, we include `essifLabTerminology`-->

## Notes
<!--Anything els that's worth mentioning.-->

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

<!--
---
## Footnotes

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

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

-->