Chapter 1. Introducing Callimachus

This part provides you with an introduction to Callimachus, what it is and why you would want to use it.

1.1. Where the name Callimachus came from

1.1.1. Who he was

This project was named after Callimachus the father of Bibliography who worked at the ancient Library of Alexandria.

Callimachus lived during 305-240 BCE.

Illustration: Great Library of Alexandria

Callimachus

  • could not categorize his own work by using Aristotle's hierarchical classification system (a problem now known as "Callimachus’ Quandary"), and therefore

  • was the first person to define the use case for Linked Data!

1.2. Callimachus features

1.2.1. Allows new data to be easily integrated with existing data

Callimachus makes data easy to create, view, and update. Integrating new data with existing data is much easier to accomplish compared to using relational databases.

1.2.2. Displays linked data in visually appealing web pages

A new user can easily import linked data and rapidly transform it into attractive web pages and editable forms.

1.2.3. Allows applications to be changed while in production

Callimachus queues and locks the data store to allow uninterrupted service while changes are made to application

1.3. Who is using Callimachus

Here is a recent sample of organizations that have adopted Callimachus by sector. For competive reasons some names are not mentioned.

1.3.1. Government

Callimachus will soon host all the data published as Linked Open Data for the US Environmental Protection Agency (EPA). The system is currently in the final phases of a security review, and is due to launch in 2013. It combines US EPA data on 1.3 million facilities regulated by the US EPA. This includes data ranging from dry cleaning operations to nuclear power plants, and reports on toxic chemicals emitted over the last 25 years.  It cross links to chemical substance databases, Open Street Maps, DBpedia content and much more.

1.3.2. Healthcare

Callimachus is used by Sentara, a regional healthcare delivery and payer organization that insures 400,000 lives. Sentara is developing a Web and mobile application called 'Weather Health'. The application combines data from the US National Library of Medicine, National Oceanic and Atmospheric Agency (NOAA), US EPA and DBpedia to better respond to chronic conditions, and reduce costly emergency visits. 

The Weather Health is project considered to be a "national good" by Sentara.  They dedicated the application to improving healthcare outcomes and reducing the cost of healthcare delivery in the US by empowering patients with timely, relevant information. 

1.3.3. Pharmaceuticals

Callimachus is being used as a knowledge management platform by a major pharmaceutical company to combine enterprise data with open data from the Web.  This KM solution was developed in 2012 and is slated to go into phase 1 production in 2013.

1.3.4. Publishing

Callimachus is being used to power an agile publishing workflow for an international business publisher. The system combines content from company document management stores with open Web content and a variety of enterprise systems.  The system was developed in 2012 and is anticipated to be used throughout North America by up to 400 editors in 2013.

1.3.5. Research 

Researchers in Europe, Brazil and the United States are using Callimachus to standardize metadata and combine data from different systems.  In one example, researchers in Finland created a "virtual machine laboratory" to track mechanical parts in industrial assembly lines.  Callimachus was used to host information about each part, including how parts related to other parts.

1.4. What developers are saying about Callimachus

1.4.1. Actually makes it easy to create a linked data application

“Tools I've been using include Protogé, Google Refine and Callimachus. It is the only development tool I have found that actually makes it easy to create a linked data application.”

1.4.2. All you need is a browser

“The user interface is consistent and all you need is a browser.”

1.4.3. RESTful from the ground up

“Callimachus is RESTful from the ground up.”

1.4.4. Confidence in the deep knowledge of the development team

“I have confidence in the expertise and deep knowledge of the development team.”

1.4.5. Handles change history well

“Wiki Systems don't handle structured content well nor promulgate change well. Callimachus focuses on structured content and handles change history well.”

1.4.6. Keeps unnecessary details hidden

"Callimachus keeps lots of the details hidden that I don't want or need to see. It allows me to see the ontology on the level that I need to."

1.4.7. Allows ontologists to work with UI experts

"There is a difference between the ontologists & UI guys [who work in HTML/CSS]. Using Callimachus, the UI guys don't have to become ontology experts and the ontologists don't need to look under the hood at the UI code."

