Validation: softwareRequirements requires URLs, but specifications requests type SoftwareSourceCode

[AutumnIsilme]

I have used the automatic generator at https://autocodemeta.linkeddata.es to generate several codemeta.json files.
Upon one of the project owners whom I have PR'd these files to attempting to validate with https://codemeta.github.io/codemeta-generator, they have gotten an error saying

"softwareRequirements" must be a list of URLs (or a single URL), but it contains: {"name":"python-dotenv","version":"==1.1.0"}

which was generated by the automatic generator.

Comparing against the specification here, I believe this indicates that "softwareRequirements" should be json objects fitting "SoftwareSourceCode" rather than a list of URLs.

[AutumnIsilme]

Minimal reproduction json:

{
    "@context": "https://w3id.org/codemeta/3.0",
    "applicationCategory": "SoftwareSourceCode",
    "softwareRequirements": [
        {
            "name": "requirement",
            "version": "1.0.0"
        }
    ],
    "@type": "SoftwareSourceCode"
}

[progval]

This is somewhat expected, the Codemeta Generator does not fully support Codemeta

[geoffroy-noel-ddh]

Thanks @progval , is that gap documented somewhere already? I'm curious to know which other parts are not supported yet.

[progval]

It's not documented, I opened #93 for that. There are too many unsupported parts to list them, but mostly: any field not listed on the interface, multiple values of most fields, languages, alternative types (like here), terms from other vocabularies (including schema.org), named graphs, and other fancy JSON-LD features that persist after compaction.