Tom Morrell

Transferring from email chain - We’ve also been experimenting with a Dracula/Wolfman free git lesson, but in the context of a Data Carpentry workshop. Git isn’t a standard part of...

The colors are great, and I think they make the contributions from the two tables clearer than the existing images.

That is an issue...and I'm not sure how we would work around it. DataCite used to allow you have custom content negotiation, but now they provide content negotiation to the...

I don't have all the answers, but I have some thoughts about the crosswalk. I think the intention for the crosswalk is both humans and machines. It's useful to have...

DataCite removed native custom content negotiation for DOIs, so there is not an easy way to have both the html and json ld on the same DOI. I'm not sure...

I've made an initial PR for contributor and keywords, which maps to the behavior of https://codemeta.github.io/codemeta-generator/ in including an array for all cases. I think **funding**, **funder**, **editor**, and **copyrightHolder**...

The realignment is to see if any of the extension terms can fit under newer releases of schema.org. For example, if we can replace codemeta:SoftwareSourceCode,funding with schema:SoftwareSourceCode,funding as in #160...

My impression is that CodeMeta intentionally selects a subset of schema.org terms that are most useful for software. In this case 'name' is used in many places in CodeMeta, so...

PR implementing change is #260

I've closed my PR so there can be more discussion. I still think moving everyone to the standard schema.org property `documentation` makes more sense than having a custom `readme` property.