To follow F1 of the FAIR data principles, the first mentioned PID must be resolvable directly.
Additionally, content negotiation should be enabled, allowing requesting specific representation of the same content, for example:
curl -L -v -X GET -H "Accept: text/turtle" https://repo.metadatacenter.org/template-instances/f15e7ef3-83b4-4577-8f22-d0ef574bab32
curl -L -v -X GET -H "Accept: application/rdf+xml" https://repo.metadatacenter.org/template-instances/f15e7ef3-83b4-4577-8f22-d0ef574bab32
curl -L -v -X GET -H "Accept: application/json-ld" https://repo.metadatacenter.org/template-instances/f15e7ef3-83b4-4577-8f22-d0ef574bab32
CEDAR artefacts (fields, elements, templates, instances) contain PIDs. However, these PIDs are not directly resolvable, e.g. a PID of an instance:
https://repo.metadatacenter.org/template-instances/f15e7ef3-83b4-4577-8f22-d0ef574bab32
is not resolvable. Instead an end-user (human or machine) must call the following PID to resolve the content that it identifies:
https://cedar.metadatacenter.org/instances/edit/https://repo.metadatacenter.org/template-instances/f15e7ef3-83b4-4577-8f22-d0ef574bab32?folderId=https:%2F%2Frepo.metadatacenter.org%2Ffolders%2F71174e18-fe48-4f09-a713-07e9f4a4d0f7
To follow F1 of the FAIR data principles, the first mentioned PID must be resolvable directly. Additionally, content negotiation should be enabled, allowing requesting specific representation of the same content, for example: