Minimal metadata schemas for science software and code, in JSON-LD
Vocabulary changes:
codemeta:contIntegration
to codemeta:continuousIntegration
(https://github.com/codemeta/codemeta/pull/302 by @tmorrell)codemeta:embargoDate
to codemeta:embargoEndDate
(https://github.com/codemeta/codemeta/pull/314 by @tmorrell)codemeta:hasSourceCode
and codemeta:isSourceCodeOf
to describe links between schema:SoftwareSourceCode
and schema:SoftwareApplication
. (https://github.com/codemeta/codemeta/pull/300 by @dgarijo and @progval)Context changes:
schema:releaseNote
(https://github.com/codemeta/codemeta/pull/280 by @progval)schema:Role
, schema:startDate
, schema:endDate
, and schema:roleName
, to allow easier expression of author and contributor roles. See http://blog.schema.org/2014/06/introducing-role.html for an introduction to the concept. (https://github.com/codemeta/codemeta/pull/241 by @progval)schema:Review
, schema:review
, schema:reviewAspect
, and schema:reviewBody
, to describe software reviews. (https://github.com/codemeta/codemeta/pull/311 by @progval)Other changes:
This release does not contain any change to the codemeta vocabulary or context.
Crosswalk updates:
New crosswalks:
Other changes:
This release candidate completes the migration to a set of terms more aligned with schema.org.
An overview of all changes in this version can be found at: https://github.com/codemeta/codemeta/issues/142#issuecomment-302182021
The codemeta
1.0 release provides a mechanism to assist the transfer of software and software metadata between the entities that author, archive, index and distribute and use the software.
To use this release, please include the following @context
in your JSON-LD metadata record:
"@context": "https://doi.org/10.5063/SCHEMA/CODEMETA-1.0"