2 other issues I have noticed that make my inner OCD unhappy:
inconsistency in the format of the table headers in the spec: most of the time it is in bold but not always- numeric examples in the tables concerning the content of json files are not "highlighted" and might not be as obvious to the reader.
For example
Number of EEG channels included in the recording (for example, 128).
Should probably be:
Number of EEG channels included in the recording (for example, `128`).
- inconsistencies in the rendering of string and numeric values for tables (mostly for stings)
Sometimes examples are written:
and other times
| Column name |
Requirement level |
Description |
| name |
REQUIRED |
Channel name (for example, FC1, Cz) |
| units |
REQUIRED |
Physical unit of the value represented in this channel, for example, V for Volt, or fT/cm for femto Tesla per centimeter (see Units). |
Originally posted by @Remi-Gau in #739 (comment)
2 other issues I have noticed that make my inner OCD unhappy:
inconsistency in the format of the table headers in the spec: most of the time it is in bold but not alwaysFor example
Should probably be:
Sometimes examples are written:
and other times
Vfor Volt, orfT/cmfor femto Tesla per centimeter (see Units).Originally posted by @Remi-Gau in #739 (comment)