-
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.
Browse files
Browse the repository at this point in the history
#577 glossary contains references
- Loading branch information
Showing
2 changed files
with
26 additions
and
1 deletion.
There are no files selected for viewing
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
25 changes: 25 additions & 0 deletions
25
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,25 @@ | ||
# 012: Define and Explain Terms in Glossary 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. | ||
|
||
## Decision | ||
|
||
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. | ||
|