HTTP Content Negotiation uses HTTP headers in both request and response to enable negotiation of serialization formats. Including this in an API specification greatly enhances its compatibility.
Since this API aims to comply to RDF constraints (IDs are URLs, keys are URLs, Resources have Classes which are URLs), it makes sense to allow other RDF serialization options, such as N-Triples and Turtle.
HTTP Content Negotiation uses HTTP headers in both request and response to enable negotiation of serialization formats. Including this in an API specification greatly enhances its compatibility.
Since this API aims to comply to RDF constraints (IDs are URLs, keys are URLs, Resources have Classes which are URLs), it makes sense to allow other RDF serialization options, such as N-Triples and Turtle.