RDF Serialization Formats
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 |  | application/trig, application/x-trig |
TriX | TriX | | application/trix |
N3 | N3 |  | text/n3, text/rdf+n3 |
Turtle | Turtle | | text/turtle, application/x-turtle |
N-Triples | NTriples | | application/n-triples, text/plain |
RDF/XML | RDFXML | | application/rdf+xml, application/xml |
BinaryRDF | BinaryRDF | | application/x-binary-rdf |
N-Quads | NQuads | | application/n-quads, text/x-nquads, text/nquads |
JSON-LD | JsonLD | | application/ld+json |
RDF/JSON | RDFJson | | 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/