This landing page has three HTTP Link headers:
describedby to
metadata
(type application/ld+json with profile
http://www.w3.org/ns/json-ld#compacted
for
compacted form)describedby to
metadata
(type application/ld+json with profile
http://www.w3.org/ns/json-ld#expanded
for
expanded form)describedby to
metadata
(type text/turtle)
The two JSON-LD metadata files 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 JSON-LD 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 text/turtle have not).
In this case the metadata files all have the same URI …/metadata,
the client is here required to use
content-negotiation by type and profile.
The profile can be selected either using or by
including profile attribute in Accept.
If no profile is specified, the server will in this case give the compacted form.
The returned type will have both a Link with rel=profile and include the profile attribute in the Content-Type,
along with a Content-Location to indicate the chosen resource.