rapid-triples

Generate RDF using a form-based interface. Fork the template and configure it with your own form.

Overview

rapid-triples is a client-side web application that lets users fill structured forms and generate RDF (Resource Description Framework) output. The form can be customised by simply modifying the JSON Schema (form.json) and the lifting template (form-lifting.jinja) in the src/assets folder. The tool accepts all valid JSON Schemas but can be further configured following the documentation of the underlying vuetify-jsonschema-form library available here. The template follows the Jinja notation as supported by the nunjucks library (documentation).

Key features:

• Form-driven — dynamic forms rendered from JSON Schema
• No backend — everything runs in the browser
• Multiple output formats — Turtle, N-Triples, N-Quads, JSON-LD
• Auto-save — form data persists in localStorage

Quick Start

npm install
npm run dev

Open http://localhost:3000.

Available Scripts

Script	Description
npm run dev	Start Vite dev server with HMR
npm run build	Type-check and production build → dist/
npm run build-only	Production build without type-check
npm run preview	Serve dist/ locally for testing

Customize

The form can be customised by modifying the JSON Schema and the lifting template in the src/assets folder. The tool accepts all valid JSON Schemas and can be further configured following the documentation of the underlying vuetify-jsonschema-form library available here. The template follows the Jinja notation as supported by the nunjucks library (documentation).

rapid-triples supports registering more than one form in src/assets/forms-config.ts. When more than one entry is present, a Form type dropdown automatically appears in the toolbar so users can switch between forms. When only one form is registered the dropdown is hidden and that form loads directly.

Form data is persisted separately in localStorage for each form key, so switching forms never loses unsaved work.

Branding

Edit src/config/branding.ts to change the application's visual identity and global settings.

• Replace public/logo.png with your own file to change the app-bar logo.
• primary and secondary accept any CSS colour value supported by Vuetify.
• locale and vocabularyLabelLang are described in detail in the sections below.

Localisation

The UI language is controlled by brand.locale in src/config/branding.ts:

• Auto-detect (default): leave locale as undefined — the app reads navigator.language from the browser and uses the closest available bundle.
• Fixed locale: set locale: 'it' to always display Italian regardless of browser settings.

English (en) and Italian (it) are included out of the box. To add a new language:

1. Add an entry to bundles in src/assets/messages.ts, keyed by its language tag:

2. Set brand.locale' in src/config/branding.ts, or leave it undefined to rely on browser auto-detection.

If a bundle is not found for the detected locale, the app falls back to English. All translatable keys are declared in the Messages interface at the top of messages.ts.

Controlled Vocabularies

rapid-triples can populate form dropdowns from SKOS RDF/XML vocabulary files without any backend. Each vocabulary is loaded at startup and injected into the form context so Nunjucks templates can map selected labels to their full IRIs.

Adding a Vocabulary

1. Place the SKOS RDF/XML file under public/vocabularies/ (e.g. public/vocabularies/licenses.rdf). The file must use the standard SKOS namespace (http://www.w3.org/2004/02/skos/core#) and include skos:prefLabel elements for each concept. Fully-qualified URLs are also accepted as sources.

2. Register the vocabulary in src/assets/vocabularies.ts by adding an entry to the VOCABULARIES array. Multiple source files are merged and deduplicated by IRI before being sorted alphabetically.

3. Reference in your JSON Schema using getItems with an expression pointing to context.vocabularies.<vocabulary-id>. Each entry exposed to the form is a VocabularyEntry object with label (skos:prefLabel, capitalised), iri, and broaderIris (array of broader concept IRIs via skos:broader).

4. Resolve to IRI in the Jinja template using the vocab_map variable, which is automatically injected at render time as a map of maps: { [vocabulary-id]: { [label]: iri } }. Use an IRI-detection pattern to also accept values that are already IRIs (e.g. pasted directly).

Tip: Set brand.vocabularyLabelLang in src/config/branding.ts to prefer labels in a specific language (e.g. 'it') when the vocabulary contains multi-language skos:prefLabel values.

Docker Deployment

Build the image:

docker build -t rapid-triples .
docker run -p 8080:80 rapid-triples

Visit http://localhost:8080/rapid-triples/.

Or use publish.sh to extract the static build without a local Node install:

bash publish.sh
# → dist/ contains the production build

Note: The base path in vite.config.mts is set to /rapid-triples/ for production builds. If you deploy the app under a different sub-path (or at the root), update the base option accordingly:

base: process.env.NODE_ENV === 'production' ? '/your-sub-path/' : '/',

Cite as

If you use rapid-triples for publications, cite the following article:

Scrocca M., Carenini A., Carriero V. & Celino I. (2025). rapid-triples: Adaptive Forms for Semi-automatic Knowledge Collection in RDF. In: 1st Workshop on Bridging Hybrid Intelligence and the Semantic Web (HAIBRIDGE 2025) co-located with the 24th International Semantic Web Conference (ISWC 2025). CEUR-WS. https://ceur-ws.org/Vol-4093/Paper4hai.pdf

Contributing

Before contributing, please read carefully, complete and sign our Contributor Licence Agreement.

When contributing to this repository, please first discuss the change you wish to make via issue or any other available method with the repository's owners.

License

Copyright (c) Cefriel.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0