diff --git a/src/03-modality-agnostic-files.md b/src/03-modality-agnostic-files.md
index c7bac03654..31efc67c0d 100644
--- a/src/03-modality-agnostic-files.md
+++ b/src/03-modality-agnostic-files.md
@@ -179,40 +179,21 @@ For backwards compatibility, if `species` is absent, the participant is assumed
 `homo sapiens`.
 
 Commonly used *optional* columns in `participants.tsv` files are `age`, `sex`,
-`handedness`, `strain` and `strain_rrid`. We RECOMMEND to make use
+`handedness`, `strain`, and `strain_rrid`. We RECOMMEND to make use
 of these columns, and in case that you do use them, we RECOMMEND to use the
 following values for them:
 
--   `age`: numeric value in years (float or integer value)
-
--   `sex`: string value indicating phenotypical sex, one of "male", "female",
-    "other"
-
-    -   for "male", use one of these values: `male`, `m`, `M`, `MALE`, `Male`
-
-    -   for "female", use one of these values: `female`, `f`, `F`, `FEMALE`,
-        `Female`
-
-    -   for "other", use one of these values: `other`, `o`, `O`, `OTHER`,
-        `Other`
-
--   `handedness`: string value indicating one of "left", "right",
-    "ambidextrous"
-
-    -   for "left", use one of these values: `left`, `l`, `L`, `LEFT`, `Left`
-
-    -   for "right", use one of these values: `right`, `r`, `R`, `RIGHT`,
-        `Right`
-
-    -   for "ambidextrous", use one of these values: `ambidextrous`, `a`, `A`,
-        `AMBIDEXTROUS`, `Ambidextrous`
-
--   `strain`: for species different from `homo sapiens`, string value indicating
-    the strain of the species, for example: `C57BL/6J`.
-
--   `strain_rrid`: for species different from `homo sapiens`, research resource identifier
-    ([RRID](https://scicrunch.org/resources/Organisms/search)) of the strain of the species,
-    for example: `RRID:IMSR_JAX:000664`.
+{{ MACROS___make_columns_table(
+   {
+      "participant_id": ("REQUIRED", "There MUST be exactly one row for each participant."),
+      "species": "RECOMMENDED",
+      "age": "RECOMMENDED",
+      "sex": "RECOMMENDED",
+      "handedness": "RECOMMENDED",
+      "strain": "RECOMMENDED",
+      "strain_rrid": "RECOMMENDED",
+   }
+) }}
 
 Throughout BIDS you can indicate missing values with `n/a` (for "not
 available").
@@ -279,32 +260,17 @@ samples.json
 
 The purpose of this file is to describe properties of samples, indicated by the `sample` entity.
 This file is REQUIRED if `sample-<label>` is present in any file name within the dataset.
-If this file exists, it MUST contain the three following columns:
-
--   `sample_id`: MUST consist of `sample-<label>` values identifying one row
-    for each sample
-
--   `participant_id`: MUST consist of `sub-<label>`
-
--   `sample_type`: MUST consist of sample type values, either `cell line`, `in vitro differentiated cells`,
-    `primary cell`, `cell-free sample`, `cloning host`, `tissue`, `whole organisms`, `organoid` or
-    `technical sample` from [ENCODE Biosample Type](https://www.encodeproject.org/profiles/biosample_type)
-
-Other optional columns MAY be used to describe the samples.
 Each sample MUST be described by one and only one row.
 
-Commonly used *optional* columns in `samples.tsv` files are `pathology` and
-`derived_from`. We RECOMMEND to make use of these columns, and in case that
-you do use them, we RECOMMEND to use the following values for them:
-
--   `pathology`: string value describing the pathology of the sample or type of control.
-    When different from `healthy`, pathology SHOULD be specified in `samples.tsv`.
-    The pathology MAY instead be specified in [Sessions files](./03-modality-agnostic-files.md#sessions-file)
-    in case it changes over time.
-
--   `derived_from`: `sample-<label>` key/value pair from which a sample is derived from,
-    for example a slice of tissue (`sample-02`) derived from a block of tissue (`sample-01`),
-    as illustrated in the example below.
+{{ MACROS___make_columns_table(
+   {
+      "sample_id": ("REQUIRED", "The combination of `sample_id` and `participant_id` MUST be unique."),
+      "participant_id": ("REQUIRED", "The combination of `sample_id` and `participant_id` MUST be unique."),
+      "sample_type": "REQUIRED",
+      "pathology": "RECOMMENDED",
+      "derived_from": "RECOMMENDED",
+   }
+) }}
 
 `samples.tsv` example:
 
@@ -429,25 +395,12 @@ Some recordings consist of multiple parts, that span several files,
 for example through `echo-`, `part-`, or `split-` entities.
 Such recordings MUST be documented with one row per file.
 
-Relative paths to files should be used under a compulsory `filename` header.
-
-If acquisition time is included it should be listed under the `acq_time` header.
-Acquisition time refers to when the first data point in each run was acquired.
-Furthermore, if this header is provided, the acquisition times of all files that
-belong to a recording MUST be identical.
-
-Datetime should be expressed as described in [Units](./02-common-principles.md#units).
-
-For anonymization purposes all dates within one subject should be shifted by a
-randomly chosen (but consistent across all recordings) number of days.
-This way relative timing would be preserved, but chances of identifying a
-person based on the date and time of their scan would be decreased.
-Dates that are shifted for anonymization purposes SHOULD be set to the year 1925
-or earlier to clearly distinguish them from unmodified data.
-Note that some data formats do not support arbitrary recording dates.
-For example, the [EDF](https://www.edfplus.info/)
-data format can only contain recording dates after 1985.
-Shifting dates is RECOMMENDED, but not required.
+{{ MACROS___make_columns_table(
+   {
+      "filename": ("REQUIRED", "There MUST be exactly one row for each file."),
+      "acq_time": "OPTIONAL",
+   }
+) }}
 
 Additional fields can include external behavioral measures relevant to the
 scan.
@@ -485,6 +438,14 @@ These files MUST include a `session_id` column and describe each session by one
 Column names in `sessions.tsv` files MUST be different from group level participant key column names in the
 [`participants.tsv` file](./03-modality-agnostic-files.md#participants-file).
 
+{{ MACROS___make_columns_table(
+   {
+      "session_id": ("REQUIRED", "There MUST be exactly one row for each session."),
+      "acq_time": "OPTIONAL",
+      "pathology": "RECOMMENDED",
+   }
+) }}
+
 `_sessions.tsv` example:
 
 ```Text
diff --git a/src/04-modality-specific-files/02-magnetoencephalography.md b/src/04-modality-specific-files/02-magnetoencephalography.md
index 46a0841597..2aeefe5cad 100644
--- a/src/04-modality-specific-files/02-magnetoencephalography.md
+++ b/src/04-modality-specific-files/02-magnetoencephalography.md
@@ -221,24 +221,28 @@ The columns of the Channels description table stored in `*_channels.tsv` are:
 
 MUST be present **in this specific order**:
 
-| **Column name** | **Requirement level** | **Description**                                                                                                                                                               |
-| --------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| name            | REQUIRED              | Channel name (for example, MRT012, MEG023).                                                                                                                                   |
-| type            | REQUIRED              | Type of channel; MUST use the channel types listed below. Note that the type MUST be in upper-case.                                                                           |
-| 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](../02-common-principles.md#units)). |
+{{ MACROS___make_columns_table(
+   {
+      "name__channels": "REQUIRED",
+      "type__channels": "REQUIRED",
+      "units": "REQUIRED",
+   }
+) }}
 
 SHOULD be present:
 
-| **Column name**    | **Requirement level** | **Description**                                                                                                                                                                                                                                                     |
-| ------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| description        | OPTIONAL              | Brief free-text description of the channel, or other information of interest. See examples below.                                                                                                                                                                   |
-| sampling_frequency | OPTIONAL              | Sampling rate of the channel in Hz.                                                                                                                                                                                                                                 |
-| low_cutoff         | OPTIONAL              | Frequencies used for the high-pass filter applied to the channel in Hz. If no high-pass filter applied, use `n/a`.                                                                                                                                                  |
-| high_cutoff        | OPTIONAL              | Frequencies used for the low-pass filter applied to the channel in Hz. If no low-pass filter applied, use `n/a`. Note that hardware anti-aliasing in A/D conversion of all MEG/EEG electronics applies a low-pass filter; specify its frequency here if applicable. |
-| notch              | OPTIONAL              | Frequencies used for the notch filter applied to the channel, in Hz. If no notch filter applied, use `n/a`.                                                                                                                                                         |
-| software_filters   | OPTIONAL              | List of temporal and/or spatial software filters applied (for example, "SSS", `"SpatialCompensation"`). Note that parameters should be defined in the general MEG sidecar .json file. Indicate `n/a` in the absence of software filters applied.                    |
-| status             | OPTIONAL              | Data quality observed on the channel `(good/bad)`. A channel is considered `bad` if its data quality is compromised by excessive noise. Description of noise type SHOULD be provided in `[status_description]`.                                                     |
-| status_description | OPTIONAL              | Freeform text description of noise or artifact affecting data quality on the channel. It is meant to explain why the channel was declared bad in `[status]`.                                                                                                        |
+{{ MACROS___make_columns_table(
+   {
+      "description": "OPTIONAL",
+      "sampling_frequency": "OPTIONAL",
+      "low_cutoff": "OPTIONAL",
+      "high_cutoff": "OPTIONAL",
+      "notch": "OPTIONAL",
+      "software_filters": "OPTIONAL",
+      "status": "OPTIONAL",
+      "status_description": "OPTIONAL",
+   }
+) }}
 
 Example:
 
diff --git a/src/04-modality-specific-files/03-electroencephalography.md b/src/04-modality-specific-files/03-electroencephalography.md
index 1222db4453..c85fc8dc71 100644
--- a/src/04-modality-specific-files/03-electroencephalography.md
+++ b/src/04-modality-specific-files/03-electroencephalography.md
@@ -216,24 +216,28 @@ The columns of the Channels description table stored in `*_channels.tsv` are:
 
 MUST be present **in this specific order**:
 
-| **Column name** | **Requirement level** | **Description**                                                                                                                                                               |
-| --------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| name            | REQUIRED              | Channel name (for example, FC1, Cz)                                                                                                                                           |
-| type            | REQUIRED              | Type of channel; MUST use the channel types listed below. Note that the type MUST be in upper-case.                                                                           |
-| 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](../02-common-principles.md#units)). |
+{{ MACROS___make_columns_table(
+   {
+      "name__channels": "REQUIRED",
+      "type__channels": "REQUIRED",
+      "units": "REQUIRED",
+   }
+) }}
 
 SHOULD be present:
 
-| **Column name**    | **Requirement level** | **Description**                                                                                                                                                                                                                                                 |
-| ------------------ | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| description        | OPTIONAL              | Free-form text description of the channel, or other information of interest. See examples below.                                                                                                                                                                |
-| sampling_frequency | OPTIONAL              | Sampling rate of the channel in Hz.                                                                                                                                                                                                                             |
-| reference          | OPTIONAL              | Name of the reference electrode(s) (not needed when it is common to all channels, in that case it can be specified in `*_eeg.json` as `EEGReference`).                                                                                                          |
-| low_cutoff         | OPTIONAL              | Frequencies used for the high-pass filter applied to the channel in Hz. If no high-pass filter applied, use `n/a`.                                                                                                                                              |
-| high_cutoff        | OPTIONAL              | Frequencies used for the low-pass filter applied to the channel in Hz. If no low-pass filter applied, use `n/a`. Note that hardware anti-aliasing in A/D conversion of all EEG electronics applies a low-pass filter; specify its frequency here if applicable. |
-| notch              | OPTIONAL              | Frequencies used for the notch filter applied to the channel, in Hz. If no notch filter applied, use `n/a`.                                                                                                                                                     |
-| status             | OPTIONAL              | Data quality observed on the channel (`good`, `bad`). A channel is considered `bad` if its data quality is compromised by excessive noise. Description of noise type SHOULD be provided in `status_description`.                                                |
-| status_description | OPTIONAL              | Free-form text description of noise or artifact affecting data quality on the channel. It is meant to explain why the channel was declared bad in `status`.                                                                                                     |
+{{ MACROS___make_columns_table(
+   {
+      "description": "OPTIONAL",
+      "sampling_frequency": "OPTIONAL",
+      "reference__eeg": "OPTIONAL",
+      "low_cutoff": "OPTIONAL",
+      "high_cutoff": "OPTIONAL",
+      "notch": "OPTIONAL",
+      "status": "OPTIONAL",
+      "status_description": "OPTIONAL",
+   }
+) }}
 
 Restricted keyword list for field `type` in alphabetic order (shared with the
 MEG and iEEG modality; however, only the types that are common in EEG data are listed here).
@@ -288,20 +292,24 @@ file MUST be specified as well**. The order of the required columns in the
 
 MUST be present **in this specific order**:
 
-| **Column name** | **Requirement level** | **Description**                     |
-| --------------- | --------------------- | ----------------------------------- |
-| name            | REQUIRED              | Name of the electrode.              |
-| x               | REQUIRED              | Recorded position along the x-axis. |
-| y               | REQUIRED              | Recorded position along the y-axis. |
-| z               | REQUIRED              | Recorded position along the z-axis. |
+{{ MACROS___make_columns_table(
+   {
+      "name__electrodes": "REQUIRED",
+      "x": "REQUIRED",
+      "y": "REQUIRED",
+      "z": "REQUIRED",
+   }
+) }}
 
 SHOULD be present:
 
-| **Column name** | **Requirement level** | **Description**                                                        |
-| --------------- | --------------------- | ---------------------------------------------------------------------- |
-| type            | RECOMMENDED           | Type of the electrode (for example, cup, ring, clip-on, wire, needle). |
-| material        | RECOMMENDED           | Material of the electrode  (for example, Tin, Ag/AgCl, Gold).          |
-| impedance       | RECOMMENDED           | Impedance of the electrode, units MUST be in `kOhm`.                   |
+{{ MACROS___make_columns_table(
+   {
+      "type__electrodes": "RECOMMENDED",
+      "material": "RECOMMENDED",
+      "impedance": "RECOMMENDED",
+   }
+) }}
 
 ### Example `electrodes.tsv`
 
diff --git a/src/04-modality-specific-files/04-intracranial-electroencephalography.md b/src/04-modality-specific-files/04-intracranial-electroencephalography.md
index e2184b79d5..84ee39d053 100644
--- a/src/04-modality-specific-files/04-intracranial-electroencephalography.md
+++ b/src/04-modality-specific-files/04-intracranial-electroencephalography.md
@@ -226,25 +226,30 @@ The columns of the Channels description table stored in `*_channels.tsv` are:
 
 MUST be present **in this specific order**:
 
-| **Column name** | **Requirement level** | **Description**                                                                                                                                                                                             |
-| --------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| name            | REQUIRED              | Label of the channel. The label must correspond to \_electrodes.tsv name and all ieeg type channels are required to have a position. The reference channel name MAY be provided in the reference column.    |
-| type            | REQUIRED              | Type of channel, see below for adequate keywords in this field. Note that the type MUST be in upper case.                                                                                                   |
-| 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](../02-common-principles.md#units)).                               |
-| low_cutoff      | REQUIRED              | Frequencies used for the low pass filter applied to the channel in Hz. If no low pass filter was applied, use `n/a`. Note that anti-alias is a low pass filter, specify its frequencies here if applicable. |
-| high_cutoff     | REQUIRED              | Frequencies used for the high pass filter applied to the channel in Hz. If no high pass filter applied, use `n/a`.                                                                                          |
+{{ MACROS___make_columns_table(
+   {
+      "name__channels": ("REQUIRED", "The label must correspond to `_electrodes.tsv` name and all ieeg type channels are
+    required to have a position."),
+      "type__channels": "REQUIRED",
+      "units": "REQUIRED",
+      "low_cutoff": "REQUIRED",
+      "high_cutoff": "REQUIRED",
+   }
+) }}
 
 SHOULD be present:
 
-| **Column name**    | **Requirement level** | **Description**                                                                                                                                                                                                                                                            |
-| ------------------ | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| reference          | OPTIONAL              | Specification of the reference (for example, 'mastoid', 'ElectrodeName01', 'intracranial', 'CAR', 'other', 'n/a'). If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.                                                               |
-| group              | OPTIONAL              | Which group of channels (grid/strip/seeg/depth) this channel belongs to. This is relevant because one group has one cable-bundle and noise can be shared. This can be a name or number. Note that any groups specified in `_electrodes.tsv` must match those present here. |
-| sampling_frequency | OPTIONAL              | Sampling rate of the channel in Hz.                                                                                                                                                                                                                                        |
-| description        | OPTIONAL              | Brief free-text description of the channel, or other information of interest (for example, position (for example, "left lateral temporal surface")).                                                                                                                       |
-| notch              | OPTIONAL              | Frequencies used for the notch filter applied to the channel, in Hz. If no notch filter applied, use n/a.                                                                                                                                                                  |
-| status             | OPTIONAL              | Data quality observed on the channel (good/bad). A channel is considered bad if its data quality is compromised by excessive noise. Description of noise type SHOULD be provided in `[status_description]`.                                                                |
-| status_description | OPTIONAL              | Freeform text description of noise or artifact affecting data quality on the channel. It is meant to explain why the channel was declared bad in `[status]`.                                                                                                               |
+{{ MACROS___make_columns_table(
+   {
+      "reference__ieeg": "OPTIONAL",
+      "group": ("OPTIONAL", "Note that any groups specified in `_electrodes.tsv` must match those present here."),
+      "sampling_frequency": "OPTIONAL",
+      "description": "OPTIONAL",
+      "notch": "OPTIONAL",
+      "status": "OPTIONAL",
+      "status_description": "OPTIONAL",
+   }
+) }}
 
 **Example** `sub-01_channels.tsv`:
 
@@ -330,35 +335,42 @@ For example:
    }
 ) }}
 
-The order of the required columns in the `*_electrodes.tsv` file MUST be as
-listed below.
+The order of the required columns in the `*_electrodes.tsv` file MUST be as listed below.
+The `x`, `y`, and `z` columns indicate the positions of the center of each electrode in Cartesian coordinates.
+Units are specified in `space-<label>_coordsystem.json`.
 
 MUST be present **in this specific order**:
 
-| **Column name** | **Requirement level** | **Description**                                                                                                                  |
-| --------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| name            | REQUIRED              | Name of the electrode contact point.                                                                                             |
-| x               | REQUIRED              | X position. The positions of the center of each electrode in xyz space. Units are specified in `space-<label>_coordsystem.json`. |
-| y               | REQUIRED              | Y position.                                                                                                                      |
-| z               | REQUIRED              | Z position. If electrodes are in 2D space this should be a column of `n/a` values.                                               |
-| size            | REQUIRED              | Surface area of the electrode, units MUST be in `mm^2`.                                                                          |
+{{ MACROS___make_columns_table(
+   {
+      "name__electrodes": "REQUIRED",
+      "x": "REQUIRED",
+      "y": "REQUIRED",
+      "z": ("REQUIRED", "If electrodes are in 2D space this should be a column of `n/a` values."),
+      "size": "REQUIRED",
+   }
+) }}
 
 SHOULD be present:
 
-| **Column name** | **Requirement level** | **Description**                                                                                                                  |
-| --------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| material        | RECOMMENDED           | Material of the electrodes.                                                                                                      |
-| manufacturer    | RECOMMENDED           | The manufacturer for each electrode. Can be used if electrodes were manufactured by more than one company.                       |
-| group           | RECOMMENDED           | The group that the electrode is a part of. Note that any group specified here should match a group specified in `_channels.tsv`. |
-| hemisphere      | RECOMMENDED           | The hemisphere in which the electrode is placed, one of `['L' or 'R']` (use capital).                                            |
+{{ MACROS___make_columns_table(
+   {
+      "material": "RECOMMENDED",
+      "manufacturer": "RECOMMENDED",
+      "group": ("RECOMMENDED", "Note that any group specified here should match a group specified in `_channels.tsv`."),
+      "hemisphere": "RECOMMENDED",
+   }
+) }}
 
 MAY be present:
 
-| **Column name** | **Requirement level** | **Description**                                                                                                                                        |
-| --------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| type            | OPTIONAL              | Optional type of the electrode, for example, cup, ring, clip-on, wire, needle, ...                                                                     |
-| impedance       | OPTIONAL              | Impedance of the electrode, units MUST be in `kOhm`.                                                                                                   |
-| dimension       | OPTIONAL              | Size of the group (grid/strip/probe) that this electrode belongs to. Must be of form `[AxB]` with the smallest dimension first (for example, `[1x8]`). |
+{{ MACROS___make_columns_table(
+   {
+      "type__electrodes": "OPTIONAL",
+      "impedance": "OPTIONAL",
+      "dimension": "OPTIONAL",
+   }
+) }}
 
 Example:
 
diff --git a/src/04-modality-specific-files/05-task-events.md b/src/04-modality-specific-files/05-task-events.md
index 193de70b02..6fe334e0ff 100644
--- a/src/04-modality-specific-files/05-task-events.md
+++ b/src/04-modality-specific-files/05-task-events.md
@@ -34,15 +34,17 @@ file describing the columns in detail (see
 The tabular files consists of one row per event and a set of REQUIRED
 and OPTIONAL columns:
 
-| **Column name** | **Requirement level** | **Data type**            | **Description**                                                                                                                                                                                                                                                               |
-| --------------- | --------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| onset           | REQUIRED              | [number][]               | Onset (in seconds) of the event measured from the beginning of the acquisition of the first data point in the corresponding task data file. Negative numbers in "onset" are allowed<sup>5</sup>.                                                                              |
-| duration        | REQUIRED              | [number][]               | Duration of the event (measured from onset) in seconds. MUST be either zero or positive (or `"n/a"` if unavailable). A "duration" value of zero implies that the event is so short as to be effectively modeled as an impulse.                                                |
-| sample          | OPTIONAL              | [number][]               | Onset of the event according to the sampling scheme of the recorded modality (that is, referring to the raw data file that the `events.tsv` file accompanies).                                                                                                                |
-| trial_type      | OPTIONAL              | [string][]               | Primary categorisation of each trial to identify them as instances of the experimental conditions. For example: for a response inhibition task, it could take on values `"go"` and `"no-go"` to refer to response initiation and response inhibition experimental conditions. |
-| response_time   | OPTIONAL              | [number][]               | Response time measured in seconds. A negative response time can be used to represent preemptive responses and `"n/a"` denotes a missed response.                                                                                                                              |
-| value           | OPTIONAL              | [string][] or [number][] | Marker value associated with the event (for example, the value of a TTL trigger that was recorded at the onset of the event).                                                                                                                                                 |
-| HED             | OPTIONAL              | [string][]               | Hierarchical Event Descriptor (HED) tag. See [Appendix III](../99-appendices/03-hed.md) for details.                                                                                                                                                                          |
+{{ MACROS___make_columns_table(
+   {
+      "onset": "REQUIRED",
+      "duration": "REQUIRED",
+      "sample": "OPTIONAL",
+      "trial_type": "OPTIONAL",
+      "response_time": "OPTIONAL",
+      "value": "OPTIONAL",
+      "HED": "OPTIONAL",
+   }
+) }}
 
 <sup>5</sup> Note for MRI data:
 If any acquired scans have been discarded before forming the imaging data file,
@@ -137,9 +139,11 @@ for a given event,
 There are no restrictions on the file formats of the stimuli files,
 but they should be stored in the `/stimuli` folder.
 
-| **Column name** | **Requirement level** | **Data type** | **Description**                                                                                                                                                                                                                                                                                            |
-| --------------- | --------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| stim_file       | OPTIONAL              | [string][]    | Represents the location of the stimulus file (such as an image, video, or audio file) presented at the given onset time. The values under the `stim_file` column correspond to a path relative to the folder `/stimuli`. For example `images/cat03.jpg` will be translated to `/stimuli/images/cat03.jpg`. |
+{{ MACROS___make_columns_table(
+   {
+      "stim_file": "OPTIONAL",
+   }
+) }}
 
 ### Stimuli databases
 
@@ -258,9 +262,3 @@ in the accompanying JSON sidecar as follows (based on the example of the previou
     }
 }
 ```
-
-<!-- Link Definitions -->
-
-[number]: https://www.w3schools.com/js/js_json_datatypes.asp
-
-[string]: https://www.w3schools.com/js/js_json_datatypes.asp
diff --git a/src/04-modality-specific-files/06-physiological-and-other-continuous-recordings.md b/src/04-modality-specific-files/06-physiological-and-other-continuous-recordings.md
index af4246d6c0..678b2fa3ae 100644
--- a/src/04-modality-specific-files/06-physiological-and-other-continuous-recordings.md
+++ b/src/04-modality-specific-files/06-physiological-and-other-continuous-recordings.md
@@ -107,11 +107,13 @@ Example `*_physio.json`:
 To store pulse or breathing measurements, or the scanner trigger signal, the
 following naming conventions SHOULD be used for the column names:
 
-| **Column name** | **Description**                                      |
-| --------------- | ---------------------------------------------------- |
-| cardiac         | continuous pulse measurement                         |
-| respiratory     | continuous breathing measurement                     |
-| trigger         | continuous measurement of the scanner trigger signal |
+{{ MACROS___make_columns_table(
+   {
+      "cardiac": "OPTIONAL",
+      "respiratory": "OPTIONAL",
+      "trigger": "OPTIONAL",
+   }
+) }}
 
 For any other data to be specified in columns, the column names can be chosen
 as deemed appropriate by the researcher.
diff --git a/src/04-modality-specific-files/09-positron-emission-tomography.md b/src/04-modality-specific-files/09-positron-emission-tomography.md
index c4312117ea..6de6644ab1 100644
--- a/src/04-modality-specific-files/09-positron-emission-tomography.md
+++ b/src/04-modality-specific-files/09-positron-emission-tomography.md
@@ -355,14 +355,16 @@ The following metadata SHOULD or MUST be provided if corresponding flags are `tr
 The following columns are defined for `_blood.tsv` files.
 The `time` column MUST always be the first column.
 
-| **Column name**              | **Requirement level**                                       | **Description**                                                                   | **Units**                                                                           |
-| ---------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
-| `time`                       | REQUIRED                                                    | Time in relation to `TimeZero` defined by the `*_pet.json`. (for example, 5)      | Seconds                                                                             |
-| `plasma_radioactivity`       | REQUIRED if `PlasmaAvail` is `true`                         | Radioactivity in plasma                                                           | Unit of plasma radioactivity (for example, `"kBq/mL"`)                              |
-| `metabolite_parent_fraction` | REQUIRED if `MetaboliteAvail` is `true`                     | Parent fraction of the radiotracer (0-1)                                          | Unit of parent fraction (for example, `"unitless"`)                                 |
-| `metabolite_polar_fraction`  | RECOMMENDED if `MetaboliteAvail` is `true`                  | Polar metabolite fraction of the radiotracer (0-1)                                | Unit of polar metabolite fraction (for example, `"unitless"`)                       |
-| `hplc_recovery_fractions`    | REQUIRED if `MetaboliteRecoveryCorrectionApplied` is `true` | HPLC recovery fractions (the fraction of activity that gets loaded onto the HPLC) | Unit of recovery fractions (for example, `"unitless"`)                              |
-| `whole_blood_radioactivity`  | REQUIRED if `WholeBloodAvail` is `true`                     | Radioactivity in whole blood samples                                              | Unit of radioactivity measurements in whole blood samples (for example, `"kBq/mL"`) |
+{{ MACROS___make_columns_table(
+   {
+      "time": "REQUIRED",
+      "plasma_radioactivity": "REQUIRED if `PlasmaAvail` is `true`",
+      "metabolite_parent_fraction": "REQUIRED if `MetaboliteAvail` is `true`",
+      "metabolite_polar_fraction": "RECOMMENDED if `MetaboliteAvail` is `true`",
+      "hplc_recovery_fractions": "REQUIRED if `MetaboliteRecoveryCorrectionApplied` is `true`",
+      "whole_blood_radioactivity": "REQUIRED if `WholeBloodAvail` is `true`",
+   }
+) }}
 
 As with all [tabular files](../02-common-principles.md#tabular-files),
 additional columns MAY be defined in `_blood.json`.
diff --git a/src/05-derivatives/03-imaging.md b/src/05-derivatives/03-imaging.md
index 66d18bf730..7f2ce11e83 100644
--- a/src/05-derivatives/03-imaging.md
+++ b/src/05-derivatives/03-imaging.md
@@ -440,13 +440,15 @@ Example:
 
 These TSV lookup tables contain the following columns:
 
-| **Column name** | **Requirement level** | **Description**                                               |
-| --------------- | --------------------- |-------------------------------------------------------------- |
-| index           | REQUIRED              | The label integer index                                       |
-| name            | REQUIRED              | The unique label name                                         |
-| abbreviation    | OPTIONAL              | The unique label abbreviation                                 |
-| color           | OPTIONAL              | Hexadecimal. Label color for visualization                    |
-| mapping         | OPTIONAL              | Corresponding integer label in the standard BIDS label lookup |
+{{ MACROS___make_columns_table(
+   {
+      "index": "REQUIRED",
+      "name__segmentations": "REQUIRED",
+      "abbreviation": "OPTIONAL",
+      "color": "OPTIONAL",
+      "mapping": "OPTIONAL",
+   }
+) }}
 
 An example, custom `dseg.tsv` that defines three labels:
 
diff --git a/src/schema/README.md b/src/schema/README.md
index 4d9eb51283..c3d142cba6 100644
--- a/src/schema/README.md
+++ b/src/schema/README.md
@@ -52,12 +52,57 @@ Each of these object types has a single file in the `objects/` folder.
 
 -   `metadata.yaml`: All valid metadata fields that are explicitly supported in BIDS sidecar JSON files.
 
+-   `columns.yaml`: All valid columns that are explicitly supported in BIDS TSV files.
+
 -   `suffixes.yaml`: Valid file suffixes.
 
 -   `top_level_files.yaml`: Valid top-level files which may appear in a BIDS dataset.
 
 -   `associated_data.yaml`: Folders that may appear within a dataset folder without following BIDS rules.
 
+### On re-used objects with different definitions
+
+If an object may mean something different depending on where it is used within the specification,
+then this must be reflected in the schema.
+Specifically, each version of the object must have its own definition within the relevant file.
+However, since object files are organized as dictionaries, each object must have a unique key.
+Thus, we append a suffix to each re-used object's key in order to make it unique.
+For objects with `CamelCase` names (for example, metadata fields), the suffix will start with a single underscore (`_`).
+For objects with `snake_case` names, two underscores must be used.
+
+There should also be a comment near the object definition in the YAML file describing the nature of the different objects.
+
+For example, the TSV column `"reference"` means different things when used for EEG data, as compared to iEEG data.
+As such, there are two definitions in `columns.yaml` for the `"reference"` column: `"reference__eeg"` and `"reference_ieeg"`.
+
+```yaml
+# reference column for channels.tsv files for EEG data
+reference__eeg:
+  name: reference
+  description: |
+    Name of the reference electrode(s).
+    This column is not needed when it is common to all channels.
+    In that case the reference electrode(s) can be specified in `*_eeg.json` as `EEGReference`).
+  type: string
+# reference column for channels.tsv files for iEEG data
+reference__ieeg:
+  name: reference
+  description: |
+    Specification of the reference (for example, 'mastoid', 'ElectrodeName01', 'intracranial', 'CAR', 'other', 'n/a').
+    If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.
+  anyOf:
+  - type: string
+  - type: string
+    enum:
+    - n/a
+```
+
+When adding new object definitions to the schema,
+every effort should be made to find a shared, common definition for the term, should it already exist.
+If the differences between two versions of the same object are subtle or driven by context,
+then you can generally _append_ additional text to the object definition within the associated rendered table in the specification,
+rather than creating a separate entry in the schema.
+
 ### `modalities.yaml`
 
 This file contains a dictionary in which each modality is defined.
@@ -270,7 +315,7 @@ ExampleField:
             type: number
 ```
 
-Finally, if the data type description of a field is reused across fields,
+Furthermore, if the data type description of a field is reused across fields,
 then it may be defined in a separate field and referenced in each target field with the `$ref` keyword.
 Here is an example of a field definition using `$ref`:
 ```yaml
@@ -308,6 +353,13 @@ ExampleField:
         - PossibleValue2
 ```
 
+### `columns.yaml`
+
+This file contains definitions for all TSV columns currently supported in BIDS.
+
+Entries in this file follow the same rules as `metadata.yaml`,
+although column names appear in `snake_case`, rather than `CamelCase`.
+
 ### `suffixes.yaml`
 
 This file contains a dictionary in which each suffix is defined.
diff --git a/src/schema/objects/columns.yaml b/src/schema/objects/columns.yaml
new file mode 100644
index 0000000000..ee658ffbbd
--- /dev/null
+++ b/src/schema/objects/columns.yaml
@@ -0,0 +1,569 @@
+---
+HED:
+  name: HED
+  description: |
+    Hierarchical Event Descriptor (HED) Tag.
+    See [Appendix III](/99-appendices/03-hed.html) for details.
+  type: string
+abbreviation:
+  name: abbreviation
+  description: |
+    The unique label abbreviation
+  type: string
+acq_time:
+  name: acq_time
+  description: |
+    Acquisition time refers to when the first data point in each run was acquired.
+    Furthermore, if this header is provided, the acquisition times of all files that
+    belong to a recording MUST be identical.
+
+    Datetime should be expressed as described in [Units](/02-common-principles.html#units).
+
+    For anonymization purposes all dates within one subject should be shifted by a randomly
+    chosen (but consistent across all recordings) number of days.
+    This way relative timing would be preserved, but chances of identifying a person based
+    on the date and time of their scan would be decreased.
+    Dates that are shifted for anonymization purposes SHOULD be set to the year 1925 or earlier
+    to clearly distinguish them from unmodified data.
+    Note that some data formats do not support arbitrary recording dates.
+    For example, the [EDF](https://www.edfplus.info/)
+    data format can only contain recording dates after 1985.
+    Shifting dates is RECOMMENDED, but not required.
+  type: string
+  format: datetime
+age:
+  name: age
+  description: |
+    Numeric value in years (float or integer value).
+  type: number
+  unit: year
+cardiac:
+  name: cardiac
+  description: |
+    continuous pulse measurement
+  type: number
+color:
+  name: color
+  description: |
+    Hexadecimal. Label color for visualization.
+  type: string
+  unit: hexadecimal
+derived_from:
+  name: derived_from
+  description: |
+    `sample-<label>` key/value pair from which a sample is derived,
+    for example a slice of tissue (`sample-02`) derived from a block of tissue (`sample-01`).
+  type: string
+  pattern: ^sample-[0-9a-zA-Z]+$
+description:
+  name: description
+  description: |
+    Brief free-text description of the channel, or other information of interest.
+  type: string
+dimension:
+  name: dimension
+  description: |
+    Size of the group (grid/strip/probe) that this electrode belongs to.
+    Must be of form `[AxB]` with the smallest dimension first (for example, `[1x8]`).
+  type: string
+duration:
+  name: duration
+  description: |
+    Duration of the event (measured from onset) in seconds.
+    Must always be either zero or positive (or `"n/a"` if unavailable).
+    A "duration" value of zero implies that the delta function or event is so
+    short as to be effectively modeled as an impulse.
+  anyOf:
+  - type: number
+    unit: s
+    minimum: 0
+  - type: string
+    enum:
+    - n/a
+filename:
+  name: filename
+  description: |
+    Relative paths to files.
+  type: string
+  format: participant_relative
+group:
+  name: group
+  description: |
+    Which group of channels (grid/strip/seeg/depth) this channel belongs to.
+    This is relevant because one group has one cable-bundle and noise can be shared.
+    This can be a name or number.
+  anyOf:
+  - type: string
+  - type: number
+handedness:
+  name: handedness
+  description: |
+    String value indicating one of "left", "right", "ambidextrous".
+
+    For "left", use one of these values: `left`, `l`, `L`, `LEFT`, `Left`.
+
+    For "right", use one of these values: `right`, `r`, `R`, `RIGHT`, `Right`.
+
+    For "ambidextrous", use one of these values: `ambidextrous`, `a`, `A`, `AMBIDEXTROUS`,
+    `Ambidextrous`.
+  type: string
+  enum:
+  - left
+  - l
+  - L
+  - LEFT
+  - Left
+  - right
+  - r
+  - R
+  - RIGHT
+  - Right
+  - ambidextrous
+  - a
+  - A
+  - AMBIDEXTROUS
+  - Ambidextrous
+  - n/a
+hemisphere:
+  name: hemisphere
+  description: |
+    The hemisphere in which the electrode is placed, one of `['L' or 'R']` (MUST be in upper-case).
+  type: string
+  enum:
+  - L
+  - R
+high_cutoff:
+  name: high_cutoff
+  description: |
+    Frequencies used for the low-pass filter applied to the channel in Hz.
+    If no low-pass filter applied, use `n/a`.
+    Note that hardware anti-aliasing in A/D conversion of all MEG/EEG electronics
+    applies a low-pass filter; specify its frequency here if applicable.
+  anyOf:
+  - type: number
+    unit: Hz
+    minimum: 0
+  - type: string
+    enum:
+    - n/a
+hplc_recovery_fractions:
+  name: hplc_recovery_fractions
+  description: |
+    HPLC recovery fractions (the fraction of activity that gets loaded onto the HPLC).
+  type: number
+  unit: arbitrary
+impedance:
+  name: impedance
+  description: |
+    Impedance of the electrode, units MUST be in `kOhm`.
+  type: number
+  unit: kOhm
+index:
+  name: index
+  description: |
+    The label integer index.
+  type: integer
+low_cutoff:
+  name: low_cutoff
+  description: |
+    Frequencies used for the high-pass filter applied to the channel in Hz.
+    If no high-pass filter applied, use `n/a`.
+  anyOf:
+  - type: number
+    unit: Hz
+  - type: string
+    enum:
+    - n/a
+manufacturer:
+  name: manufacturer
+  description: |
+    The manufacturer for each electrode.
+    Can be used if electrodes were manufactured by more than one company.
+  type: string
+mapping:
+  name: mapping
+  description: |
+    Corresponding integer label in the standard BIDS label lookup.
+  type: integer
+material:
+  name: material
+  description: |
+    Material of the electrode (for example, `"Tin"`, `"Ag/AgCl"`, `"Gold"`).
+  type: string
+metabolite_parent_fraction:
+  name: metabolite_parent_fraction
+  description: |
+    Parent fraction of the radiotracer (0-1).
+  type: number
+  minimum: 0
+  maximum: 1
+metabolite_polar_fraction:
+  name: metabolite_polar_fraction
+  description: |
+    Polar metabolite fraction of the radiotracer (0-1).
+  type: number
+  minimum: 0
+  maximum: 1
+# name column for channels.tsv files
+name__channels:
+  name: name
+  description: |
+    Label of the channel.
+  type: string
+# name column for electrodes.tsv files
+name__electrodes:
+  name: name
+  description: |
+    Name of the electrode contact point.
+  type: string
+# name column for dseg.tsv files
+name__segmentations:
+  name: name
+  description: |
+    The unique label name.
+  type: string
+notch:
+  name: notch
+  description: |
+    Frequencies used for the notch filter applied to the channel, in Hz.
+    If no notch filter applied, use `n/a`.
+  anyOf:
+  - type: number
+    unit: Hz
+  - type: string
+    enum:
+    - n/a
+onset:
+  name: onset
+  description: |
+    Onset (in seconds) of the event, measured from the beginning of the acquisition
+    of the first data point stored in the corresponding task data file.
+    Negative onsets are allowed, to account for events that occur prior to the first
+    stored data point.
+    For example, in case there is an in-scanner training phase that begins before
+    the scanning sequence has started events from this sequence should have
+    negative onset time counting down to the beginning of the acquisition of the
+    first volume.
+
+    If any data points have been discarded before forming the data file
+    (for example, "dummy volumes" in BOLD fMRI),
+    a time of 0 corresponds to the first stored data point and not the first
+    acquired data point.
+  type: number
+  unit: s
+pathology:
+  name: pathology
+  description: |
+    String value describing the pathology of the sample or type of control.
+    When different from `healthy`, pathology SHOULD be specified.
+    The pathology may be specified in either `samples.tsv` or
+    `sessions.tsv`, depending on whether the pathology changes over time.
+  type: string
+participant_id:
+  name: participant_id
+  description: |
+    A participant identifier of the form `sub-<label>`,
+    matching a participant entity found in the dataset.
+  type: string
+  pattern: ^sub-[0-9a-zA-Z]+$
+plasma_radioactivity:
+  name: plasma_radioactivity
+  description: |
+    Radioactivity in plasma, in unit of plasma radioactivity (for example, `"kBq/mL"`).
+  type: number
+# reference column for channels.tsv files for EEG data
+reference__eeg:
+  name: reference
+  description: |
+    Name of the reference electrode(s).
+    This column is not needed when it is common to all channels.
+    In that case the reference electrode(s) can be specified in `*_eeg.json` as `EEGReference`).
+  type: string
+# reference column for channels.tsv files for iEEG data
+reference__ieeg:
+  name: reference
+  description: |
+    Specification of the reference (for example, 'mastoid', 'ElectrodeName01', 'intracranial', 'CAR', 'other', 'n/a').
+    If the channel is not an electrode channel (for example, a microphone channel) use `n/a`.
+  anyOf:
+  - type: string
+  - type: string
+    enum:
+    - n/a
+respiratory:
+  name: respiratory
+  description: |
+    continuous breathing measurement
+  type: number
+response_time:
+  name: response_time
+  description: |
+    Response time measured in seconds.
+    A negative response time can be used to represent preemptive responses and
+    "n/a" denotes a missed response.
+  anyOf:
+  - type: number
+    unit: s
+  - type: string
+    enum:
+    - n/a
+sample:
+  name: sample
+  description: |
+    Onset of the event according to the sampling scheme of the recorded modality
+    (that is, referring to the raw data file that the `events.tsv` file accompanies).
+  type: integer
+sample_id:
+  name: sample_id
+  description: |
+    A sample identifier of the form `sample-<label>`,
+    matching a sample entity found in the dataset.
+  type: string
+  pattern: ^sample-[0-9a-zA-Z]+$
+sample_type:
+  name: sample_type
+  description: |
+    Biosample type defined by
+    [ENCODE Biosample Type](https://www.encodeproject.org/profiles/biosample_type).
+    One of: `"cell line"`, `"in vitro differentiated cells"`, `"primary cell"`, `"cell-free sample"`,
+    `"cloning host"`, `"tissue"`, `"whole organisms"`, `"organoid"`, or `"technical sample"`.
+  type: string
+  enum:
+  - cell line
+  - in vitro differentiated cells
+  - primary cell
+  - cell-free sample
+  - cloning host
+  - tissue
+  - whole organisms
+  - organoid
+  - technical sample
+sampling_frequency:
+  name: sampling_frequency
+  description: |
+    Sampling rate of the channel in Hz.
+  type: number
+  unit: Hz
+session_id:
+  name: session_id
+  description: |
+    A session identifier of the form `ses-<label>`,
+    matching a session found in the dataset.
+  type: string
+  pattern: ^ses-[0-9a-zA-Z]+$
+sex:
+  name: sex
+  description: |
+    String value indicating phenotypical sex, one of "male", "female", "other".
+
+    For "male", use one of these values: `male`, `m`, `M`, `MALE`, `Male`.
+
+    For "female", use one of these values: `female`, `f`, `F`, `FEMALE`, `Female`.
+
+    For "other", use one of these values: `other`, `o`, `O`, `OTHER`, `Other`.
+  type: string
+  enum:
+  - male
+  - m
+  - M
+  - MALE
+  - Male
+  - female
+  - f
+  - F
+  - FEMALE
+  - Female
+  - other
+  - o
+  - O
+  - OTHER
+  - Other
+  - n/a
+size:
+  name: size
+  description: |
+    Surface area of the electrode, units MUST be in `mm^2`.
+  type: number
+  unit: mm2
+software_filters:
+  name: software_filters
+  description: |
+    List of temporal and/or spatial software filters applied
+    (for example, "SSS", `"SpatialCompensation"`).
+    Note that parameters should be defined in the general MEG sidecar .json file.
+    Indicate `n/a` in the absence of software filters applied.
+  anyOf:
+  - type: string
+  - type: string
+    enum:
+    - n/a
+species:
+  name: species
+  description: |
+    The `species` column SHOULD be a binomial species name from the
+    [NCBI Taxonomy](https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi)
+    (for example, `homo sapiens`, `mus musculus`, `rattus norvegicus`).
+    For backwards compatibility, if `species` is absent, the participant is assumed to be
+    `homo sapiens`.
+  type: string
+status:
+  name: status
+  description: |
+    Data quality observed on the channel.
+    Must be one of: `good`, `bad`, or `n/a` (when quality is unknown).
+    A channel is considered `bad` if its data quality is compromised by excessive noise.
+    Description of noise type SHOULD be provided in `[status_description]`.
+  type: string
+  enum:
+  - good
+  - bad
+  - n/a
+status_description:
+  name: status_description
+  description: |
+    Freeform text description of noise or artifact affecting data quality on the channel.
+    It is meant to explain why the channel was declared bad in `[status]`.
+  type: string
+stim_file:
+  name: stim_file
+  description: |
+    Represents the location of the stimulus file (such as an image, video, or
+    audio file) presented at the given onset time.
+    There are no restrictions on the file formats of the stimuli files,
+    but they should be stored in the `/stimuli` folder
+    (under the root folder of the dataset; with optional subfolders).
+    The values under the `stim_file` column correspond to a path relative to
+    `/stimuli`.
+    For example `"images/cat03.jpg"` will be translated to `"/stimuli/images/cat03.jpg"`.
+  type: string
+  format: stimuli_relative
+strain:
+  name: strain
+  description: |
+    For species different from `homo sapiens`, string value indicating
+    the strain of the species, for example: `C57BL/6J`.
+  type: string
+strain_rrid:
+  name: strain_rrid
+  description: |
+    For species different from `homo sapiens`, research resource identifier
+    ([RRID](https://scicrunch.org/resources/Organisms/search))
+    of the strain of the species, for example: `RRID:IMSR_JAX:000664`.
+  type: string
+  format: rrid
+time:
+  name: time
+  description: |
+    Time, in seconds, relative to `TimeZero` defined by the `*_pet.json`.
+    For example, 5.
+  type: number
+  unit: s
+trial_type:
+  name: trial_type
+  description: |
+    Primary categorisation of each trial to identify them as instances of the
+    experimental conditions.
+    For example: for a response inhibition task, it could take on values "go" and
+    "no-go" to refer to response initiation and response inhibition experimental
+    conditions.
+  type: string
+trigger:
+  name: trigger
+  description: |
+    continuous measurement of the scanner trigger signal
+  type: number
+# type column in channels.tsv files
+type__channels:
+  name: type
+  description: |
+    Type of channel; MUST use the channel types listed below.
+    Note that the type MUST be in upper-case.
+  type: string
+  enum:
+  - MEGMAG
+  - MEGGRADAXIAL
+  - MEGGRADPLANAR
+  - MEGREFMAG
+  - MEGREFGRADAXIAL
+  - MEGREFGRADPLANAR
+  - MEGOTHER
+  - EEG
+  - ECOG
+  - SEEG
+  - DBS
+  - VEOG
+  - HEOG
+  - EOG
+  - ECG
+  - EMG
+  - TRIG
+  - AUDIO
+  - PD
+  - EYEGAZE
+  - PUPIL
+  - MISC
+  - SYSCLOCK
+  - ADC
+  - DAC
+  - HLU
+  - FITERR
+  - OTHER
+# type column for electrodes.tsv files
+type__electrodes:
+  name: type
+  description: |
+    Type of the electrode (for example, cup, ring, clip-on, wire, needle).
+  type: string
+units:
+  name: units
+  description: |
+    Physical unit of the value represented in this channel,
+    for example, `V` for Volt, or `fT/cm` for femto Tesla per centimeter
+    (see [Units](/02-common-principles.html#units)).
+  type: string
+  format: unit
+value:
+  name: value
+  description: |
+    Marker value associated with the event (for example, the value of a TTL
+    trigger that was recorded at the onset of the event).
+  anyOf:
+  - type: number
+  - type: string
+volume_type:
+  name: volume_type
+  description: |
+    The `*_aslcontext.tsv` table consists of a single column of labels identifying
+    the `volume_type` of each volume in the corresponding `*_asl.nii[.gz]` file.
+  type: string
+  enum:
+  - control
+  - label
+  - m0scan
+  - deltam
+  - cbf
+whole_blood_radioactivity:
+  name: whole_blood_radioactivity
+  description: |
+    Radioactivity in whole blood samples,
+    in unit of radioactivity measurements in whole blood samples (for example, `"kBq/mL"`).
+  type: number
+x:
+  name: x
+  description: |
+    Recorded position along the x-axis.
+  type: number
+y:
+  name: y
+  description: |
+    Recorded position along the y-axis.
+  type: number
+z:
+  name: z
+  description: |
+    Recorded position along the z-axis.
+  anyOf:
+  - type: number
+  - type: string
+    enum:
+    - n/a
diff --git a/tools/mkdocs_macros_bids/macros.py b/tools/mkdocs_macros_bids/macros.py
index 9a3cf15cc2..2cfa5e4b78 100644
--- a/tools/mkdocs_macros_bids/macros.py
+++ b/tools/mkdocs_macros_bids/macros.py
@@ -5,8 +5,8 @@
 code_path = os.path.abspath(os.path.join(os.path.dirname(__file__), ".."))
 sys.path.append(code_path)
 
-from schemacode import schema, utils
 from examplecode import example
+from schemacode import schema, utils
 
 
 def make_filename_template(**kwargs):
@@ -115,6 +115,31 @@ def make_metadata_table(field_info):
     return table
 
 
+def make_columns_table(column_info):
+    """Generate a markdown table of TSV column information.
+
+    Parameters
+    ----------
+    column_info : dict
+        A list of the column names.
+        Column names correspond to filenames in the "columns" folder of the
+        schema.
+        Until requirement levels can be codified in the schema,
+        this argument will be a dictionary, with the column names as keys and
+        the requirement levels as values.
+
+    Returns
+    -------
+    table : str
+        A Markdown-format table containing the corresponding table for
+        the requested columns.
+    """
+    schemapath = utils.get_schema_path()
+    schema_obj = schema.load_schema(schemapath)
+    table = schema.make_columns_table(schema_obj, column_info)
+    return table
+
+
 def make_filetree_example(filetree_info, use_pipe=True):
     """Generate a filetree snippet from example content.
 
diff --git a/tools/mkdocs_macros_bids/main.py b/tools/mkdocs_macros_bids/main.py
index 05ec392201..8db94a0411 100644
--- a/tools/mkdocs_macros_bids/main.py
+++ b/tools/mkdocs_macros_bids/main.py
@@ -37,4 +37,5 @@ def define_env(env):
     )
     env.macro(macros.make_suffix_table, "MACROS___make_suffix_table")
     env.macro(macros.make_metadata_table, "MACROS___make_metadata_table")
+    env.macro(macros.make_columns_table, "MACROS___make_columns_table")
     env.macro(macros.make_filetree_example, "MACROS___make_filetree_example")
diff --git a/tools/schemacode/schema.py b/tools/schemacode/schema.py
index daa9011a83..f4ec722d69 100644
--- a/tools/schemacode/schema.py
+++ b/tools/schemacode/schema.py
@@ -604,3 +604,74 @@ def make_metadata_table(schema, field_info, tablefmt="github"):
     # Print it as markdown
     table_str = tabulate(df, headers="keys", tablefmt=tablefmt)
     return table_str
+
+
+def make_columns_table(schema, column_info, tablefmt="github"):
+    """Produce columns table (markdown) based on requested fields.
+
+    Parameters
+    ----------
+    schema : dict
+        The BIDS schema.
+    column_info : dict of strings or tuples
+        A dictionary mapping column names to requirement levels in the
+        rendered columns table.
+        The dictionary values may be strings, in which case the string
+        is the requirement level information, or two-item tuples of strings,
+        in which case the first string is the requirement level information
+        and the second string is additional table-specific information
+        about the column that will be appended to the column's base
+        definition from the schema.
+    tablefmt : string, optional
+        The target table format. The default is "github" (GitHub format).
+
+    Returns
+    -------
+    table_str : str
+        The tabulated table as a Markdown string.
+    """
+    fields = list(column_info.keys())
+    # The filter function doesn't work here.
+    column_schema = schema["objects"]["columns"]
+
+    retained_fields = [f for f in fields if f in column_schema.keys()]
+    dropped_fields = [f for f in fields if f not in column_schema.keys()]
+    if dropped_fields:
+        print("Warning: Missing fields: {}".format(", ".join(dropped_fields)))
+
+    # Use the "name" field in the table, to allow for filenames to not match
+    # "names".
+    df = pd.DataFrame(
+        index=[column_schema[f]["name"] for f in retained_fields],
+        columns=["**Requirement Level**", "**Data type**", "**Description**"],
+    )
+    df.index.name = "**Column name**"
+    for field in retained_fields:
+        field_name = column_schema[field]["name"]
+        requirement_info = column_info[field]
+        description_addendum = ""
+        if isinstance(requirement_info, tuple):
+            requirement_info, description_addendum = requirement_info
+
+        requirement_info = requirement_info.replace(
+            "DEPRECATED",
+            "[DEPRECATED](/02-common-principles.html#definitions)",
+        )
+
+        type_string = utils.resolve_metadata_type(column_schema[field])
+
+        description = (
+            column_schema[field]["description"] + " " + description_addendum
+        )
+        # A backslash before a newline means continue a string
+        description = description.replace("\\\n", "")
+        # Two newlines should be respected
+        description = description.replace("\n\n", "<br>")
+        # Otherwise a newline corresponds to a space
+        description = description.replace("\n", " ")
+
+        df.loc[field_name] = [requirement_info, type_string, description]
+
+    # Print it as markdown
+    table_str = tabulate(df, headers="keys", tablefmt=tablefmt)
+    return table_str