27 lines
863 B
ReStructuredText
27 lines
863 B
ReStructuredText
|
.. need to design a way to bring in multiple glossary data sources
|
||
|
|
so that we can use the global shared glossary + our project
|
||
|
|
specific glossary
|
||
|
|
|
||
|
|
#########
|
||
|
|
Glossary
|
||
|
|
#########
|
||
|
|
|
||
|
|
Glossary
|
||
|
|
|
||
|
|
.. glossary::
|
||
|
|
|
||
|
|
Document
|
||
|
|
A written collection of information, instructions, drawings,
|
||
|
|
specifications, etc. that is *maintained* throughout the
|
||
|
|
design/operation/decommissioning of the facility. Differs from a
|
||
|
|
*record* in that it is expected to be *maintained* by revisions as
|
||
|
|
needed. See :need:`R_APPB_45`
|
||
|
|
|
||
|
|
Record
|
||
|
|
A written collection of information providing evidence of
|
||
|
|
work that was done at a specific time. Records are expected
|
||
|
|
to be *retained* for a certain retention period, e.g.
|
||
|
|
for the lifetime of the plant or for a given number of years.
|
||
|
|
See :need:`R_APPB_79`
|
||
|
|
|
||
|
|
|