Matt Jones

That's great, @moranegg . As these are accepted into schema.org, it strikes me that we should be modifying the CodeMeta schema to reference the new schema.org types. So I am...

We use the `@list` structure on science on schema.org as well, and have a [writeup describing the uses for `@list`](https://github.com/ESIPFed/science-on-schema.org/blob/develop/guides/GETTING-STARTED.md#json-ld-list) in the upcoming release that may be helpful. I think...

I noted a syntax error above. Other than fixing that up, I think the general idea of `hasSourceCode` and the specific implementation and definition are all great. So, let's get...

@cboettig Given that this is a schema change, we should probably merge into a branch for the time being as the master branch is used for validation in the tests. ...

Sounds good. Looking into why the tests in Travis are failing, I think the PR has a mismatch between some of the documentation files and the new changes in the...

@moranegg The tests are still failing on the PR, and so we can't merge until those are passing. Plus, the PR seems to have conflicts that need to get resolved...

@dgarijo That's up to you, but would be appreciated. Eventually either Carl or I would get to it in the process of preparing a 3.0 release, but I am fully...

Sounds like a great addition to me.

Awesome. A pull request would be welcome with the new term definition for the new property (hopefully aligned with an existing well-defined vocabulary if it exists) and additions to the...

I agree that including `legalName` should not create an error. That said, I think the intention of CodeMeta is to provide opinionated guidelines on which schema.org fields really should be...