Support integration with ORCID data, so that authors can receive credit/attribution in their docmaps and also for linking docmaps data to other information about that author.
standardize how to include ORCIDs in the participants / actor model.
build-in verification of ORCID claims (requires partnering with ORCID to augment their API).
Use case
There is already growing consensus in some preprint science communities on the value of seamless integration with ORCID attribution for authors, which DocMaps needs to support.
Proposed solution
It is straightforward to standardize making unverifiable statements about ORCIDs in DocMaps.
A complication is that DocMaps verification must remain offline — this integration must allow a publisher to include information from ORCID’s databases that is trustworthy without separate contact with ORCID by the reader. This is currently unsupported because, as described above about DocMaps server integrity, the ORCID API does not serve cryptographic information, instead relying on HTTPS to be the source of trust.
Therefore we need to partner with ORCID to substantially improve their offline-verifiable signature support.
Additional information
Provide any additional information that might be helpful in understanding the semantics improvement issue, such as relevant research or examples from other projects.
Protocol semantics improvement
Description
Support integration with ORCID data, so that authors can receive credit/attribution in their docmaps and also for linking docmaps data to other information about that author.
participants/ actor model.Use case
There is already growing consensus in some preprint science communities on the value of seamless integration with ORCID attribution for authors, which DocMaps needs to support.
Proposed solution
It is straightforward to standardize making unverifiable statements about ORCIDs in DocMaps.
A complication is that DocMaps verification must remain offline — this integration must allow a publisher to include information from ORCID’s databases that is trustworthy without separate contact with ORCID by the reader. This is currently unsupported because, as described above about DocMaps server integrity, the ORCID API does not serve cryptographic information, instead relying on HTTPS to be the source of trust.
Therefore we need to partner with ORCID to substantially improve their offline-verifiable signature support.
Additional information
Provide any additional information that might be helpful in understanding the semantics improvement issue, such as relevant research or examples from other projects.