-
Notifications
You must be signed in to change notification settings - Fork 6
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
Compose and publish metadata for all software/services, for tool discovery #38
Labels
FAIR Tool Discovery
FAIR Tool Discovery
Milestone
Comments
The first step (or last, depending on how you look at it) in composing publishing software metadata and making it harvestable, is registering the software with the tool source registry, that is being tracked in #91 |
proycon
added a commit
to LanguageMachines/frog
that referenced
this issue
Jul 21, 2022
…osed) CLARIAH requirements (CLARIAH/clariah-plus#38)
proycon
added a commit
to LanguageMachines/ucto
that referenced
this issue
Jul 21, 2022
…osed) CLARIAH requirements (CLARIAH/clariah-plus#38)
proycon
added a commit
to LanguageMachines/mbt
that referenced
this issue
Jul 21, 2022
proycon
added a commit
to LanguageMachines/timbl
that referenced
this issue
Jul 21, 2022
proycon
added a commit
to LanguageMachines/libfolia
that referenced
this issue
Jul 21, 2022
proycon
added a commit
to LanguageMachines/foliautils
that referenced
this issue
Jul 22, 2022
proycon
added a commit
to proycon/colibri-core
that referenced
this issue
Jul 22, 2022
Closing, succeeded by #143 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All CLARIAH software/services should provide metadata in the agreed upon form (will be specified as part of the Software Requirements), it's most likely going to be the requirement to include a
codemeta.json
file in the root of the source code repository, and OpenAPI or other dedicated endpoints for webservices.This task is one that is spread over all CLARIAH partners/institutions and this issue may track general progress.
The text was updated successfully, but these errors were encountered: