Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Context parsed wrong? #32

Closed
broeder-j opened this issue Oct 17, 2022 · 1 comment
Closed

Context parsed wrong? #32

broeder-j opened this issue Oct 17, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request ready Done/implemented, but release still pending

Comments

@broeder-j
Copy link

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
Copy link
Owner

proycon commented Oct 17, 2022

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.

@proycon proycon self-assigned this Oct 17, 2022
proycon added a commit that referenced this issue Oct 17, 2022
@proycon proycon added enhancement New feature or request ready Done/implemented, but release still pending labels Oct 17, 2022
proycon added a commit that referenced this issue Oct 17, 2022
@proycon proycon closed this as completed Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready Done/implemented, but release still pending
Projects
None yet
Development

No branches or pull requests

2 participants