I wonder if there is

• a summary of divergences from BIDS (e.g. new entities like _date and _software) with argumentation for their necessity?
• why/where BEP032 (https://bids.neuroimaging.io/bep032) is not fulfilling the use cases you have?
• as BIDS becomes more and more schema driven -- would it be feasible to express all (most?) of divergences within schema fork and thus still benefit from e.g. schema-driven bids-validator? (to a degree we did that in early days of schema for DANDI archive while keeping a fork of schema with new entities added and specifying "custom" version of BIDS for that schema so schematools validator could work on it)
• any desires for a potential BIDS 2.0 which could help bridge the gap between BIDS and NeuroBlueprint? may be some of them already listed on https://github.com/bids-standard/bids-2-devel ? e.g.
  • Make it possible to specify folders layout to be other than sub-{label}/[ses-{label}/] bids-standard/bids-2-devel#54

Thanks in advance!