Skip to content

Conversation

@stain
Copy link
Contributor

@stain stain commented Oct 6, 2023

See discussion in codemeta/codemeta#236 (comment)

As this this modifies the 3.0 release-in-progress it uses the w3id PID from codemeta/codemeta#216 but the old https://codemeta.github.io/terms/ namespace unless discussion agrees to also change these to w3id for 3.0

@moranegg
Copy link
Member

moranegg commented Aug 8, 2025

Seems that this PR is finalized.

@moranegg
Copy link
Member

Need help to resolve conflicts before merge.

## The JSON-LD Context File

The current codemeta context file can be found at [![DOI](https://img.shields.io/badge/doi%3A-10.5063%2FSCHEMA%2FCODEMETA--2.0-blue.svg)](https://doi.org/10.5063/schema/codemeta-2.0)
The current codemeta context file can be used from <https://w3id.org/codemeta/3.0> -- note that browsers will redirect using _content negotiation_ to a HTML page, while JSON-LD processors will get the JSON-LD context.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like content negotiation no longer works.

A browser also gets the context file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @dgarijo

we're really cursed with these links -_-

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it works for https://w3id.org/codemeta/ but not for the versions. I will look into this. Apologies.

I would also like the terms to resolve, which need a special redirection. Been trying to get to this for a while. I will assume the id will be something like https://w3id.org/codemeta/X.X/TERM

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw, this will not affect the release, but I will try to have it working this week

@bact
Copy link
Contributor

bact commented Oct 1, 2025

Need help to resolve conflicts before merge.

@moranegg I try to resolve this with #73

@progval
Copy link
Member

progval commented Oct 1, 2025

Merge via #73

@progval progval closed this Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants