BEP update

[franklin-feingold]

Hey BEP028!

Happy new year! I am opening up this issue to inquire if you all may have a status update to share? These updates are shared on our website. I have included a couple points to guide the update.

BEP status update:

1. Status update on BEP 028
2. Sharing the blocking items or sticking points
3. Items left to discuss and clarify

Thank you!

[cmaumet]

Hi @franklin-feingold,

Here is an update prepared with @satra and @remiadon:

Status update on BEP 028

BEP is being actively developed. BEP-related discussions happen in the dedicated BEP028 Github repository and BEP contributors meet once a month as part of the NIDM group meeting (see how to join here). A set of examples and user stories are currently being refined.

Sharing the blocking items or sticking points

The potential scope of provenance is large. A list of priorities for users and developers will narrow this down to things we can address given the current resources.

Items left to discuss and clarify

A set of examples is currently being refined. Our next goal is to converge on a set of user stories by priorities so that the model can be developed with those in mind. We are aiming to do a poll for the BIDS community to address this and also to engage more contributors.

Thanks!

[franklin-feingold]

hi @cmaumet (@satra and @remiadon)

Thank you for your update - all sounds great!

[franklin-feingold]

hi @cmaumet @satra @remiadon

I hope you all are doing well! I am writing over to inquire about potential updates to your BIDS BEP’s progress. These updates are intended to keep us coordinated and are shared publicly on our website. I have included a couple points below to guide the update.

BEP status update points:

• Status update on BEP 028
• Sharing the blocking items or sticking points
• Items left to discuss and clarify

[remiadon]

@franklin-feingold thank you for this !

[franklin-feingold]

hi @cmaumet @satra @remiadon

Happy new year and hope this email finds you well! I am writing over to further inquire about potential updates on your progress. Similar to last time, I have included a couple of points below to guide the update.

BEP status update points:

• Status update on BEP 028
• Sharing the blocking items or sticking points
• Items left to discuss and clarify

Thank you!

[cmaumet]

Hi @franklin-feingold ! Thanks for reaching out.

We are currently in a phase of internal review of the specification and should have a clearer idea on timeline in 2 weeks.

Our aim is to open the specification for community review very soon 🎉

[franklin-feingold]

hi @cmaumet !

I apologize for my delayed response - but sounds great! Once you have a clearer timeline, may you please email over to me so we can start discussing plans for moving forward!