Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
Excerpt

All of the public RDF in VIVO is available in response to Linked Open Data requests. VIVO responds to standard LOD requests, and also some request formats that are particular to VIVO.

Overview

...

Linked Open Data is one of the fundamental concepts of the Semantic Web. It consists of asking a server for the RDF relating to an individual. If the response includes object properties that link to other individuals, those individuals can be queried also. For more information on Linked Open Data, see Concept: Linked Data.

VIVO accepts standard requests for Linked Open Data and some non-standard ones. The contents of the response are in accordance with those suggested by the  in their tutorial How to Publish Linked Data on the Web.

VIVO will provide Linked Open Data in several formats. The semantic content remains the same; only the syntax differs among formats.

An example

The examples on this page are based on a fictitious individual named "Able Baker", with a URI of http://vivo.mydomain.edu/individual/n3639. To keep the examples simple, this person has just a few items in his VIVO profile. His profile page looks like this:

Image Added

Requesting Linked Open Data from VIVO

Available formats

VIVO will serve Linked Open Data in these formats:

Specifications for each of the formats are provided by the World Wide Web Consortium (W3C).

Types of requests

The standard way of requesting Linked Open data is an HTTP request to the URI of the individual in question, with the Accept header on the request indicating the desired format. If there is no Accept header, it is assumed to be text/html, and the standard profile page is returned.

Response formatURLAccept header
RDF/XML
http://vivo.mydomain.edu/individual/n3639
application/rdf+xml
N3
http://vivo.mydomain.edu/individual/n3639
text/n3
Turtle
http://vivo.mydomain.edu/individual/n3639
text/turtle
JSON-LD
http://vivo.mydomain.edu/individual/n3639
application/json

The different responses may also be explicitly requested by URL. In fact, the requests listed above will simply redirect the browser to these URLs:

Response formatURL
RDF/XML
http://vivo.mydomain.edu/individual/n3639/n3639.rdf
N3
http://vivo.mydomain.edu/individual/n3639/n3639.n3
Turtle
http://vivo.mydomain.edu/individual/n3639/n3639.ttl
JSON-LD
http://vivo.mydomain.edu/individual/n3639/n3639.jsonld

Finally, VIVO allows you to request Linked Open Data in a way that is not specified by the standard. You can make an HTTP GET request to the URI of the individual, and include a format parameter that specifies the format of the response.

Response formatURL
RDF/XML
http://vivo.mydomain.edu/individual/n3639?format=rdfxml
N3
http://vivo.mydomain.edu/individual/n3639?format=n3
Turtle
http://vivo.mydomain.edu/individual/n3639?format=ttl
JSON-LD
http://vivo.mydomain.edu/individual/n3639?format=jsonld

What is included in the response?

...

Let's say that we have a faculty member with just a few items on his profile page. It might look like this:

Image Removed 

Here is the RDF for this person, produced by a request for http://vivo.mydomain.edu/individual/n3639. In this example, the RDF is expressed in N3 format.

...

Note

How to make them public or private, and how to obtain the private ones by logging in before requesting LOD.

Available formats

Note

List the formats we provide, with references to definitions, especially for JSONLD

...