From c4ee8d68cdff253055f86ed82c3992de8562bd35 Mon Sep 17 00:00:00 2001 From: Oscar Esteban Date: Mon, 25 Mar 2024 13:58:08 +0100 Subject: [PATCH] enh: harmonize with motion specs see https://github.com/bids-standard/bids-specification/pull/1749#issuecomment-2017854619 --- src/common-principles.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/src/common-principles.md b/src/common-principles.md index 5e638404d8..156546b982 100644 --- a/src/common-principles.md +++ b/src/common-principles.md @@ -430,16 +430,22 @@ NIfTI header. ### Tabular files -Tabular data MUST be saved as plain-text, tab-delimited values (`.tsv`) files, +Tabular data MUST be saved as plain-text, tab-delimited values (TSV) files +(with [extension `.tsv`](glossary.md#tsv-extensions)), that is, CSV files where commas are replaced by tab characters. Tabs MUST be true tab characters and MUST NOT be a series of space characters. Tabular data containing large numbers of rows MAY be saved as [compressed tabular files (with extension `.tsv.gz`)](#compressed-tabular-files) as prescribed below. Each TSV file MUST start with a header line listing the names of all columns -with the exception of [compressed tabular files](#compressed-tabular-files) -where column names are defined in a sidecar metadata -[JSON object](https://www.json.org/json-en.html) described below. +with two exceptions: + +1. [compressed tabular files](#compressed-tabular-files), + for which column names are defined in a sidecar metadata + [JSON object](https://www.json.org/json-en.html) described below; and +1. [motion recording data](modality-specific-files/motion.md), + which use plain-text TSV and columns are defined as described + in its corresponding of the specifications. It is RECOMMENDED that the column names in the header of the TSV file are written in [`snake_case`](https://en.wikipedia.org/wiki/Snake_case) with the