55-rda-r1-01m-t5-type-unresolve

This landing page has these FAIR Signposting HTTP headers:

• rel=cite-as to w3id PID
• rel=type to https://w3id.org/a2a-fair-metrics/not-found/
• rel=type to https://w3id.org/a2a-fair-metrics/00-404-not-found/
• rel=type to https://s11.no/2022/a2a-fair-metrics/29-http-500-server-error/

This is a test for FAIR principle RDA-R1-01M - Plurality of accurate and relevant attributes are provided to allow reuse.

Test 6: Each rel=type url resolves.

In this case, each of the types are broken:

• https://w3id.org/a2a-fair-metrics/not-found/ will give 404 Not Found at PID provider w3id.org
• https://w3id.org/a2a-fair-metrics/00-404-not-found/ will redirect, then give 404 Not Found
• https://w3id.org/a2a-fair-metrics/29-http-500-server-error/ redirects, then gives a 500 Server Error

Only the first of these indicate that the type PID is unknown and should cause a failure. The second one indicates that the PID record redirect is outdated -- this is quite typical of poorly deployed ontologies and should be a strong warning. The third one could be a transient error and give a soft warning.