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
This recent NISO report about badges gives some recommendations about what badge metadata should be made available in a structured form. We should revisit if all the information is available via the codecheck.yml, and think about how badge and YAML file could be connected.
Also, the idea to add a crpytographic hash in the image header for authentication of the badge source is interesting, but would require an own badge server.
It's a pity that they have ROR-R (reproduced) only as an extension of ROR (reviewed), whereas CODECHECK does reproduction without too much code review.
The text was updated successfully, but these errors were encountered:
This recent NISO report about badges gives some recommendations about what badge metadata should be made available in a structured form. We should revisit if all the information is available via the
codecheck.yml
, and think about how badge and YAML file could be connected.https://doi.org/10.3789/niso-rp-31-2021
Also, the idea to add a crpytographic hash in the image header for authentication of the badge source is interesting, but would require an own badge server.
It's a pity that they have
ROR-R
(reproduced) only as an extension ofROR
(reviewed), whereas CODECHECK does reproduction without too much code review.The text was updated successfully, but these errors were encountered: