Skip to content

Commit

Permalink
RF: use "specification" not "protocol" to refer to BIDS
Browse files Browse the repository at this point in the history
Even the repository is bids-specification
  • Loading branch information
yarikoptic authored and sappelhoff committed Mar 4, 2019
1 parent 9e3b150 commit d90b454
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/02-common-principles.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
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.
Throughout this specification we use a list of terms. To avoid
misunderstanding we clarify them here.

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
Expand Down Expand Up @@ -40,7 +40,7 @@ clarify them here.

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
complexity. For the purpose of this specification 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 behaviors (with different
Expand Down

0 comments on commit d90b454

Please sign in to comment.