Morane Gruenpeter

I must say that the granularity of identification is much more delicate than separating `parent-doi` and `concpet-doi`, this is why it should be discussed in a larger forum (maybe the...

Great idea to list all vocabularies that can/should be crosswalked in the same issue. I would add software registries that have metadata about software, including: - [ ] libraries.io -...

I want to do a PR for BibTeX with the following BibLaTeX software style. https://www.ctan.org/tex-archive/macros/latex/contrib/biblatex-contrib/biblatex-software The terms are detailed here: https://gitlab.inria.fr/gt-sw-citation/bibtex-sw-entry With 4 different software levels/types: - @software, - @softwareversion,...

Update: `maintainer` has been added as a property: https://schema.org/maintainer

I think the use case of `programmingLanguage` is about tagging the software with a set of dedicated keywords expressing the languages used and not for dependencies. The question remains, if...

I agree that the usage of both classes might be confusing. On the other hand, I find also confusing having `codeRepository` and `hasSourceCode` terms. Even if `hasSourceCode` is more generic,...

@dgarijo @alee this is a very interesting discussion ! I looked at the added CodeMeta terms, all are added into the source code class with `codemeta:SoftwareSourceCode`. From my understanding, the...

@dgarijo I think this PR is waiting for a CodeMeta v3 release ;-)

On the SCIWG we have the CodeMeta task force, with which we are working on the adoption of the codemeta terms into schema.org. I have just added `hasSourceCode` to the...

> This makes sense to me as well. Is this pattern being used now to describe CRedit roles in schema.org descriptions of journal publications as well? It makes sense to...