Versions Compared

Old Version 2

changes.mady.by.user Julie McMurry

Saved on

compared with

New Version 3

changes.mady.by.user Daniela Bourges-Waldegg

Saved on

Key

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

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. Other applications can access the data to present different views of it, incorporate it in other websites, etc.

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-f22c80000005Image Added

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

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

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

  • a SPARQL endpoint (currently with authentication)
  • a harvest API that lists all published resources in a repository (currently with authentication)

The eagle-i team is in the process of developing public versions of these two interfaces. The upcoming release will include a public version of the harvest API, so stay tuned for examples of eagle-i resource lists.