You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"developmentStatus": [
"trl:Level8Complete",
{
"@id": "https://www.repostatus.org/#active",
"@type": "skos:Concept",
"og:image": "https://www.repostatus.org/badges/latest/active.svg",
"skos:definition": "The project has reached a stable, usable state and is being actively developed.",
"skos:inScheme": [
{
"@id": "https://www.repostatus.org/",
"@type": "skos:ConceptScheme",
"dct:creator": "Jason Antman",
"dct:description": "A standard to easily communicate to humans and machines the development/support and usability status of software repositories/projects.",
"dct:title": "repostatus.org"
},
{
"@id": "https://www.repostatus.org/",
"@type": "skos:ConceptScheme",
"dct:creator": "Jason Antman",
"dct:description": "A standard to easily communicate to humans and machines the development/support and usability status of software repositories/projects.",
"dct:title": "repostatus.org"
}
],
"skos:prefLabel": "Active"
}
],
}
string + object produces a kind of mixed content that's problematic for the CMDI conversion. We should get two objects here.
The text was updated successfully, but these errors were encountered:
The prefixes like tlr: but also skos: are defined in the JSON-LD for https://w3id.org/research-technology-readiness-levels which is included into the context. So they are valid, unlike what I thought at first.
Parsing the resulting codemeta.json does seem to work okay as well.
So here the question remains only, why did it not get expanded with the full context information (--includecontext)
proycon
added a commit
to proycon/codemetapy
that referenced
this issue
Feb 28, 2023
May relate to #33
Also affects CMDI conversion by @menzowindhouwer:
string + object produces a kind of mixed content that's problematic for the CMDI conversion. We should get two objects here.
The text was updated successfully, but these errors were encountered: