Skip to content

2024 03 21 steering group minutes

Topic Relevant Links and to do
Guest Franco Pestilli
Cooperation with DICOM standard

YOH pointed David Clunie to our DICOMs deficits table , he forwarded to WG-16 to consider at the next meeting March Wed 13th, 2024.

BIDS 2.0 going forward!
BEP guidelines updating (Camille & Rémi)

https://github.com/bids-standard/bids-extensions/pull/28

See Oscar’s vision of having BEP leads as core experts of BIDS and other domain expert be contributors (i.e. not lead BEPs) https://github.com/bids-standard/bids-extensions/pull/28#discussion_r1528721354

BEP guidelines PR on technical committee https://github.com/bids-standard/bids-extensions/pull/29

Unsticking BEPs (may be covered by previous topics). Maintainer suggestions:

  1. Steering directly mediate conflicts

  2. "BEP delegates" a la Python

Rough consensus: Resolve first, formalize process later

Present: Kim Ray, Camille Maumet, Yarik Halchenko, Ariel Rokem, Chris Markiewicz, Dora Hermes

Guest: Franco Pestilli

BIDS Meeting Notes

Franco is sick, so meeting with him deferred to future meeting (possibly next time, April 4th)

Cooperation with DICOM standard

YOH met with them to discuss issues between BIDS and DICOM

  • Dicom cannot enforce anything, and its difficult for them to suddenly make things mandatory

  • YOH will meet with GE manufacturer this Fri to discover more about "IHE Sharazone", which is a system that the vendors use to share example data between them to check for compatibility across. It seems that this is rather closed down, so hard to access and contribute to.

  • Overall, the call useful in the context that DICOM folks are now more aware of incompatibilities between BIDS and DICOM

BIDS 2.0 going forward!

YOH

  • A replacement/substitution of inheritance principles would be useful (allows you to define common metadata at the top level and more specific metadata at lower levels)

  • Discusses formalizing common principles into a standard

  • Might want to reach out to [PsychDS] to create a migration path

  • For example: Allen institute has a file naming schema that we might want to adopt/incorporate

  • Please add examples to this issue for consideration (issue 62?)

BEP guidelines updating (Camille & Rémi)

  • Update the process of how people can submit new proposals for BEPS

  • The process of obtaining a BEP number is not clearly outlined

  • The expectation to 'become familiar' with BIDS before starting a BEP is a 'high bar' to attain

    • Some believe that BEP leads should be BIDS experts and domain experts should be contributors

      • Concerns exist that this approach may limit entrance to BIDS

  • Suggestions - adopt a procedure similar to debian where experts need to pass an exam to obtain an expert status

    • Should a BEP lead already be a BIDS contributor to ensure they have some existing BIDS knowledge

  • Often BEP leads are already BIDS familiar because of the steps that they need to create the BEP

    • Create BIDS examples in a pull request
    • Add to schema
    • However sometimes this familiarity is a result of going through the BEP creation process

  • CM: Current loose guidelines for establishing a BEP

    • Maintainers have a template that they provide to individuals that are interested in creating a BEP, often the maintainers ensure that the BEP lead has contributed to BIDS previously.
    • There has also been some approval by the steering committee
    • Currently, BIDS maintainers are not comfortable with the new expectation that they help 'solve' many BIDS issues/concerns (instead of the community agree on solutions)

  • The committee returns to the idea of having a BEP mentor for each BEP that has BIDS/BEP experience and can help guide the BEP lead through the BEP process

    • This could reduce zombie BEPs (when a BEP is forgotten or not actively being developed)
    • Could also help with junior people contributing and potentially becoming BEP leads

  • Should there be a google doc or pull request first for a BEP?