Install fuseki with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• fuseki-backup
• fuseki-plain
• fuseki-server

Project history

Jena began at HP Labs in Bristol in 2000 as an open-source Java framework for Semantic Web applications. Apache's Jena history page says HP reduced direct development support in 2009, the project applied to enter the Apache Software Foundation in November 2010, and Jena graduated as an Apache top-level project in April 2012.

Fuseki grew as the server-facing distribution within Jena: the Fuseki documentation presents it as the SPARQL server integrated with TDB for robust transactional persistent storage and with Jena text query. The Jena downloads page packages Apache Jena and Apache Jena Fuseki as the two binary distributions for the most commonly used portions of the system.

Adoption history

Jena's own history page says the project has been extensively used in a wide variety of Semantic Web applications and demonstrators. Fuseki is the deployment-oriented piece of that stack, giving RDF and SPARQL users a server rather than only Java APIs and command-line tools.

Its adoption follows standards adoption: Fuseki exposes W3C SPARQL 1.1 protocols and Graph Store HTTP RDF Update, so it became a package for running standards-compliant RDF endpoints in development, research, and production Semantic Web systems.

How it is used

Fuseki can be run as a standalone server, as a service, as a web application, in a plain mode, or embedded in another application. Configuration can come from `$FUSEKI_BASE/configuration/`, the system database, `$FUSEKI_BASE/config.ttl`, or command-line and programmatic setup depending on the Fuseki mode.

Security for the Fuseki2 web application uses Apache Shiro, controlled by `$FUSEKI_BASE/shiro.ini`. The documentation notes that if the file is absent the server initializes with a default configuration that can be replaced or edited.

Why package nerds care

Fuseki matters to package people because it is the installable server boundary for Jena: a Java Semantic Web framework becomes a service with ports, config directories, security files, persistent stores, and command-line launchers. It is also a good example of an Apache project where a language library, server distribution, Maven artifacts, and OS packages all describe the same upstream.

Timeline

• 2000: Jena development starts at HP Labs in Bristol.
• 2009: HP refocuses development activity away from direct Jena support.
• 2010: Jena is adopted into the Apache Software Foundation incubator.
• 2012: Jena graduates as an Apache top-level project.
• Current docs: Fuseki is documented as the Jena SPARQL server with TDB integration and Shiro-based webapp security.

Related projects

• Fuseki is part of Apache Jena and is closely related to Jena ARQ, TDB/TDB2, RDF Connection, Jena text query, and GeoSPARQL modules.
• Its security documentation depends on Apache Shiro, and its network role is defined by W3C SPARQL and RDF graph-store protocols.

Sources

• https://github.com/apache/jena
• https://jena.apache.org/about_jena/about.html
• https://jena.apache.org/documentation/fuseki2/fuseki-configuration.html
• https://jena.apache.org/documentation/fuseki2/fuseki-security.html
• https://jena.apache.org/documentation/fuseki2/index.html
• https://jena.apache.org/download/index.cgi