-
Notifications
You must be signed in to change notification settings - Fork 159
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
[FIX] URI "definition" and recommendation #629
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
anything else but the DOIs that should change?
IMHO all JSON fields that contain URLs or DOIs. For example CogAtlasID
, which says:
source: table in https://bids-specification.readthedocs.io/en/latest/04-modality-specific-files/03-electroencephalography.html#sidecar-json-_eegjson
the big benefit would be that we can validate for URIs, see: bids-standard/bids-validator#1072
the drawback would be that probably so far people have been specifying DOIs either as a URL, or potentially using just the DOI without any prefixes.
But I could live with that drawback in order to make the spec better in the future. Could be considered a breaking change though 🤷♂️
This looks ready to go. Some changes are I think not problematic but some other I am much less sure about especially in the "higher level" files ("common principles" and "modality agnostic") as they could "break" things. Will add comments through the review panel. Once again will leave the linting as a last step when we agree content. |
One last question: that relates to the diversity of format we use to refer to papers in the specs themselves. There are a couple of links to some papers in the specs that use a URL rather than a DOI. Should those be changed? For example, should this:
be turned into this:
|
I think that'd be reasonable. And I think @yarikoptic would agree as well. See his comment: #403 (comment) |
Co-authored-by: Stefan Appelhoff <stefan.appelhoff@mailbox.org>
- refer to URI where relevant - update json examples accordingly
fix linter fix internal link target
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
However, we need other people to chime in about the potential breakage of now wanting our DOIs specified as URI in the from doi:thedoi
From a technical validation perspectives, only the datasets will break that specified the DOI as just thedoi
, because those that used https://doi.org/thedoi
still have a valid URI.
here's the link to previous discussion on this: #629 (comment)
src/04-modality-specific-files/04-intracranial-electroencephalography.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Stefan Appelhoff <stefan.appelhoff@mailbox.org>
revert changes to prevent conflicts with bids-standard#630
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! I have made some suggestions to maintain backwards compatibility. Let me know what you think.
Co-authored-by: Chris Markiewicz <effigies@gmail.com> Apply suggestions from code review Co-authored-by: Chris Markiewicz <effigies@gmail.com>
905c229
to
4ddf5a7
Compare
lint table fix link to deprecated section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd still like to have a general note with the URI definition, but I can be argued out of it if you're so inclined.
Co-authored-by: Chris Markiewicz <effigies@gmail.com>
Thanks @Remi-Gau |
yes, I do. Thank you! ;) |
TO DO
doi:<path>
For reviewers