# The RDF Presentation ontology
An RDF graph can be presented in several ways, using different media types.

## DBpedia Archivo Ontology Snapshot

| Attribute |  Value |
| - | - |
| Ontology URI | <https://w3id.org/rdfp/>
| Snapshot OWL Version IRI | <https://w3id.org/rdfp/rdfp-1.0>
| Snapshot Time | 2020-06-10 22:09:49

The [DBpedia Archivo Databus agent](https://databus.dbpedia.org/ontologies) generates only basic, static documentation for the archived snapshots of the ontologies. More, augmented and dynamic information for this ontology is rendered on and retrievable via [DBpedia Archivo Frontend](http://archivo.dbpedia.org/info?o=https://w3id.org/rdfp/).

## Ontology Metadata

DBpedia Archivo extracts metadata from the ontology for well known properties (e.g. dct:description). This subsection shows the content of every property individually using a separate heading.

### dct:description

## RDF Presentation and RDF Presentation Negotiation

**To cite our work:**

> Maxime Lefrançois _Interopérabilité sémantique libérale pour les services et les objets_, Actes de la 17ème conférence Extraction et Gestion des Connaissances, EGC, Jan 2017, Grenoble, France - ([PDF](http://www.maxime-lefrancois.info/docs/Lefrancois-EGC2017-Interoperabilite.pdf) - [BibTeX](Lefrancois-EGC2017-Interoperabilite.bib))


An RDF graph can be presented in several ways, using different media types. Examples of RDF media types include `application/rdf+xml`, `text/turtle`, `application/json+ld`.

Today, most of the content consumed/produced/published, on the Web is not presented in RDF. 

In the Web of Things, HTTP servers and clients would rather exchange lightweight documents, potentially binary. 
Currently, most existing RDF Presentations generically apply to any RDF graph, at the cost of being heavy text-based documents.
Yet, lightweight HTTP servers/clients could be better satisfied with consuming/producing/publishing lightweight documents, may its structure be application-specific.

On the other hand, various formalisms have been developed:

- to lift documents to RDF. Examples include [RML mappings](http://rml.io), [XSPARQL](http://xsparql.deri.org/), [SPARQL-Generate](http://w3id.org/sparql-generate/);
- to lower RDF to documents. Examples include [XSPARQL](http://xsparql.deri.org/), [STTL, aka SPARQL-Template](https://ns.inria.fr/sparql-template/);
- to validate RDF graphs. Examples include simple [SPIN](http://spinrdf.org/), [ShEx](http://shexspec.github.io), [SHACL](https://www.w3.org/TR/shacl/). 

For a given range of RDF graphs and a specific media types, an RDF Presentation is a combination of lifting, lowering, and validation rules. With these rules, one can coherently interpret a representation as RDF (lift), validate the RDF graph, and generate back the representation from the RDF graph (lower).

While sending any kind of document, potentially lightweight, an HTTP server/client may refer to the specific RDF Presentation that is used. Then, the HTTP client/server can lift the document to RDF, and validate it.

Similarly, while requesting for an RDF graph, an HTTP server/client may inform the client/server what representation it prefers. Then, the client/server can validate the RDF graph, then lower it into a document.

### RDF Presentation description 

Following the Linked Data principles, RDF Presentations are given uniform identifiers (URIs), and an RDF description of these presentations can be retrieved at their URI.

The RDFP vocabulary can be used to describe RDF Presentations and the range of RDF graphs they apply to. It can be accessed at this URI: https://w3id.org/rdfp/ using content negotiation (i.e., set HTTP Header field `Accept` to one of the RDF syntaxes media types, or access it directly in [turtle](index.ttl), or in [RDF/XML](index.rdf).

For example, the RDF Presentation identified by https://w3id.org/rdfp/example/graph/xml 303 redirects to https://w3id.org/rdfp/example/description where it is described as follows:

```
@prefix rdfp: <https://w3id.org/rdfp/>.
@base <https://w3id.org/rdfp/>.

<example/graph/xml> a rdfp:Presentation ;
  rdfp:mediaType "application/xml" ; 
  rdfp:liftingRule <example/graph/xml/liftingRule> ;
  rdfp:loweringRule <example/graph/xml/loweringRule> ;
  rdfs:isDefinedBy <example/description> .
```

A full example RDF graph that uses this vocabulary can be found at URI https://w3id.org/rdfp/example/description. Use content negotiation, or access it directly in [turtle](https://w3id.org/rdfp/example/description.ttl), or in [RDF/XML](https://w3id.org/rdfp/example/description.rdf).


The RDFP vocabulary describes web resources, RDF graphs, ontologies, and their representations.

  The URI of a named graph is the identification of that graph in the sense of the W3C Architecture of the World Wide Web, Volume One.
  The graph is the content, and that graph can be represented by many different documents that can then be exchanged on the Web.

## Referring to an RDF Presentation

The RDF Presentation qualifies the representation type. Following the general architecture principles defined in [W3C Architecture of the World Wide Web, Volume One](https://www.w3.org/TR/2004/REC-webarch-20041215/), we keep orthogonal the identification and representation concepts. Arguably, the representation type (the media type) should be annotated with a link to the RDF Presentation used. 

Although new media types could have a parameter that refers to its presentation, such as: `application/seas;p="https://w3id.org/rdfp/example/graph/xml"`. 
This link cannot be set by a global media type parameter, as per [RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies](https://tools.ietf.org/html/rfc2045):

> There are NO globally-meaningful parameters that apply to all media types.  Truly global mechanisms are best addressed, in the MIME model, by the definition of additional Content-* header fields.

We hence introduce HTTP header field `Content-Presentation` for this purpose. The value of this field is any absolute URI, that identifies the RDF Presentation of the represented RDF graph. 

Using this header properly, any existing server can be adapted to behave "as if" it was producing RDF: the client simply needs to dereference the presentation link, and use the associated lifting rule to interpret the retrieved document as RDF.

Equally important, a lightweight client/server can send lightweight binary messages, while still letting its server/client the chance to interpret the message body as RDF.

## RDF Presentation Negotiation

RDF Presentation Negotiation is a way for the client to state its presentation preferences for the response message body. 

To achieve this, we introduce HTTP header field `Accept-Presentation`.  The value of this field is any (absolute) URI, that identifies the RDF Presentation the clients would like the server to use to encode the response RDF graph. 

Using this header properly, a lightweight client can request a compliant server to encode its responses in a specific format, hence transferring all the computation cost on the server.


## Directly referring to the lowering rule, validation rule, or lifting rule

In some situations, it may seem unreasonable to expect the client/server to:

1. dereference the RDF Presentation URI,
1. parse the RDF document,
1. navigate to the lifting, validation, or lowering rule of the RDF Presentation.

Hence, in a future version of RDFP, we may introduce additional HTTP header fields to directly refer to these rules. For example:

- HTTP header field `Content-Lifting-Rule` would mean that the receiver may use this lifting to generate RDF from the content;
- HTTP header field `Accept-Lowering-Rule` would mean that the client expects the server to use this lowering rule to generate a content it can process.

## Implementation over Jersey

[`rdfp-jersey-server`](get-started.html) is an extension of Jersey that eases the development of RESTful services that produce and consume RDF. It hides the RDF Presentation description and RDF Presentation Negotiation parts, and lets the end developer focus on manipulating RDF graphs as [Apache Jena](http://jena.apache.org/) models.


## Related projects

The RDFP vocabulary is used in the following related projects:

- [ONTOP - Ontology Platform](https://w3id.org/ontop/);

`rdfp-jersey-server` is used in the following related projects:

- [PEP - Process Execution Platform](https://w3id.org/pep/);
- [CNR Smart Charging Provider SEAS pilot platform](http://cnr-seas.cloudapp.net/scp/).

## Contact

maxime.lefrancois.86@gmail.com

http://maxime-lefrancois.info/

 + ## All DBpedia Archivo ontologies from w3id.org domain

Each artifact in this group deals as the archive for snapshots of one ontology of the [DBpedia Archivo](https://databus.dbpedia.org/ontologies) -  A Web-Scale Interface for Ontology Archiving under Consumer-oriented Aspects. Find out more at [http://archivo.dbpedia.org](http://archivo.dbpedia.org). The description for the individual files in the artifact can be found [here](http://dev.dbpedia.org/DBpedia_Archvio#files).