Choose identifier for the CodeMeta schema about codemeta HOT 7 CLOSED

September 6th is behind us.
We can move forward with the identifier: https://w3id.org/codemeta

from codemeta.

I agree and need some community feedback for the best solution with the identifier and resolution.
I see we agree on w3id for the ID.
Now we need to agree on the redirection. Let's see if we get answers before October 15th.

from codemeta.

@stain I raised this in #216 a few years ago. Completely moving to w3id may bring in incompatibility changes for those registries that have adopted codemeta, so I understand it may be trickier... but I would still go for it

from codemeta.

(First of all, support move to w3id!)

The current JSON-LD context maps to https://codemeta.github.io/terms/ as namespace, yet implied term URIs like https://codemeta.github.io/terms/maintainer do not currently resolve. Relying on deployment details like github.io in a namespace is also not good practice.

Should this then not use PID namespace https://w3id.org/codemeta# instead? You can then add id="maintainer" etc. in the HTML so also human browser get the definition. (and perhaps some javascript can do highlighting of selected row)

from codemeta.

Hi @dgarijo,
In this folder do we need to change the redirection before updating this information on this repo?

Thanks for the help.
Best,
Morane

from codemeta.

Even though all issues related to the redirection are not yet (?) resolved, I am happy to see the namespace. Will start using it for our extension on properties related to Software Management Plans (that might bring suggestions for new properties).

from codemeta.

@moranegg no changes are needed. If you want to change the link to the latest version, you only need to change the link in the htaccess which now points to https://raw.githubusercontent.com/codemeta/codemeta/3.0/codemeta.jsonld. Or ping me with the right file and I will change it in a sec

from codemeta.