-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
#577 put conclusion of issue in ADR-012
- Loading branch information
1 parent
9744c38
commit 874fce9
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
23 changes: 23 additions & 0 deletions
23
documentation/decisions/012-explanation-and-refs-in-glossary.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# 012: Define and Explain Terms AND Give References in Glossary | ||
|
||
## Status: Accepted | ||
|
||
## Context | ||
|
||
In [issue 577](https://github.com/isaqb-org/curriculum-foundation/issues/577) we discussed our usage of the _Glossary_ as a means to define or explain terms. | ||
|
||
We decided to: | ||
|
||
1. give a understandable ("good") explanation in the glossary | ||
2. add (maybe historical) references also in the glossary | ||
|
||
|
||
## Rationale: | ||
|
||
The list of references in the curriculum shall not become overly long - and shall contain current and easily-accessible references. | ||
Historical references are better suited for the glosssary. | ||
|
||
## Consequences: | ||
|
||
See the context - there is a lot of work to be done for defining terms. | ||
|