Fixture — record-export-jsonld

Profile: export-only Endpoint: GET /api/ric/v1/records/{slug}/export (default JSON-LD; ?format=ttl or ?format=rdf for alternatives) Content-Type: application/ld+json Content-Disposition: attachment; filename="{slug}-ric.jsonld"

Canonical per-record dump envelope. A dump is a single @graph-wrapped JSON-LD document containing the root Record plus its transitively-reachable authority entities (creators, places, rules, activities, instantiations) as separate objects in the graph.

Required envelope structure:

@context — MUST bind rico to the ontology IRI and include xsd for typed literals. openric, rdf, rdfs, owl are RECOMMENDED (servers emit these to be friendly to consumers).
@graph — array, MUST be non-empty. First element SHOULD be the root Record; order of subsequent elements is unconstrained.

Content negotiation:

`?format=`	`Accept:`	Response MIME
`jsonld` / omitted	`application/ld+json`	`application/ld+json` (this fixture)
`ttl` / `turtle`	`text/turtle`	`text/turtle; charset=utf-8`
`rdf` / `rdfxml`	`application/rdf+xml`	`application/rdf+xml; charset=utf-8`

The Turtle and RDF-XML representations MUST be lossless round-trips of the JSON-LD graph — they are generated by JsonLdConverter::toTurtle / ::toRdfXml in the reference implementation and carry the same triples.

Empty dumps: a record with no transitively-reachable authorities produces @graph with a single entry (the root Record). A request for a non-existent slug returns 404 not-found with application/problem+json, not an empty @graph envelope.