Stefan Appelhoff

Should probably be fixed here: https://github.com/mne-tools/mne-bids/blob/0b1a61d7660b35438b78898878ef0c8b51d8716b/mne_bids/read.py#L621 - to take into account: https://github.com/mne-tools/mne-bids/pull/1106

to be merged before continuing work here: - [x] https://github.com/JuliusWelzel/bids-specification/pull/5 (and `git pull` locally, before continuing work after that PR has been merged)

> Some fields (for example [SubjectArtifactDescription](https://bids-specification.readthedocs.io/en/stable/glossary.html#objects.metadata.SubjectArtefactDescription) are used in this BEP. The description from the schema can be misleading sometimes, adding a description_addendum only helps in some cases. Is there...

> As it currently reads, it seems that it's just two names for identical strings. If it's a required entity, then why duplicate it in the metadata? My initial thought...

open points: - [x] moving tracksys entity up in the ordering (before `run`) - [x] last point from [here](https://github.com/bids-standard/bids-specification/pull/981#issuecomment-1436564049)

closed in #981

> for anyone who may get involved in the release of the specs, I can give you a tour of what this does if you are interested (also to increase...

Just a note that on the ["recent contributors" WIKI](https://github.com/bids-standard/bids-specification/wiki/Recent-Contributors), where contributors are supposed to enter their details, it currently says: ``` - name: - contributions: - email (optional): - github...

> Let me know if you think we need more. I added an email they should write to ([email protected], which gets redirected to anyone who has access to the account...

> Are we sure that if we do that we will keep the same generic DOI? Should we ask zenodo in advance to see if some DOI magic needs to...