IdRef for developers

3.3.  RDF format, data Web, content negotiation

This link allows direct access to the RDF data describing a person:

NB: The RDF data of an authority of the type Personal name contain both the information present in the authority record and the list of documents described by the Sudoc to which this person is associated (at different titles: author, illustrator, thesis director, subject, etc.)

You can also access these RDF data by summoning the following "generic document":

specifying in the http request that you wish to receive RDF/XML according to the principle of contents negotiation.

Accept: application/rdf+xml

The server then returns the same content as

If the HTTP request summons the same generic document specifying that HTML is wanted,

Accept: application/xhtml+xml,text/html

The server will return an HTML page. The following link directly returns the same HTLM page: .

On the data web, each entity can be identified by a URL. In IdRef, the authority record for Paul Veyne is identified by (the generic document that can be of an HTML, RDF or XML form), but the person himself is identified by .

Since a person (or concept, work of art, Corporate body, etc.) is not a document, it cannot be accessible on the web. The URL of this person cannot directly reach the person in question. On the other hand, this URL indirectly reaches a document that describes the person:

  1. (URL of the person) is signaled by the client

  2. The server responds by proposing a redirection towards the generic document , via an http 303 code

  3. Depending on the MIME type requested, the server responds by RDF or HTML. The default setting is HTML.

Sudoc record identifier


URL of the generic document that describes an entity (person, concept, etc.)

URL of the HTML document that describes an entity

URL of the RDF document that describes an entity

URL of the UNIMARC/MARCXML document that describes an entity

URL of the entity itself described