codemeta
applicationCategory and applicationSubCategory description & recommended use
For federated search purposes in the context of research software, it would be very helpful to have the following controlled-vocabulary entries:
- scientific domain, as identified by any of the existing ontologies, e.g., UAT, GCMD, EDAM, SWEET
- software function category (e.g., Data Processing vs Data Visualization) and software function subcategory (e.g., Grid/Mesh Generation vs Inversion/Data Assimilation) described through this ontology: https://cor.esipfed.org/ont/earthcube/sfo
One possibility to address this would be through recommendations on the use of applicationCategory and applicationSubCategory schema.org properties for SoftwareApplication, similar to how they are used here: https://github.com/BioSchemas/specifications/blob/master/Tool/examples/0.6-DRAFT/jaspar.jsonld
There, applicationSubCategory is used for scientific domain descriptions. The ontological context is provided.
An additional schema.org field, featureList, is used to describe the software function categories. See a separate issue #394 that proposes including featureList as an additional field in codemeta.
There are two separate concerns in this issue:
- Include the https://schema.org/applicationSubCategory in CodeMeta terms
- Guidelines for Controlled vocabularies, which will not be directly in the CodeMeta vocabulary but rather include a supplementary context
https://schema.org/applicationSubCategory is listed as part of codemeta at https://codemeta.github.io/terms/ - am I missing context or something else here?
You are right; my mistake when reading.
So the only thing here is guidance non the context.
