Skip to content

Commit 6d3bbea

Browse files
agahkarakuzusappelhoff
agahkarakuzu
authored and
sappelhoff
committed
Address suggestions by @tsalo 
1 parent bcb0223 commit 6d3bbea

2 files changed

Lines changed: 12 additions & 11 deletions

File tree

‎src/02-common-principles.md‎

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -161,19 +161,20 @@ A summary of all entities in BIDS and the order in which they MUST be
161161
specified is available in the [entity table](./99-appendices/04-entity-table.md)
162162
in the appendix.
163163

164-
### Parametrically linked file collections
164+
### Entity-linked file collections
165165

166166
A set of files that are related to each other based on a repetitive acquisition of
167-
sequential data by changing acquisition parameters one (or multiple) at a time.
168-
The suffix serves as an identifier for these collections, holding a logical grouping
169-
of constituent files.
167+
sequential data by changing acquisition parameters one (or multiple) at a time and/or by
168+
being inherent components of the same data. The suffix serves as an identifier for these
169+
collections, holding a logical grouping of constituent files.
170170
Within each collection, files MUST be distinguished from each other by at least one
171171
entity (e.g., `echo`) that corresponds to an altered acquisition parameter (e.g.,
172-
`EchoTime`). Note that these entities MUST be described by the specification and the
173-
parameter changes they declare SHOULD NOT invalidate the definition of the accompanying
174-
suffix. For example, the use of the `echo` entity along with the `T1w` suffix casts doubt on
175-
the validity of the identified contrast weighting.
176-
Provided the conditions above are satisfied, any suffix (e.g. `bold`) can identify a parametrically linked file collection, although certain suffixes are exclusive for this purpose (e.g., `MP2RAGE`).
172+
`EchoTime`) or that defines a component relationship (e.g., `part`). Note that these entities
173+
MUST be described by the specification and the parameter changes they declare SHOULD NOT invalidate
174+
the definition of the accompanying suffix. For example, the use of the `echo` entity along with the
175+
`T1w` suffix casts doubt on the validity of the identified contrast weighting.
176+
Provided the conditions above are satisfied, any suffix (e.g. `bold`) can identify an entity-linked file
177+
collection, although certain suffixes are exclusive for this purpose (e.g., `MP2RAGE`).
177178
All the use cases concerning this convention are RECOMMENDED to be included in the [file collections](./99-appendices/10-file-collections.md) appendix for clarity. This convention is mainly intended for but not
178179
limited to MRI modalities.
179180

‎src/99-appendices/10-file-collections.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Appendix X: File collections
22

3-
To give context to the use of [parametrically linked file collections](./02-common-principles.md#file-name-structure), applications appealing to this common
4-
principle are listed by descriptive tables under their respective modalities.
3+
To give context to the use of [entity-linked file collections](./02-common-principles.md#file-name-structure), applications concerned with this
4+
common principle are listed by descriptive tables under their respective modalities.
55

66
## Magnetic Resonance Imaging
77

0 commit comments

Comments
 (0)