BEP038: Atlas examples

[effigies]

This branch implements examples according to bids-standard/bids-specification#1714 (rendered: https://bids-specification--1714.org.readthedocs.build/en/1714/).

Please make PRs against the bep038 branch, and we will merge this PR as a part of merging BEP038.

xref bids-standard/bids-validator#288

[oesteban]

• atlas-*_description.json does not currently have a file rule. From reading the BEP, it looks like it can occur at any level of the hierarchy, which is not possible with the current structure of file rules. Is it problematic to require it to be found at the dataset root?

I don't think this should be a problem.

• *_dseg.tsv need to be non-empty files.

Gotcha, will give them content.

• *_stat-confidence_* - The stat entity is not defined.

desc then?

[effigies]

• *_stat-confidence_* - The stat entity is not defined.

desc then?

Sounds good to me.

[CPernet]

I have added an example for an atlas we made, and want to distribute - this is thus a dataset. I think this is correct ?? I can see some redundancy between the dataset_description.json and the atlas-ONPNeuroMarkflorbetapir_description.json what do you guys think? @oesteban @effigies

[tsalo]

I have this empty because the SpatialReference depends on the resolution and this atlas is available in res-01 and res-02. Also, the SpatialReference should be present in the individual sidecar JSONs.

[tsalo]

This isn't in the BEP or the spec, but it seems like we should have something like it.