You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some target schema has more than one property that can correspond to a property in CodeMeta.
Currently, it looks like a de facto way to do specify them in the mapping table is by putting them together in the same field and separated them by a forward slash (/).
softwareRequirements, Software Discovery Index: "Platform, environment, and dependencies"
(Ruby Gem uses both / and .)
There is also a use of or:
funding, OntoSoft: fundingReference.awardTitle or fundingReference.awardNumber
If we can settled down on one suggested way to put a list of possible corresponding properties, be it a / or a , or an or or something else, we may able put it to Contribution Guide (CONTRIBUTING.md).
The text was updated successfully, but these errors were encountered:
Some target schema has more than one property that can correspond to a property in CodeMeta.
Currently, it looks like a de facto way to do specify them in the mapping table is by putting them together in the same field and separated them by a forward slash (
/
).For example:
repository/location
scm / repositories
scm.name / scm.url
license / license-file / license-files
license / license-url
synopsis / description
identifiers / person.orcid / doi
dependencies / bundledDependencies / bundleDependencies / peerDependencies
devDependencies / optionalDependencies
author/authors
But few others use a comma (
,
).For example:
dependencies, dev-dependencies, build-dependencies
Depends, SystemRequirements
Depends, SystemRequirements
requirements, add_runtime_dependency
"Platform, environment, and dependencies"
(Ruby Gem uses both
/
and.
)There is also a use of
or
:fundingReference.awardTitle or fundingReference.awardNumber
If we can settled down on one suggested way to put a list of possible corresponding properties, be it a
/
or a,
or anor
or something else, we may able put it to Contribution Guide (CONTRIBUTING.md).The text was updated successfully, but these errors were encountered: