Document that we only support a subset of Codemeta

[progval]

It's confusing to many people that the "Import Codemeta" document rejects valid documents.

We cannot reasonably add full support for Codemeta without bloating the interface, so we need to document it, and make it clear when on errors.

[geoffroy-noel-ddh]

Hi, thanks for opening that issue!

I understand the difficulty for the interface to completely support Codemeta. But I'm wondering about the validation function itself as the generator is recommended on the CodeMeta site as a way to validate codemeta.json files. Is the validation logic tied to the interface or does it work through a independent jsonld schema validator? If codemeta schema is defined somewhere formally then, in principle, the validation, unlike the interface itself, could be exhaustive?

[progval]

as the generator is recommended on the CodeMeta site as a way to validate codemeta.json files

That looks like a mistake

Is the validation logic tied to the interface or does it work through a independent jsonld schema validator?

Kind of both.

If codemeta schema is defined somewhere formally then, in principle, the validation, unlike the interface itself, could be exhaustive?

There isn't a formal schema. We could define one, but in my experience, validators/parsers generated from a schema give incomprehensible errors to normal users, because they would also be generated. The goal of the Codemeta Generator is to prioritize usability over completeness.

[progval]

Though if someone wants to write a proper validator, they are welcome to. It's probably best to start from scratch rather than reuse the existing code in the Codemeta Generator