You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Data stored in eagle-i repositories is published as Linked Open Data (LOD),in particular:

  • All eagle-i resources are identified by URIs.
  • All resource URIs are HTTP URLs, i.e. they are resolvable.
  • The HTTP protocol is used for content negotiation; the data is available in a variety of formats: RDF/XML, RDF/N3, HTML,...


The eagle-i search application indexes this data and leverages its semantics to offer a targeted search. Third party applications can also access the data to present different views of it, incorporate it in other websites, etc.

The Linked Open Data can be directly accessed in three ways:
1) Public SPARQL Endpoints
2) RDF downloads
3) Lists of URIs

Links to each of these mechanisms can be found at the data export portal: https://www.eagle-i.net/export/.


If a user or application knows the URI of a particular resource, they can simply request its data using the HTTP protocol; below is an example of an eagle-i resource:

http://alaska.eagle-i.net/i/0000012a-25c2-5d13-76e0-f22c80000005

and here is the RDF/XML representation of the same resource:

http://alaska.eagle-i.net/i/0000012a-25c2-5d13-76e0-f22c80000005?format=application/xml


In addition to resolvable URIs, the eagle-i repository provides two interfaces for obtaining lists of resources:

  • a SPARQL endpoint (currently with authentication, public SPARQL endpoint anticipated May 2012)
  • a harvest API that lists all published resources in a repository (currently with authentication)

Existing public datasets, via the harvest API:


Useful LOD references

http://www.w3.org/DesignIssues/LinkedData.html

http://linkeddatabook.com/editions/1.0/

How are we doing?

Is there anything that could be clearer in our documentation? We welcome your questions and feedback. 

  • No labels