-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulling and managing versions of the schema #2
Comments
Version of schema indeed should be the one of the schema used from bids-specification. Version of the library. - a different matter, and more over library ideally should support multiple versions of the schema, and use the one specified in the dataset. |
By "library" do you mean
I agree that |
By library I meant pybids-light . |
My assumption is that any dataset that was valid for any version >= 1.0.0 should be valid now, with the caveat that there may be deprecation warnings. I wasn't involved with BIDS from the start, though, so I'm not actually that familiar with changes made pre-1.2.0 or so. It could be that backwards-incompatible changes were made back then. |
Ultimately, we will want to have the schema versioned, so you can run
pybids-light
with different rules based on which version you're using, but that won't be very important until BIDS 2.0 starts going. I'm comfortable avoiding the version question until later, but we should figure out how we want to pull the schema. Should we just grab frombids-specification
's main branch?The text was updated successfully, but these errors were encountered: