Matt Jones

@moranegg See the related discussion in SOSO for schema.org citations: https://github.com/ESIPFed/science-on-schema.org/issues/42

What do you mean by the main crosswalk page? Are you referring to: https://codemeta.github.io/crosswalk/ ? If so, then I think its been that way all along, and @cboettig just picked...

@moranegg I suspect they should be separate as well given that each of the bibtex types has a different set of allowed fields. The 4 crosswalks will likely be very...

Thanks, @yvanlebras, for the PR -- it would be great to add a Conda mapping. In reviewing your PR, I note that you did not follow the format of the...

@dgarijo you make a good point. We published the 2.0 version using the doi https://doi.org/10.5063/schema/codemeta-2.0, and our intention was that would be the context for the terms. So this resolves...

Thanks @dgarijo Personally I much prefer to keep the version in the namespace, as it makes it much clearer which version of a vocabulary people are using in particular instance...

That's a very good point about the property rename. For other vocabularies that we manage like ECSO, the new versions only contain new terms -- once minted, old term URIs...

Thanks, @VickyMerzOwn for the crosswalk. I retargeted the PR at the develop branch and we will review it for the next release.

Many repositories support pre-reserving DOIs and other identifiers. That's what we do in the KNB, and it is supported via the EZID API for issuing DOIs using the `reserved` status....

The 'master DOI' approach has the advantage of being simple. We have the same feature in DataONE (we call it a 'Series Identifier' because it identifies a series of versions)...