You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/bids-standard/bids-specification/tree/master/src/schema now (thanks to @tsalo for leading the effort) is now providing a machine readable specification sufficient to validate file paths and basic structure. We should start working on formalizing that specification possible serialization(s) so they would be exported across all versions of BIDS in https://github.com/bids-standard/bids-schema and also possibly in a form most useful to be used by the tools such as bids-validator (see e.g. bids-standard/bids-schema#2). Having formalized serializations across different versions of BIDS could elevate many needs for hardcoding in bids-validator, and also make its reports bids version specific (with hints on what would change whenever validating against current released version etc)
The text was updated successfully, but these errors were encountered:
https://github.com/bids-standard/bids-specification/tree/master/src/schema now (thanks to @tsalo for leading the effort) is now providing a machine readable specification sufficient to validate file paths and basic structure. We should start working on formalizing that specification possible serialization(s) so they would be exported across all versions of BIDS in https://github.com/bids-standard/bids-schema and also possibly in a form most useful to be used by the tools such as bids-validator (see e.g. bids-standard/bids-schema#2). Having formalized serializations across different versions of BIDS could elevate many needs for hardcoding in bids-validator, and also make its reports bids version specific (with hints on what would change whenever validating against current released version etc)
The text was updated successfully, but these errors were encountered: