RDF Serialization Formats

Currently, PoolParty API methods support the following RDF serialization formats.

Formats differ from each other regarding the possibility to support a context of data ("named graphs").

Format Name

Parameter

Format Supports Named Graphs

Usage as Content-Type Header

TriG

TriG

(tick)

application/trig, application/x-trig

TriX

TriX

(tick)

application/trix

N3

N3

(minus)

text/n3, text/rdf+n3

Turtle

Turtle

(minus)

text/turtle, application/x-turtle

N-Triples

NTriples

(minus)

application/n-triples, text/plain

RDF/XML

RDFXML

(minus)

application/rdf+xml, application/xml

BinaryRDF

BinaryRDF

(tick)

application/x-binary-rdf

N-Quads

NQuads

(tick)

application/n-quads, text/x-nquads, text/nquads

JSON-LD

JsonLD

(tick)

application/ld+json

RDF/JSON

RDFJson

(tick)

application/rdf+json

The format name is used as request parameter in for example: Web Service Method: Export and Download Project Data.

The Content-Type header is used for uploading data as in Web Service Method: Import Project Data

Support of named graphs

For example, the syntax of Turtle supports only the specification of single graphs without a means for "naming" them. In contrast to TriG, which is an extension of Turtle being able to support multiple graphs in one RDF dataset.

See further details about the supported serialization formats here: https://www.w3.org/TR/rdf11-primer/