Table 3:
Controlled vocabularies
| Controlled vocabulary (#terms) | Description |
|---|---|
| Identifier type (4) | The type of tool identifier, e.g., “doi” |
| Tool type (15) | The type of application software, e.g., “Command-line tool” |
| Operating system (3) | The operating system supported by a downloadable software package, e.g., “Linux” |
| Programming language (57) | Name of programming language the software source code was written in, e.g., “C” |
| License (326) | Software or data usage license, e.g., “GPL-3.0” |
| Maturity (3) | How mature the software product is, e.g., “Mature” |
| Cost (3) | Monetary cost of acquiring the software, e.g., “Free of charge” |
| Accessibility (3) | Whether there are non-monetary restrictions on accessing an online service, e.g., “Open access” |
| Elixir platform (5) | ELIXIR research infrastructure technical platform, e.g., “Tools” |
| Elixir node (22) | ELIXIR research infrastructure national node, e.g., “France” |
| Elixir community (11) | Name of relevant ELIXIR (or other) community, e.g., “Galaxy” |
| Link type (12) | The type of data, information, or system that is obtained when the link is resolved, e.g., “Helpdesk” |
| Download type (18) | Type of download that is linked to, e.g., “Source code” |
| Documentation type (15) | Type of documentation that is linked to, e.g., “API documentation” |
| Publication type (6) | Type of publication, e.g., “Review” |
| Relation type (6) | Type of tool relationship, e.g., “uses” |
| Credit entity type (6) | Types of entities that may be credited, e.g., “Person” |
| Credit entity role (7) | Roles that may be assigned to creditable entities, e.g., “Developer” |
biotoolsSchema defines 18 controlled vocabularies catering for technical aspects of software description.