1.4.8. Absolutely necessary glue for Web apps

"It provided easy to use, absolutely necessary "glue" for producing data drive Web apps."

1.4.9. Enables a focus on business direction not the UI

"With Callimachus, I'm getting that shorter path to the technical resolution for that I'm trying to deliver. Allows me to focus on the business direction and not the UI"

1.5. Developer prerequisites

1.5.1. Web standards

Callimachus developers should be familiar with current Web standards, especially HTML version 5, CSS version 3 and JavaScript.

As well some knowledge of transforming data using XML technologies is helpful, especially XSLT and the recent XML pipeline language, XProc.

1.5.2. Linked data standards

Callimachus developers should also be familiar (or prepared to become familiar) with the standard for linked data - the Resource Description Framework (RDF).  In particular, they need to learn how to use RDFa as a means of annotating HTML tags with data via the addition of attributes.

1.5.3. Reference documents

The developer should refer to the following documents as required:

HTML 5

CSS 3

RDF

SPARQL

XSL

Xproc


Chapter 2. Getting Callimachus Up and Running

2.1. Installing Callimachus

2.1.1. Introduction

Callimachus includes a setup script that is used to intialize a new and upgrade an existing Callimachus instance. Follow the procedure below to install the latest Callimachus distribution.

2.1.2. Procedure

Step Action
1

Check if a Java Development Kit (JDK not just a JRE) is installed and that the version is correct. Callimachus requires different JDK versions depending on what version of Callimachus you are using. If you are using:  

  • Callimachus 1.1.1 and earlier requires JDK 1.6 (1.6.0_20 or higher, but not 1.7)
  • Callimachus 1.1.2 can work with either JDK 1.6 (1.6.0_20 or higher) or 1.7
  • Callimachus 1.2 and later require JDK 1.7

From the command prompt issue the command: java -version and javac -version to see what version is locally installed. You can also issue the command: which java to see the directory where it is installed. Install a Java JDK if it is not yet installed.

NB: Callimachus will not work with JDK version 8 at this time.

2

Download the .zip file for the latest version of Callimachus from http://callimachusproject.org and unzip it into an empty target directory.

3

Copy the file etc/callimachus-defaults.conf to a new file called etc/callimachus.conf. Open etc/callimachus.conf in a text editor and make the following changes as necessary:

  • Remove the '#' before the PORT and ORIGIN variables and edit them to match the appropriate values for your system. The value of ORIGIN must match exactly what will be in the browser's address bar before the path. Set the PORT variable to 80 if you want to be able to access Callimachus without a port number in the URL. Warning: After the setup script has been run, the ORIGIN variable cannot be changed without reinstalling Callimachus.
  • Create a file called mail.properties in the etc/ directory to allow for mail functionality within Callimachus. 
4

Run the Callimachus setup script from a console to initialize Callimachus.

For Mac and Linux Desktop users:

  • Run bin/callimachus-setup.sh and follow any prompts.

For Linux Server users (as root):

  • Run bin/callimachus-install.sh
  • Run bin/callimachus-setup.sh

For Windows Users:

  • Run bin/callimachus-setup.bat and follow any prompts.

Note: In Callimachus 1.1, instead of being prompted for a password during the setup script, you will be provided a URL at the end of the setup script. Once you have started the server, access that URL and setup your initial password. If you lost the URL (and setup mail.properties correctly) you can receive a temporary password via email using the "Need another password?" button on the sign in page.

5

Setup your initial user account and password by copying and pasting the URL provided at the end of the setup script into the browser. If your operating system supports it, you are have a local windowing system and a Web browser, the setup script will open your default browser to the login screen so you won't need to copy and paste the URL.

The setup URL will take you to the login screen:

Initial user login screen

You will then be asked to create a username and password for the initial user:

Initial user sign in

Some things to know:

Note: You should set up your initial user right away.  Run the setup script again if your initial user invitation expires.

Note: To stop the server at any time, run bin/callimachus-stop.sh (Mac/Linux) or bin/callimachus-stop.bat (Windows)

Congratulations, you've installed Callimachus succesfully! If you think something is not working correctly or some part of the installation process has gone wrong, please post to the discussion group.

2.2. Browser support

This describes the browsers that are supported by Callimachus.

2.2.1. Supported browsers

We support the current and previous major releases of Chrome and Firefox on a rolling basis. Each time a new browser version is released, the following Callimachus release will begin supporting that browser version and stop supporting the third most recent browser version.

2.2.2. Partially supported browsers

Callimachus provides partial support for the following

Browser Issue
Safari 6, 7
  • Drag and drop from the local file system into browser is not supported.
  • Does not support logging in with email address via digest access.
  • Does not retain the login state in all cases.
Internet Explorer 9, 10 and 11
  • Cannot upload files in .docbook format. Docbook documents must be created within Callimachus.
  • Drag and drop from local file system into browser is not supported.
  • Client-side validation when creating a concept is not functioning. Be careful to always enter a Label for concepts.

2.2.3. Unsupported browsers

Callimachus does not support

  • Internet Explorer 6
  • Internet Explorer 7
  • Internet Explorer 8

2.3. Adding users

To add a new user, an existing user who is part of the "admin" group must:

  1. Navigate the /admin URL.
  2. Select a group into which the new user is being added.  That group's edit template will be accessed when the link is clicked.
  3. Invite a new user using the icon in the Members field.
  4. Complete a user invitation form for the person to add.
  5. Save the group.
  6. Add the user to other User Groups as needed by clicking on the Members icon and using the lookup search box in the dialogue.

The new user will recieve an email invitation with a registration link and instructions on how to log in.

It is necessary for Callimachus to send email in order to invite new users!  Make certain that your etc/mail.properties file is correctly configured before you attempt to invite users.  If your users do not receive invitations, check the etc/mail.properties file for correctness first.

The /admin screen is shown in the following screenshot.  You are advised to follow the Principle of Least Privilege when adding users to groups.  Select the appropriate group:

Then add one or more members:

Editing group membership

Selecting the icon to the right of the Members header will display a new user invitation form:

The new user invitation form

When you have finished editing the group, don't forget to save your changes!

Saving a group

A user invitation email message will look something like this:

User Invitation Email

2.3.1. The Super Group

There is an additional group that is present in Callimachus by default: The "super" group.  Members of the super group have privileges to view and modify content in the /callimachus folder tree.  That is, they may modify the core of a running Callimachus instance.

The super group is useful for users wishing to fully explore Callimachus or to experiment on a running instance.  The Callimachus development team uses the group on a regular basis to develop the product.

However, enabling the super group can also be dangerous, especially for those systems that are accessible from the public Internet.  Any user account that is subverted and has membership in the super group will have permissions to modify many aspects of Callimachus.  So, we strongly recommend that Internet deployments not give user accounts membership in the super group.

The preferred way to put yourself into the super group is to check out the source code and then follow the directions in the README file under the Installation section.  Specifically, you may provide a username, email and password to Callimachus by creating a build.properties file in the same directory as build.xml. The username you provide will be placed into the super group.  Put the variables "callimachus.username", "callimachus.email", and "callimachus.password" followed by '=' and their value on their own line. Copy src/callimachus-defaults.conf to etc/callimachus.conf and edit file as above.

You can then execute 'ant run' from a command line in this top directory to run the server. If some files fail to download you may have to run "ant clean dist" and run "ant run" again.  This runs the Callimachus server from the source code checkout.

You may then make any changes you wish to the /callimachus folder tree by editing the files in the browser using Callimachus' development features.  Issuing 'ant pull' from the command line will pull your changes back into your local filesystem's source tree.  Note that you might wish to commit those changes into your local revision control system from there.

Any files that you modify outside of the /callimachus folder tree will be unaffected by 'ant pull'.

Do not use the super group for Callimachus instances that are deployed to the public Internet.

You can optionally create the initial Callimachus user in the “super” group at setup time by running the setup script with the -g flag.  This is not generally recommended, but may be useful for some developers when running Callimachus on their own local computers:


bin/callimachus-setup.sh -g /auth/groups/super

or, for Windows:


bin\callimachus-setup.bat -g '/auth/groups/super'

Once the initial user is a member of the super group that user will have permission to invite other users into that group.

2.4. Starting and stopping the Callimachus server

2.4.1. Purpose

This describes how to start and stop the Callimachus server.

2.4.2. Procedure

Step Action Example
1 From the command prompt navigate to the Callimachus directory. ../3RoundStones/callimachus-1.0
2 Start the server by running the callimachus-start.sh script from the /bin directory. bin/callimachus-start.sh
3 Stop the server by running the callimachus-stop.sh script. bin/callimachus-stop.sh

Note: Always stop the Callimachus server before starting it again.

2.5. Starting the Callimachus client

2.5.1. Instruction

To start the Callimachus client in your browser enter: http://localhost:8080/

Note: This assumes you are running the Callimachus server on the same machine you are accessing it in your browser. Replace localhost with the host name and if applicable, the port number of the server you are using.

2.6. Sample Callimachus applications

New developers should see the tutorials listed on the main documentation page, especially the Developers Tutorial.

Currently, these sample applications are available:

Callimachus Sample Applications
This application... Demonstrates...
Quotes This application demonstrates Named SPARQL Queries and their use within HTML pages.
School Wards This application provides more familiarity with HTML form fields, such as radio, checkbox, and select options.
Meeting Notes This application shows the use of nested resources. Each Meeting instance may have Note instances associated with it.
Directory This application demonstrates how to create new resources with complex structure and create and edit forms with embedded resources.

Callimachus applications are packaged as CAR files, and can be installed by importing the contents of the sample application into a newly created folder. 

  • Choose one of the sample applications over and download the .car file.
  • Once a user account is created:
    • Log in and choose 'Home folder' in the main menu.
    • Click the Create button at the upper left of the folder display and choose 'Folder' from the menu options.
    • You will be asked to name the new folder and will then be placed into it.
    • Choose 'Import folder contents' in the Main Menu at the upper right of the folder display.
    • Select the .car file previously downloaded.
    • Select the radio button "Replace this folder's contents".
    • Select the Import button to import the CAR contents into your new folder.


Chapter 3. A Short Introduction to RDF

In this chapter we briefly describe what RDF is, what its advantages are and how it works in Callimachus.

3.1. About RDF

3.1.1. Introduction

The Resource Description Framework (RDF) is a W3C standard for modelling linked data. The purpose of linked data is to enable data from different sources to be easily and meaningfully linked together, thereby making it more useful.

3.1.2. Triples

RDF represents data as simple sentences called “triples”. A triple is made up of a subject, predicate and object. 

3.1.3. Car ownership modeled as triples

A triple can be visualized as a graph, where ovals represent the subject or object of the sentence, while arrows represent the predicates (i.e. the relationships).

3.2. Advantages of RDF over relational databases

3.2.1. Expanding your data horizons

With RDF one resource can be combined with any other resource by making an assertion about the relationship (a triple). This makes it easy to expand a database that has been implemented using RDF.

3.2.2. Advantages of RDF over relational databases

External data Inferencing Schema New attributes Query structure
Relational Database Merge schema Not supported Required Requires migration Optimized for updates
RDF Database Identify redundencies Optional Optional Added on the fly Faster joins

3.3. RDF resource

3.3.1. Definition

An RDF resource is any person, place, event, object (i.e. anything) that can be uniquely identified by using a Uniform Resource Identifier (URI). 

3.3.2. Examples

Data concerning:

  1. A store

  2. An item in a store

  3. The price of an item in a store

  4. Someone’s opinion about the price of an item in a store

  5. and so on...

In Callimachus the domain, folder path plus resource name combine to form the absolute identifier of the resource.

3.3.3. Adding meaning by using vocabularies

When naming resources developers are encouraged to use terms from commonly used controlled vocabularies or "ontologies".  Controlled vocabularies make it possible to construct queries that relate otherwise disparate datasets.

3.3.4. Commonly used vocabularies

Below are some widely used vocabularies for naming and describing resources.

Vocabulary  Description Searchable QNames
Dublin Core Fifteen properties frequently used to describe resources, similar to the type of information found on a library card.
Friend of a Friend (FOAF) A vocabulary for linking people and information about them.
Freebase A repository of open data containing almost 23 million entities.
GoodRelations A vocabulary for describing products and services.
GeoNames A vocabulary with the official geographical names for all countries and containing over eight million placenames.
Open Graph Protocol A vocabulary for describing "rich objects" in a Facebook social graph.
RDF Schema (RDFS) A vocabulary for structuring RDF resources.
Semantically-Interlinked Online Communities (SIOC) A vocabulary for linking online communities.
Simple Knowledge Organization System (SKOS) A vocabulary for organizing knowledge contained in thesauri, classification schemes, subject heading lists and taxonomies.
Vcard A vocabulary for the type of information that might be found on a business card.

Note: QName stands for "qualified name" and enables the abbreviation of URIs. The QNames shown here are used to lookup resources  in Callimachus.

3.4. RDFa

3.4.1. What it is

RDFa is a W3C standard used to embed RDF data directly inside web pages by using attributes - hence the 'a' in RDFa. While RDFa is similar to microdata and microformats, it offers important advantages such as being able to use multiple vocabularies in the same page.

Source: Executive Briefing on Linked Data

Like a credit card, web pages that use RDFa have both a human-readable as well as a machine-readable side. 

3.4.2. RDFa attributes

RDFa uses the attributes shown below to embed meaningful data in the page by forming triple statements.

Subject or resource Predicate Literal values
  • @about

  • @resource

  • @href

  • @src

  • @property

  • @rel

  • @rev

  • @content

  • @datatype

  • @xml:lang

  • text()

3.4.3. How Callimachus uses RDFa attributes

Callimachus extends the RDFa syntax by allowing variables as well as URIs to be used in attributes. This allows data to be updated directly in web pages, as well as displaying updated data as it changes.

Callimachus further extends the RDFa syntax by introducing expressions that allow values to be substituted within attribute values or within text nodes.

The table below describes the purpose of each RDFa attribute and how it is represented in Callimachus.

Attribute

Purpose

Representation

@about and @src

Specifies the resource that the metadata is about.

Variable or URI

@rel and @rev

Specifies a relationship or a reverse-relationship with another resource (sometimes called object property).

Reserved keyword or CURIE

@href and @resource

  1. Specifies the partner resource of rev or rel, or

  2. Specifies the resource the metadata is about for property (when rev or rel is not present).

Variable or URI

@property

 Specifies a CURIE property for the content of an element (sometimes called datatype property).

CURIE

@content

An optional attribute that overrides the content of the element when using the property attribute.

A plain literal (string)

@datatype

An optional attribute that specifies the datatype of text specified for use with the property attribute.

@typeof

An optional attribute that specifies the RDF type(s) of the subject.

Note: Callimachus converts the attributes into graph patterns. Blank nodes and empty property contents are treated as wildcards. Graph patterns with wildcards or variables partners are optionally joined in the result.


Chapter 4. Callimachus User Interface

This describes the main features of the Callimachus user interface.

4.1. Main menu

4.1.1. Description

The main menu is represented as a small icon beside the Look-up box, and provides system-level functions when clicked.

Screenshot: main menu

Menu item Function
Home folder Brings you to the root folder. From the root folder you can navigate and modify the site.
Recent changes Displays recent changes to the site.
About Callimachus Takes you to the Callimachus project home.
Getting started Takes you to the Callimachus Getting Started document.
Send feedback Allows you to send feedback using Google Groups.
Help Page sensitive help links, if applicable (opens in a new browser).
Other links Other pages specific links may also appear.
What links here Displays other resources that are linked to the current one.
Related changes Displays changes related to the current resource.
Permissions Displays and allows permissions to the current resource to be changed.
Introspect resource Inspect the components that comprise a resource.
Print this page Print the current page.
User name Takes you to your user page where you can change your password or email address.
Sign out Signs you out of Callimachus.

4.2. Home Folder Edit Tab

The Edit tab of the Home Folder serves as a control dashboard for many crucial functions within Callimachus. 

4.2.1. Access

To access the Home Folder Edit tab simply navigate to the Home Folder via the Main Menu and click the "Edit" tab.

4.2.2. Components

Realm Settings

Realm settings determine are applied across an entire Callimachus instance and control some of the fundamental access and presentation aspects.

Layout

Layout is the extra markup that is applied to every xhtml template within a Callimachus instance. This is the easiest way to apply common layout and styling across your Callimachus pages and applications. To creating a custom Layout follow the steps below.

Step Action Example
1 Click the widget below Layout
2 Replace the layout name with a new one Customized Layout
3 Choose the Add new layout option
4 Choose a folder to save the new layout
5 Modify the layout as desired
6 Click the layout dialogue Save button to store the new layout
7 Click the realm Save button to apply the layout

The layout file is a XQuery file that utilizes most of the Callimachus layout functions. Callimachus utilizes the Bootstrap framework which makes both formatting and styling much easier for everyday developers. Check out Bootswatch for free Bootstrap themes that will integrate with Callimachus seamlessly. The theme can be either downloaded locally or referenced via a <link> tag. In your Callimachus Layout file simply paste the link underneath {calli:styles-href(<link rel="stylesheet" />)} in this manner:

{calli:styles-href(<link rel="stylesheet" />)}
<link rel="stylesheet" type="text/css" href="http://bootswatch.com/flatly/bootstrap.min.css" />
Allowed Origins

Allowed origins are origins from which scripts can make requests to a Callimachus instance. For example, if Callimachus was installed at http://host.example.com and had an Allowed Origin of http://allowed.example.com, scripts located on allowed.example.com could make requests to host.example.com. If you do not want your Callimachus instance to be made available to other origins then the only Allowed Origin should be the origin at which your instance is installed. 

This origin configuration is in line with the CORS specification. 

Authentication

Different authentication options can be managed from this tab. A list of the authentication mechanisms currently applied to the Callimachus instance are rendered by default. 

Authentication options can be added via the icon next to "Authentication." They can be removed by clicking the small "x" next to the authentication option. Be aware that by clicking this "x" you are only removing the authentication mechanism as an option for logging in, but not deleting the authentication configuration itself.

Credentials

Credentials are managed via the Home Folder Edit tab. A list of the credentials currently applied to the Callimachus instance are rendered by default. 

Credentials can be added via the icon next to "Credentials." They can be removed by clicking the small "x" next to the credential listing. Be aware that by clicking this "x" you are only removing the credential from use in the current instance, but not deleting the credential configuration itself.

Directory Index

Directory index settings determine how requests directly to the Home Folder should be handled.

Type

The type is the response code that is sent. For more information on exactly what these types represent read the PURL documentation.

Content Location

Content location is the resource that should be returned to the browser when the Home Folder is requested. This is the best way you can set the home page for your Callimachus instance. Generally this is some sort of landing or index page for your application or system.

Cache Control

Cache control is used to control how often the content will be refreshed for users of a Callimachus instance. The value entered will determine exactly how the system responds to multiple requests for the same resource over a given period of time. For a list of the available values for this field please see the specification section "cache-response-directive". An example value would be "max-age=3600".  

4.3. Create menu

4.3.1. Description

The create menu is represented as a red button with the label Create when navigating folders. When pressed it provides a submenu of resources that are used to build Callimachus applications.

Screenshot: Create menu

4.4. Folders

A Callimachus folder is a way to group files/resources. A folder may contain any of the following

  • File resources,
  • Folder resources, or
  • RDF resources

To create a folder, select Folder using the create menu from the folder you wish to create the new folder in.

Pragma Description
?contents Atom feed of the folder's contents
?changes Atom feed of the changes to files or resources within the folder
?archive Download a CAR file of the containing files and resources, or 404 if the folder is empty
PUT ?archive Replaces the files and resources within the folder with the archive in the request body
DELETE ?archive Removes all files and resources within the folder
?create=... Responds with the create form of the given class

4.4.1. Deleting the contents of a folder

To delete the contents of a folder

  • Click on the Edit tab
  • Use the Delete button to delete the folder and its contents

4.4.2. Granting folder permissions

To grant permissions to a folder, navigate to the desired folder and select Permissions from the main menu.

Lookup and add User Group(s) to the appropriate Role to assign permissions.

Role Permissions
Reader Redirected to the folder's index target (configured in the edit tab)
Subscriber View file listing, see the history, and discuss the folder
Contributor Create new resources in this folder
Editor Make changes using the edit tab and create new resources in this folder
Administator View, create and modify using any available operation

4.4.3. Exporting and importing the contents of a folder

Callimachus compresses and stores the contents of folders in CAR files. To export or import the contents of a folder, navigate to the folder and open the main menu.

If you click the Export folder contents entry, you will be prompted for a location on your computer to save the CAR file. If you click Import folder contents you will be prompted to specifiy the CAR file you wish to import. CAR files can either be imported and create/replace a subfolder or replace the current folder's contents.

4.5. File

Callimachus supports some binary and text files, ZIP files and Callimachus Archive File (CAR) files. 

4.5.1. Binary and Text Files

Binary and text files are used to store many of the types of Callimachus resources and are the building blocks for all Callimachus applications.

Adding, deleting or renaming a file

To add a file

  1. Click the upload file button, next to the create menu, from the folder you wish to store the file in, then
  2. Using the file upload dialogue upload the file from your computer

To delete a file

  • navigate to the folder with the file you want to delete, then

  • open the file, click on the edit tab and press the Delete button

To rename a file (not all types of files can be renamed)

  • navigate to the folder with the file you want to rename

  • click on the edit tab and press the Save as... button

  • save the file with its new name

  • delete the older file

4.5.2. ZIP Files

ZIP files can be used to import files in bulk. Files from a local filesystem can be archived together and imported into a folder at once. However, the entire folder's content must be imported at once.

4.5.3. Callimachus Archive Files

A Callimachus Archive File (CAR) file has the .car extension and contains the contents of a folder at some point in time. CAR files are used to backup and restore Callimachus applications, as well as to transfer large amounts of RDF data between systems.

4.6. Resource browser

4.6.1. Description

The resource browser provides a convenient way for users to view, modify, discuss and find out more about an RDF resource or a Callimachus  resource. It consists of the five tabs shown below. Access to tabs depends on user permissions.

Screenshot: The Resource Browser

4.7. View tab

4.7.1. Description

The resource browser View tab shows the resource rendered for viewing according to its type.

Screenshot: View tab for a DocBook article

Note: For the View tab to be active for an RDF resource, it must be of a class that has a view template associated with it.

4.8. Edit tab

4.8.1. Description

The resource browser Edit tab allows the resource to be edited depending on its type.

Screenshot: Edit tab showing a DocBook article

Note: For the Edit tab to be active for an RDF resource, it must be of a class that has a edit template associated with it.

4.9. Discussion tab

4.9.1. Description

The resource browser Discussion tab allows changes to a resource to be discussed.

Screenshot: Discussion tab allowing discussion about a DocBook article

4.10. Describe tab

4.10.1. Description

All resources in Callimachus are stored as OWL/RDF, and the resource browser Describe tab shows the RDF that describes the current resource.

Screenshot: Describe tab showing the triples for the main article

4.11. History tab

4.11.1. Description

The resource browser History tab shows in chronological order the changes made to a resource.

Screenshot: History tab showing the changes to a DocBook article


Chapter 5. More About Callimachus

5.1. Further Reading

  • Web Developer's Guide introduces developers on how to develop linked data applications using Callimachus.

  • Administrator's Guide explains the authentication and authorization used in Callimachus.

  • Reference is a technical description of the various options and functions available to Web developers in Callimachus.

5.2. Callimachus Support

3 Round Stones offers commercial support and private virtual cloud hosting for enterprises running Callimachus.

Commuity support may be access through our mailing list.