Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • 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 data in 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.is contributed by Network member institutions. This data can be freely searched using our central search application, but it is also available three other ways, also reachable through https://www.eagle-i.net/export/:

  1. Public SPARQL Endpoints
  2. RDF downloads
  3. Lists of URIs*

*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?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)
  • a harvest API that lists all published resources in a repository (currently with authentication)

...

Useful LOD references

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

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

http://www.cambridgesemantics.com/semantic-university/sparql-101