-
Notifications
You must be signed in to change notification settings - Fork 61
Add What is a Glossary? explanation #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
bruce-esrig
wants to merge
26
commits into
canonical:main
Choose a base branch
from
bruce-esrig:gloss-explain
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
9dc677d
Add draft explanation What is a Glossary?
bruce-esrig 2a2b0d7
Corrected errors ... note that there's no glossary (yet?), so the ter…
bruce-esrig 91eca0f
Merge branch 'canonical:main' into gloss-explain
bruce-esrig d08fbc5
Caught up w oda/main. Fixed typo in links for authors. Updated custom…
bruce-esrig cecd913
Added mini-glossaries. Removed some excess headings.
bruce-esrig 2e93826
Deleting another two excess headings.
bruce-esrig 4ce203b
Add appendices for mechanics and locally-defined terms. rST and MyST …
bruce-esrig 73d27c3
Merge branch 'canonical:main' into gloss-explain
bruce-esrig e986bac
Update website/docs/explanation/glossary_what.md
bruce-esrig 79c5382
Update website/docs/explanation/glossary_what.md
bruce-esrig f9c4ded
Update website/docs/explanation/glossary_what.md
bruce-esrig 5d08c72
Update website/docs/explanation/glossary_what.md
bruce-esrig 0b7f809
Update website/docs/explanation/glossary_what.md
bruce-esrig dc1494c
Update website/docs/explanation/glossary_what.md
bruce-esrig d197584
Update website/docs/explanation/glossary_what.md
bruce-esrig 26dbeaf
Update website/docs/explanation/glossary_what.md
bruce-esrig 6d67e4b
Update website/docs/explanation/glossary_what.md
bruce-esrig fbaecec
Update website/docs/explanation/glossary_what.md
bruce-esrig 6f650a3
Update website/docs/explanation/glossary_what.md
bruce-esrig 2d726e5
Update website/docs/explanation/glossary_what.md
bruce-esrig 9af28da
Update website/docs/explanation/glossary_what.md
bruce-esrig d7ecba1
Use 4-space indentation for quoted markup. Explain glossary entry < d…
bruce-esrig f913bce
Merge branch 'canonical:main' into gloss-explain
bruce-esrig 0ab2e44
Merge branch 'main' into gloss-explain
s-makin e850bcb
Merge branch 'canonical:main' into gloss-explain
bruce-esrig 578cc1b
Merge branch 'canonical:main' into gloss-explain
bruce-esrig File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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,130 @@ | ||
# What is a glossary? | ||
|
||
A *glossary* gives the meanings of *terms* in a work or domain. | ||
It is presented as a list of terms in alphabetic order, each with a *gloss* that explains the term. | ||
|
||
Each explanation gives the reader enough understanding to become familiar, and perhaps even comfortable, with the term. | ||
|
||
Simplicity is prized. A glossary entry should aim to make the reader one step more comfortable with the term. | ||
|
||
## Structure | ||
|
||
### Definition | ||
|
||
A definition is a statement of fact that conveys the meaning of a term. | ||
A definition that consists of a simple phrase or sentence may be all the explanation that is needed. For example: | ||
|
||
```{glossary} | ||
core | ||
The working memory of a computer. | ||
``` | ||
|
||
### Abbreviation | ||
|
||
If the term is an abbreviation, the gloss starts with the expanded form of the term. The abbreviation is explained briefly after this expansion. For example: | ||
|
||
```{glossary} | ||
DNS | ||
**Domain Name System**. A system that translates human-readable domain names (canonical.com) to their IP addresses (185.125.190.20). | ||
``` | ||
|
||
In a conversational style, the definition has more of the structure and tone of a spoken sentence. | ||
For example, the definition may begin by repeating the term being defined. | ||
|
||
```{glossary} | ||
FC | ||
**Fiber Channel** is a storage networking protocol used for low-latency communication between a storage device and a node | ||
in a Storage Area Network (SAN). | ||
``` | ||
|
||
In this definition of FC, the abbreviation SAN is preceded by its expansion as is customary in running text. | ||
This is a good way to handle abbreviations that may be unfamiliar or have not yet been formally defined. | ||
|
||
### Cross-references | ||
|
||
Cross-references help readers navigate among related terms. | ||
|
||
If the gloss for a term discusses a second term, the second term should be linked. | ||
|
||
<!-- {term}`DNS` replaced by *DNS* --> | ||
<!-- other terms: LDAP, SSL, TLS, DTLS --> | ||
|
||
|
||
```{glossary} | ||
DDNS | ||
**Domain Name System**. | ||
A service that automatically updates {term}`DNS` records when the underlying IP address changes (aka, dynamic IP). | ||
``` | ||
|
||
When a concept that provides depth or broader context is used in a gloss, it can be linked using "See". | ||
|
||
```{glossary} | ||
DIT | ||
**Directory Information Tree**. In directory services (See {term}`LDAP`), a hierarchical tree-like structure used to organize and store information. | ||
``` | ||
|
||
A collection of related topics can be provided at the end of the gloss. These could link elsewhere in the documentation, or to external resources. | ||
|
||
```{glossary} | ||
GnuTLS | ||
**GNU’s Not Unix Transport Layer Security**. | ||
A GNU software package that secures data in transit by implementing the | ||
{term}`SSL`, {term}`TLS`, and {term}`DTLS` protocols. | ||
|
||
Related topic(s): [GnuTLS (Ubuntu Server documentation)](https://documentation.ubuntu.com/server/explanation/crypto/gnutls/#), | ||
[GnuTLS (official site)](https://www.gnutls.org/), | ||
Cryptography, Web services, OpenLDAP. | ||
|
||
``` | ||
|
||
## Dictionary features | ||
|
||
Glossary entries tend to be simpler than full dictionary entries. Some glossary entries, however, may include dictionary features such as the origin of a term, or the pronunciation, or an alternate form, or some other specialized aspect of the term that is of great interest. | ||
|
||
## Appendix 1: Mechanics | ||
|
||
This document is written in Markedly Structured Text | ||
([MyST](https://myst-parser.readthedocs.io/en/latest/syntax/typography.html#syntax-glossaries)). | ||
|
||
Glossaries can also be produced using [reStructured Text (rST)](https://sublime-and-sphinx-guide.readthedocs.io/en/latest/glossary.html). | ||
|
||
A reference to a term is coded as follows: | ||
|
||
`{term}`referenced_term | ||
|
||
A complex glossary entry is coded as follows ("..." indicates omitted characters): | ||
|
||
```{glossary} | ||
GnuTLS_example | ||
**GNU’s Not Unix Transport Layer Security**. | ||
A GNU software package that secures data in transit by implementing the | ||
{term}`SSL`, {term}`TLS`, and {term}`DTLS` protocols. | ||
|
||
Related topic(s): [GnuTLS (Ubuntu Server doc...)](https://doc.../gnutls/#), | ||
[GnuTLS (official site)](https://www.gnutls.org/), | ||
Cryptography, Web services, OpenLDAP. | ||
``` | ||
|
||
## Appendix 2: Locally-defined terms | ||
|
||
These terms are referenced within the topic to illustrate cross-references. | ||
|
||
```{glossary} | ||
datagram | ||
In networking, a self-contained, independent packet sent over a network. | ||
A datagram can be routed from source to destination without relying on earlier or subsequent transfers. | ||
|
||
DTLS | ||
**Datagram Transport Layer Security**. A protocol that provides security for {term}`datagram`-based communication, such as UDP. | ||
DTLS offers security features similar to TLS, but is adapted because datagram protocols are connectionless. | ||
|
||
LDAP | ||
**Lightweight Directory Access Protocol**. | ||
|
||
SSL | ||
**Secure Socket Layer**. | ||
|
||
TLS | ||
**Transport Layer Security**. | ||
|
||
``` |
This file contains hidden or 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 |
---|---|---|
|
@@ -5,5 +5,6 @@ | |
:glob: | ||
:maxdepth: 1 | ||
|
||
What is a glossary <glossary_what> | ||
About the Academy <about> | ||
``` |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A gloss is more than a definition since it can include all kinds of extra features (See also, etc.).
Second, I was hiding a question about terms with multiple meanings. Is the gloss everything after the entry, or is a gloss what is written about an individual numbered sense? I'm inclined to define gloss as the smaller of the two, so that each numbered sense has its own gloss.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case, should we redefine the header "Structure" as "Structure of the gloss" or similar?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about ... (putting the content here till my git fix is in) ...
Structure of a gloss
This section describes a gloss that explains a single sense of a term.
If a term has multiple senses, each sense has its own gloss. In that case, the glosses under the term are numbered. The order of the glosses should be instructive, with the most basic or common senses presented first.