search

codemeta / codemeta-generator

This repository contains a (client-side) web application to generate Codemeta documents (aka. codemeta.json).
https://codemeta.github.io/codemeta-generator/
GNU Affero General Public License v3.0
8 stars 5 forks source link

relationship of codemeta JSON-LD to schema.org??? #9

Open smrgeoinfo opened 4 years ago

smrgeoinfo commented 4 years ago

the web form at https://codemeta.github.io/codemeta-generator/ should have some text or a link to clarify the relationship of the generated JSON-LD to schema.org dataset descriptions. Will codemeta JSON-LD validate with the structured data testing tool?

moranegg commented 4 years ago

Hello @smrgeoinfo,

I am curious about your use case. I can point you to the CodeMeta user guide here: https://codemeta.github.io/user-guide/ The tool creates a codemeta.json file, which is specified by the CodeMeta vocabulary and community. The CodeMeta vocabulary is an extension of the SoftwareSourceCode and the SoftwareApplication classes in schema.org. The generator, like the CodeMeta vocabulary, focuses software only. The recommendation is to add a codemeta.json file into a software source code repository as a metadata file.

The web form is part of the CodeMeta space on https://codemeta.github.io/ and everything I have written in this comment can be found on its homepage or in the two following repositories:

Would it be helpful to repeat that on the generator web form itself?

mbjones commented 4 years ago

@smrgeoinfo Last I checked, codemeta.json files do validate with the GSDTT. The fields in the codemeta context are derived from the fields of the same name in schema.org, but GSDTT does not recognize this linkage, which requires a logic parsing layer to understand the relations. So GSDTT doesn't 'see' the associated schema.org fields and types them as codemeta fields. For example, the CodeMeta context file defines Person as:

"Person": {"@id": "schema:Person"}

That should set any codemeta:Person as an instance of schema:Person, which if you drop a codemeta document into the JSON-LD Playground and compact the file you see it resolves correctly to the right schema.org type. But the GSDTT does not seem to do this. I've been contemplating proposing a change to CodeMeta to use the schema.org types directly rather than being referenced by their @id.