10. Content negotiation for schema.org/JSON-LD and other content types may be supported so that the persistent identifier expressed as URL resolves directly to machine-readable metadata.
- Short Title: 10. Content negotiation for schema.org/JSON-LD and other content types may be supported so that the persistent identifier expressed as URL resolves directly to machine-readable metadata.
- Source Documnent: A data citation roadmap for scholarly data repositories
- Source Document Link: https://doi.org/10.1038/s41597-019-0031-8
- Publishing Organisation: FORCE11.org and BioCADDIE Data Citation implementation Pilot Repositories Expert Group
- Date of Publication: 2021-04-10
- Topic: Metadata richness/ ingest/ submission, Machine-actionability
- Keywords: content negotiation, schema.org, JSON-LD, PID, identifiers, machine-actionability, metadata
- Addressed Stakeholders: data service providers
- Full Text: Persistent identifiers expressed as HTTP URI must by default resolve to the landing page for that dataset (see guideline #3). Data repositories and identifier service providers such as identifi s.org, N2T or DataCite in addition may implement HTTP content negoti- ation for the persistent identifi expressed as HTTP URI, returning machine readable metadata in various formats. Content negotiation is for example supported by identifiers.org and DataCite and can return metadata in RDF-XML, BibTeX, schema.org and other metadata formats.