search

proycon / codemetapy

A Python package for generating and working with codemeta
https://codemeta.github.io/
GNU General Public License v3.0
24 stars 5 forks source link

Context parsed wrong? #32

Closed broeder-j closed 1 year ago

broeder-j commented 1 year ago

Currently codemetapy often generates a context for the jsonLD like this:

    "@context": [
        "https://raw.githubusercontent.com/codemeta/codemeta/2.0/codemeta.jsonld",
        "https://raw.githubusercontent.com/schemaorg/schemaorg/main/data/releases/13.0/schemaorgcontext.jsonld",
        "https://w3id.org/software-types",
        "https://w3id.org/software-iodata"
    ],

While codemeta does expect a context like this:

"@context": "https://doi.org/10.5063/schema/codemeta-2.0",

Is there any good reason for the first context list? I know that usual context can be nested and complex and codemeta.json would do well to allow for easy extensions or embeding. While it does not, the harvester should put the right context in my opinion, at least the right reference to the codemeta schema.

proycon commented 1 year ago

I had some issues where doi.org didn't properly work at the time, but I agree it would be better to put the doi.org URL in there (and schema.org). I'll try if it works now.