We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At OHBM we already had a few questions about how one should encode parameter
For the moment we allow passing any json-compliant values into the attributes field of an Activity
attributes
Activity
We should not encode parameters, but provide a way to encode parameters My Suggestion is that we define a new type name Parameter
Parameter
new_features.md
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Update proposal for BIDS Prov (BEP028)
Problem Statement
At OHBM we already had a few questions about how one should encode parameter
For the moment we allow passing any json-compliant values into the
attributes
field of anActivity
We should not encode parameters, but provide a way to encode parameters
My Suggestion is that we define a new type name
Parameter
Checklist
new_features.md
at the root of this projectThe text was updated successfully, but these errors were encountered: