This landing page has two HTTP Link headers:
describedby to metadata.compacted.jsonld
(type application/ld+json with profile
http://www.w3.org/ns/json-ld#compacted
for
compacted form)describedby to metadata.expanded.jsonld
(type application/ld+json with profile
http://www.w3.org/ns/json-ld#expanded
for
expanded form)
The two metadata file are both in JSON-LD format, but have different profile values
according to JSON-LD specification.
The compacted form is more readable as JSON, but may require retrieving a @context.
The returned Content-Type for the metadata files
should in this case include the corresponding profile attribute,
as it has been defined for this particular content type
(however other types like application/zip have not).
In this case the two metadata files have separate URIs, so the client is here not required to use content-negotiation by profile.