Skip to content
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

Literature citations #36

Closed
Lestropie opened this issue Nov 22, 2021 · 2 comments
Closed

Literature citations #36

Lestropie opened this issue Nov 22, 2021 · 2 comments

Comments

@Lestropie
Copy link
Collaborator

Note that this Issue is not of the same criticality as the other entries in #29, but I do nevertheless think it warrants conversation with invested parties outside of BEP016 development.

The current state of BEP016 has many literature citations, corresponding primarily to publications where various diffusion models are introduced. There is however, as far as I can see, no precedent for such set in the existing BIDS specification. Therefore do we:

  1. Omit literature citations entirely from the specification;

  2. Decide on and set a precedent regarding how such citations will be included in the specification documentation (I'm not aware of capabilities of Markdown in this respect so am deferring to expertise from others).

@Lestropie
Copy link
Collaborator Author

Note that there are literature citations within some parts of the specification, mostly inline with URLs included in the main text. So if handling of literature citations within the specification were to be changed, then I expect that the BIDS maintainers would prefer that an explicit PR be created with the specific purpose of changing the way that citations are handled, rather than that change being bundled in a modality-specific BEP.

@Lestropie
Copy link
Collaborator Author

In #92, explicit definition of reserved values for the "_param-" entity have been removed. A consequence of this is that citation of literature articles within the specification have been removed. To get back some lost ground I'm proposing in #101 having the ability to define for each parameter map file a URL that describes that one parameter. That is more extensible than having such baked into the specification. So I'm closing this as obsolete. If someone wishes to make a case subsequent to #92 either to have some mechanism by which to define citations in the specification for any reason, and/or to have reserved "_param-" values, that should be raised as a new Issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant