Page History
...
- 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. Third party applications can also 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/:
*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, public SPARQL endpoint forthcoming)
- a harvest API that lists all published resources in a repository (currently with authentication)
Existing public datasets, via the harvest API:
- University of Alaska Fairbanks
- Dartmouth College
- Harvard University
- Jackson State University
- Morehouse School of Medicine
- Montana State University
- Oregon Health and Science University
- University of Hawaii at Manoa
- University of Puerto Rico Medical Sciences Campus
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. http://www.cambridgesemantics.com/semantic-university/sparql-101
Overview
Content Tools