Carl Boettiger

There was a nice start outlining the objectives of codemeta, but there was no JSON-LD schema at the time, and I think the paper ought to give some sense of...

:+1: LGTM. @mbjones ?

`CONTRIBUTORS.md` is nice; though of course it seems like this information should be captured in our `codemeta.json` file in this repo! Currently `codemeta.json` has a more complete version of this...

Thanks @mbjones that's awesome. Right, the non-schema terms create an issue. I don't quite follow how the EarthCube examples are getting around this, the [example](https://raw.githubusercontent.com/earthcubearchitecture-project418/p418Vocabulary/master/html/voc/static/schema/examples/resource/dataset-full.jsonld) I looked at doesn't seem...

Right, I saw that, just wasn't sure in what sense it was really adding the vocabulary. i.e. if `geolink:Person` type defines some additional property `x`, we still cannot add said...

Thanks @mfenner , this sounds like a good direction to go. Currently codemeta has 10 terms that are not in schema.org: https://codemeta.github.io/terms/ . A handful of those are arguably overly...

@danbri Thanks for getting in touch! A few quick answers: - Most terms in codemeta come directly from Schema.org, while currently ten additional terms are provided by CodeMeta; see the...

@danbri can probably elaborate further, but I believe Google's structured data testing tool is not intended to be a generic validator of the W3C JSON-LD specification, but rather, whether the...

:+1: Thanks for raising this issue, I agree with these suggestions. Personally I agree with the view that `creator` should be interpreted as a synonym of `author`, and that think...

@mbjones regarding the ordering, it might be worth a note that the certain tools, e.g. the standard JSON-LD operations found in https://json-ld.org/playground/, will not preserve order of a set, so...