[FIX] number of small corrections to the specification

CHANGES.md

@@ -10,7 +10,7 @@ CapManufacturersModelName.
 -   Remove EEGSamplingFrequency and ManufacturersAmplifierModelName
 from the meg.json.
 
--   Improved the behavioural data description.
+-   Improved the behavioral data description.
 
 1.1.0
 
@@ -71,7 +71,7 @@ from the meg.json.
 -   Added trial_type column to the event files.
 
 -   Added missing sub-<participant_label> in
-   behavioural data file names
+   behavioral data file names
 
 -   Added ability to store stimuli files.
 

mkdocs.yml

@@ -14,7 +14,7 @@ nav:
         - Magnetoencephalography: 04-modality-specific-files/02-magnetoencephalography.md
         - Task events: 04-modality-specific-files/03-task-events.md
         - Physiological and other continous recordings: 04-modality-specific-files/04-physiological-and-other-continous-recordings.md
-        - Behavioral experiments (with no MRI): 04-modality-specific-files/05-behavioural-experiments.md
+        - Behavioral experiments (with no MRI): 04-modality-specific-files/05-behavioral-experiments.md
       - Longitudinal and multi-site studies: 05-longitudinal-and-multi-site-studies.md
       - Extending the BIDS specification: 06-extensions.md
       - Appendix:

src/01-introduction.md

@@ -8,7 +8,7 @@ obtained in neuroimaging experiments. Even two researchers working in the same
 lab can opt to arrange their data in a different way. Lack of consensus (or a
 standard) leads to misunderstandings and time wasted on rearranging data or
 rewriting scripts expecting certain structure. Here we describe a simple and
-easy-to-adopt way of organising neuroimaging and behavioural data. By using this
+easy-to-adopt way of organising neuroimaging and behavioral data. By using this
 standard you will benefit in the following ways:
 
 -   It will be easy for another researcher to work on your data. To understand

src/02-common-principles.md

@@ -9,13 +9,13 @@ interpreted as described in [[RFC2119](https://www.ietf.org/rfc/rfc2119.txt)].
 Throughout this protocol we use a list of terms. To avoid misunderstanding we
 clarify them here.
 
-1.  Dataset - a set of neuroimaging and behavioural data acquired for a purpose
+1.  Dataset - a set of neuroimaging and behavioral data acquired for a purpose
     of a particular study. A dataset consists of data acquired from one or more
     subjects, possibly from multiple sessions.
 
 1.  Subject - a person or animal participating in the study.
 
-1.  Session - a logical grouping of neuroimaging and behavioural data consistent
+1.  Session - a logical grouping of neuroimaging and behavioral data consistent
     across subjects. Session can (but doesn't have to) be synonymous to a visit
     in a longitudinal study. In general, subjects will stay in the scanner
     during one session. However, for example, if a subject has to leave the
@@ -33,17 +33,17 @@ clarify them here.
     scanning sequence/protocol.
 
 1.  Data type - a functional group of different types of data. In BIDS we define
-    five data types: func (task based and resting state functional MRI), dwi
+    six data types: func (task based and resting state functional MRI), dwi
     (diffusion weighted imaging), fmap (field inhomogeneity mapping data such as
     field maps), anat (structural imaging such as T1, T2, etc.), meg
-    (magnetoencephalography).
+    (magnetoencephalography), beh (behavioral).
 
 1.  Task - a set of structured activities performed by the participant. Tasks
     are usually accompanied by stimuli and responses, and can greatly vary in
     complexity. For the purpose of this protocol we consider the so-called
     “resting state” a task. In the context of brain scanning, a task is always
     tied to one data acquisition. Therefore, even if during one acquisition the
-    subject performed multiple conceptually different behaviours (with different
+    subject performed multiple conceptually different behaviors (with different
     sets of instructions) they will be considered one (combined) task.
 
 1.  Event - a stimulus or subject response recorded during a task. Each event
@@ -128,13 +128,13 @@ participant can exist only at participant level directory, i.e
 specific to a participant is to be declared only at top level of dataset for eg:
 `task-sist_bold.json` must be placed under `/dataset/task-sist_bold.json`
 
-Example 1: Two JSON files at same level that are applicable for NIfTI file.
+Example 1: Two JSON files that are erroneously at the same level.
 
 ```Text
 sub-01/
     ses-test/
-        sub-test_task-overtverbgeneration_bold.json
-        sub-test_task-overtverbgeneration_run-2_bold.json
+        sub-01_ses-test_task-overtverbgeneration_bold.json
+        sub-01_ses-test_task-overtverbgeneration_run-2_bold.json
         anat/
             sub-01_ses-test_T1w.nii.gz
         func/
@@ -146,8 +146,8 @@ In the above example, two JSON files are listed under `sub-01/ses-test/`, which
 are each applicable to
 `sub-01_ses-test_task-overtverbgeneration_run-2_bold.nii.gz`, violating the
 constraint that no more than one file may be defined at a given level of the
-directory structure. Instead `task-overtverbgeneration_run-2_bold.json` should
-have been under `sub-01/ses-test/func/`.
+directory structure. Instead `sub-01_ses-test_task-overtverbgeneration_run-2_bold.json`
+should have been under `sub-01/ses-test/func/`.
 
 Example 2: Multiple run and rec with same acquisition (acq) parameters acq-test1
 
@@ -168,7 +168,7 @@ apply to different runs and rec files. Also if the JSON file
 (`task-xyz_acq-test1_bold.json`) is defined at dataset top level directory, it
 will be applicable to all task runs with `test1` acquisition parameter.
 
-Case 2: Multiple json files at different levels for same task and acquisition
+Example 3: Multiple json files at different levels for same task and acquisition
 parameters
 
 ```Text
@@ -198,12 +198,10 @@ possible. Since the NIfTI standard offers limited support for the various image
 acquisition parameters available in DICOM files, we RECOMMEND that users provide
 additional meta information extracted from DICOM files in a sidecar JSON file
 (with the same filename as the `.nii[.gz]` file, but with a `.json` extension).
-Extraction of BIDS compatible metadata can be performed using dcm2nii
-[https://www.nitrc.org/projects/dcm2nii/](https://www.nitrc.org/projects/dcm2nii/)
-and dicm2nii
-[http://www.mathworks.com/matlabcentral/fileexchange/42997-dicom-to-nifti-converter/content/dicm2nii.m](http://www.mathworks.com/matlabcentral/fileexchange/42997-dicom-to-nifti-converter/content/dicm2nii.m)
+Extraction of BIDS compatible metadata can be performed using [dcm2nii](https://www.nitrc.org/projects/dcm2nii/)
+and [dicm2nii](http://www.mathworks.com/matlabcentral/fileexchange/42997-dicom-to-nifti-converter/content/dicm2nii.m)
 DICOM to NIfTI converters. A provided
-validator[https://github.com/INCF/bids-validator](https://github.com/INCF/bids-validator)
+[validator](https://github.com/bids-standard/bids-validator)
 will check for conflicts between the JSON file and the data recorded in the
 NIfTI header.
 
@@ -262,12 +260,11 @@ Example:
 ## Key/value files (dictionaries)
 
 JavaScript Object Notation (JSON) files MUST be used for storing key/value
-pairs. Extensive documentation of the format can be found here:
+pairs. JSON files MUST be in UTF-8 encoding. Extensive documentation of the format can be found here:
 [http://json.org/](http://json.org/). Several editors have built-in support for
 JSON syntax highlighting that aids manual creation of such files. An online
 editor for JSON with built-in validation is available at:
-[http://jsoneditoronline.org](http://jsoneditoronline.org). JSON files MUST be
-in UTF-8 encoding.
+[http://jsoneditoronline.org](http://jsoneditoronline.org). 
 
 Example:
 

src/03-modality-agnostic-files.md

@@ -173,7 +173,7 @@ decreased. Dates that are shifted for anonymization purposes should be set to a
 year 1900 or earlier to clearly distinguish them from unmodified data. Shifting
 dates is recommended, but not required.
 
-Additional fields can include external behavioural measures relevant to the
+Additional fields can include external behavioral measures relevant to the
 scan. For example vigilance questionnaire score administered after a resting
 state scan.
 

src/04-modality-specific-files/02-magnetoencephalography.md

@@ -76,7 +76,7 @@ Whenever possible, please avoid using ad-hoc wording.
 | ManufacturersModelName | RECOMMENDED. Manufacturer’s designation of the MEG scanner model (e.g. `CTF-275`). See [Appendix VII](../99-appendices/07-meg-systems.md) with preferred names                                                                                                                  |
 | SoftwareVersions       | RECOMMENDED. Manufacturer’s designation of the acquisition software.                                                                                                                                                                                                            |
 | TaskDescription        | RECOMMENDED. Description of the task.                                                                                                                                                                                                                                           |
-| Instructions           | RECOMMENDED. Text of the instructions given to participants before the scan. This is not only important for behavioural or cognitive tasks but also in resting state paradigms (e.g. to distinguish between eyes open and eyes closed).                                         |
+| Instructions           | RECOMMENDED. Text of the instructions given to participants before the scan. This is not only important for behavioral or cognitive tasks but also in resting state paradigms (e.g. to distinguish between eyes open and eyes closed).                                         |
 | CogAtlasID             | RECOMMENDED. URL of the corresponding [Cognitive Atlas](http://www.cognitiveatlas.org/) term that describes the task (e.g. Resting State with eyes closed "[http://www.cognitiveatlas.org/term/id/trm_54e69c642d89b](http://www.cognitiveatlas.org/term/id/trm_54e69c642d89b)") |
 | CogPOID                | RECOMMENDED. URL of the corresponding [CogPO](http://www.cogpo.org/) term that describes the task (e.g. Rest "[http://wiki.cogpo.org/index.php?title=Rest](http://wiki.cogpo.org/index.php?title=Rest)")                                                                        |
 | DeviceSerialNumber     | RECOMMENDED. The serial number of the equipment that produced the composite instances. A pseudonym can also be used to prevent the equipment from being identifiable, as long as each pseudonym is unique within the dataset.                                                   |

src/06-extensions.md

@@ -9,16 +9,14 @@ There are many ways to get involved with the BIDS community!
 ### The BIDS Starter Kit
 If you're new
 to the BIDS community and you'd like to learn a bit more, we recommend checking
-out the [BIDS Starter Kit]
-(https://github.com/bids-standard/bids-starter-kit/blob/master/README.md).
+out the [BIDS Starter Kit](https://github.com/bids-standard/bids-starter-kit/blob/master/README.md).
 This has introductory information about the BIDS specification, tools in
 the BIDS ecosystem, and how you can get involved.
 
 ### The BIDS Contributor guide
 
 If you'd like to get involved more heavily in helping extend the BIDS
-specification or develop tools for it, see the [BIDS Contributor Guide]
-(https://docs.google.com/document/d/1pWmEEY-1-WuwBPNy5tDAxVJYQ9Een4hZJM06tQZg8X4/edit?usp%3Dsharing&sa=D&ust=1537468908724000). It contains more in-depth information for getting
+specification or develop tools for it, see the [BIDS Contributor Guide](https://docs.google.com/document/d/1pWmEEY-1-WuwBPNy5tDAxVJYQ9Een4hZJM06tQZg8X4/edit?usp%3Dsharing&sa=D&ust=1537468908724000). It contains more in-depth information for getting
 involved with the BIDS community.
 
 ## BIDS Extension Proposals
@@ -54,8 +52,14 @@ Below is a table of currently-active BEPs.
 | [BEP023](https://docs.google.com/document/d/1yzsd1J9GT-aA0DWhdlgNr5LCu6_gvbjLyfvYq2FuxlY) | [PET Preprocessing derivatives](https://docs.google.com/document/d/1yzsd1J9GT-aA0DWhdlgNr5LCu6_gvbjLyfvYq2FuxlY)                                                                              | Martin Noergaard, Graham Searle, Melanie Ganz                  |
 | [BEP024](https://docs.google.com/document/d/1fqnJZ18x5LJC8jiJ8yvPHUGFzNBZ6gW2kywYrUKWtuo) | [Computed Tomography scan (CT)](https://docs.google.com/document/d/1fqnJZ18x5LJC8jiJ8yvPHUGFzNBZ6gW2kywYrUKWtuo)                                                                              | Hugo Boniface                                                  |
 
-When an extension reaches maturity it is merged into the main body of the
-specification.
+When an extension reaches maturity it is merged into the main body of the specification.
+Below is a table of BEPs that have been merged in the main body of the specification.
+
+
+| Extension label                                                                           | Title                                                                                                           | Moderators/leads                                        |
+| :---------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------ |
+| [BEP008](https://docs.google.com/document/d/1FWex_kSPWVh_f4rKgd5rxJmxlboAPtQlmBc1gyZlRZM) | [Magnetoencephalography (MEG)](https://docs.google.com/document/d/1QwfHyBzOyFWOLO4u_kkojLpUhW0-4_M7Ubafu9Gf4Gg) | Guiomar Niso                                            |
+
 
 All of the extension ideas that are not backwards compatible and thus
 will have to wait for BIDS 2.0 are listed

src/99-appendices/01-contributors.md

@@ -22,7 +22,7 @@ Legend (source:
 | 🔧    | Tools                                                                       |
 | 🌍    | Translation                                                                 |
 | ⚠️    | Tests                                                                       |
-| ✅     | Tutorials                                                                   |
+| ✅    | Tutorials                                                                   |
 | 📢    | Talks                                                                       |
 | 📹    | Videos                                                                      |
 
@@ -86,7 +86,7 @@ your name is not listed, please add it.
 - Thomas E. Nichols 📖📢🔧
 - Dylan Nielson 📖💻🔧
 - Guiomar Niso 📖💡📢
-- Robert Oostenveld 📖🔧📢💡
+- Robert Oostenveld 📖🔧📢💡✅⚠️🤔
 - Patrick Park 📖💡💬
 - Dianne Patterson 📖
 - John Pellman 📖