Clarify FAIR EVA positioning in README (what it is and is not) - #287
Open
ferag wants to merge 1 commit into
Open
Clarify FAIR EVA positioning in README (what it is and is not)#287ferag wants to merge 1 commit into
ferag wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR clarifies FAIR EVA positioning in the README:
Why
Users often compare FAIR tools as if they were interchangeable services. This change makes explicit that FAIR EVA is meant to be instantiated and adapted through plugins/configuration for institutional repositories, domain repositories, data portals, and API-based services.
Scope
Documentation-only change in README.md.
Validation