Main Page
From Tupelo Wiki
| Table of contents |
Download
Follow this link to Download Tupelo 2
Documentation
Quick documentation links:
- Overview - an introduction to Tupelo for programmers
- API Reference - detailed Tupelo kernel API reference
- Javadoc (http://dlt-dev.ncsa.uiuc.edu/javadoc/t2/current/) for current release
- Tupelo Server Protocol - the Tupelo client / server protocol spec
- Tupelo Server Webapp - how to set up the Tupelo server implementation
- Python Support - the Python client for Tupelo Server
- Tupelo 2 Cookbook - examples of API usage (incomplete and out of date)
News
Update from 9 July 2008: Tupelo 2.3 is now available. See the Tupelo 2 page for the latest.
Update from 9 April 2008: Tupelo 2.2.0 is now available. See the Tupelo 2 page for the latest.
Update from 20 February 2008: Tupelo 2.1.0 is now available. See the Tupelo 2 page for the latest. We will be continuing to update this site with documentation in the coming days and weeks.
Update from September 2007: Tupelo 2.0.1 has been released. For information see the Tupelo 2 page.
Update from July 2007: Tupelo 2.0 has been released. For information see the Tupelo 2 page.
Welcome
This site contains information, documentation, and access to downloadable software including and related to the Tupelo semantic content repository, NCSA (http://www.ncsa.uiuc.edu/) software for managing data and metadata.
Tupelo is being developed by Joe Futrelle (http://www.ncsa.uiuc.edu/People/futrelle), Joel Plutchak, and Jeff Gaynor at NCSA. The development effort was initially primarily supported by the NEES (http://www.nees.org/) project.
About Tupelo 2
Tupelo is a data and metadata management system based on semantic web technologies. Tupelo provides a variety of generic utilities for managing large RDF graphs using best-of-breed RDF database implementations such as Jena (http://jena.sourceforget.net/) and Sesame (http://www.openrdf.org/).
Tupelo is designed for archiving large-scale, complex scientific data and metadata collections. It is also suitable for more conventional digital libraries containing Dublin Core (http://dublincore.org/) or other standard digital library metadata schemas. Its RDF-based metadata framework can support a wide variety of schemas, from simple, flat-namespace schemas such as Dublin Core, to hierarchical models derived from XML Schema (http://www.w3.org/XML/Schema), to more web-like models derived from RDF (http://www.w3.org/RDF/) variants such as RSS (http://en.wikipedia.org/wiki/RSS).
Features
- Client-side bindings for multiple RDF stores and other content management systems and protocols including
- Jena
- Sesame 1.0
- Mulgara (not included in 2.3)
- Mptstore (not included in 2.3)
- RSS
- WebDAV
- URIQA
- plain filesystem
- MySQL
- PostgreSQL
- Derby
- Server-side support for content API's including
- URIQA
- RSS
- Abstract "Context"/"Operator" model supporting
- Writing and querying RDF data to heterogeneous stores
- Reading and writing binary streams
- Merging/mirroring heterogeneous RDF and content stores
- Declarative specification and procedural execution of RDF transformation rules
- Rudimentary ability to execute SPARQL queries and SWRL rules
About the name
The name "Tupelo" comes from the word "tuple" (http://en.wikipedia.org/wiki/Tuple). It's also the name of a kind of gum tree (http://en.wikipedia.org/wiki/Tupelo) as well as the birthplace of Elvis Presley (http://en.wikipedia.org/wiki/Elvis_Presley#Birth_.26_Childhood).
Releases
Tupelo 2.3 is available here.
Previous versions
The previous major version of Tupelo is 1.1, which we're providing for historical reasons. Tupelo 2 is a complete rewrite.
It can be downloaded at the following link:
Tupelo 1 is summarized in "Tupelo: a Semantic Content Repository" presentation (pdf (http://dlt.ncsa.uiuc.edu/presentations/ggf15-futrelle.pdf))

