The CodeMeta community has created a vocabulary adapted to describe software and specifically research software, by including a codemeta.json file in the root directory of your repository.
The vocabulary is a subset of schema.org (see issue 161).
The following terms are not part of schema.org:
- softwareSuggestions
- maintainer
- contIntegration
- buildInstructions
- developmentStatus
- embargoDate
- funding
- issueTracker
- referencePublication
- readme
To easily work on the properties propositions, it would be best to use the detailed table with the following columns for each item:
status of each term:
- term
- type
- description
- lead
- status
- proposal text
- issue on CodeMeta
- issue on schema.org
- similar terms
- similar proposals
- Wikidata term
- Notes
Dashboard: Google spreadsheet
For each step you do, update in the Dashboard the status of the proposal with the step number and notes relative to the proposal
- [done for all] Choose a property and note you are the lead for its preparation.
- Check if there has been a proposal for this property on schema.org repository with or without label:"schema.org vocab" (all issues)
- Check if the property exists on schema.org in other classes for a different domain (consider that the property may exist but its label may be a synonym of the property identified in Codemeta)
- Check if the property exist on Wikidata (https://www.wikidata.org/wiki/Q7397) which will help in community consensus (see Wikidata issue on schema.org)
- Prepare a proposition text.
Here are a couple of examples:
- schemaorg/schemaorg#809
- schemaorg/schemaorg#148
- schemaorg/schemaorg#2300
- Add interesting examples here
- Post issue on the CodeMeta repository with the proposal to get feedback from the CodeMeta community and improve proposal and fix proposal submission date on schema.org: codemeta/codemeta#160
- Post issue on schema.org with one or more labels: