Short description of overarching theme/goals behind BIDS 2.0 . To make BIDS

• more flexible as capable to accommodate new fields of neuroscience and use cases and possibly avoid breeding of "BIDS-like" offsprings
  • Use-cases:
    • Use-case(s): BIDS-inspired/like standards #62
    • Use-case: AIND schema #60
• more consistent:
  • added from below by @tsalo: address any inconsistencies or inefficiencies that we had to incorporate into BIDS to maintain backwards compatibility. For example:
    • dropping either IntendedFor or B0FieldIdentifier/B0FieldSource,
    • removing deprecated elements like the phase suffix,
    • and addressing how space is used inconsistently across modalities.
  • see issues labeled with "deprecation" (most should get addressed)
  • see issues labeled with "consistency" (many should get addressed)
• more modular
  • see issues labeled with "modularity" (some should get addressed)
• more tools-friendly
  • even more assumptions should migrate from human written documentation into machine-readable form (schema, and auxilary metadata, such as DatasetType etc)
• more user-friendly
  • largely via "more consistent"
  • some rules could be relaxed or made more stringent to again reduce ambiguity
• easy to adopt/migrate to: analogy could be "python 2 to 3 migration" -
  • it should largely remain the same
  • "migration" helper should be provided to automagically upgrade from 1.x to 2.x. Ref: Develop bids-migration script #67 .

With that in mind, not all issues in this repository will be approached for 2.0. Please vote with 👍 or 👎 on existing issues