Table of Contents

Introduction

AllegroGraph's triple-stores now support Callimachus. This support has two levels. Firstly, AllegroGraph will automatically add (and delete) soundex-based indexing triples as you add regular triples to your store. For example, if you add the triple

Secondly, AllegroGraph will add auditing triples to your store whenever a SPARQL UPDATE command deletes a triple (and the insert-graph-uri is set). The details of the auditing triples are beyond the scope of this document but are designed to track provenance and change activity.

Callimachus support must be turned on before a store will begin adding Soundex or Auditing triples. You can turn on Callimachus behavior by sending an HTTP POST request to your store:

POST .../repository/STORENAME/callimachus

You can also make Callimachus behavior the default for the server using the AllegroGraph configuration file.

Configuration File

There are two configuration parameters that allow AllegroGraph to support Callimachus:

Callimachus - This can either yes or no and defaults to no. When it is yes, then every triple-store created by this server will default to acting as a Callimachus store (you can still pass the parameter to create-triple-store to make a non-Callimachus store).

CallimachusDataDir - This tells AllegroGraph where to look in order to find the auxiliary files Callimachus uses to configure its Soundexing support. Generally speaking, you should not need to set this value. It defaults to the lib/soundex-data/ directory of your server installation.

SPARQL soundex filter functions

AllegroGraph associates

<http://www.openrdf.org/rdf/2011/keyword#soundex>

and

<http://www.openrdf.org/rdf/2011/keyword#regex>

with the functions Callimachus uses to create its soundex-based text index. This means that you can use them in FILTERs and other SPARQL expressions. For example, to find every subject whose soundex matches that of tess, we could write: