A local-first SKOS workspace
Informed building, not blind building. Augmentation, not automation.
Intentional Arrangement
Saved locally
Build
Validate
Concepts
Museums
↳ Exhibitions
↳ Artists
Museum
A place that collects, preserves, and interprets objects of cultural, artistic, or scientific importance.
qSKOS check ready
The browser is the workspace
Validate as you type
Use qSKOS quality checks to catch structural problems before they harden into your vocabulary.
Export in seven formats
Move between Turtle, RDF/XML, JSON-LD, CSV, Excel, RDF/JSON, and Markdown without locking your work into one system.
Run entirely in your browser
Projects autosave in this browser—not the cloud. Export RDF or download a workspace backup regularly: clearing browser data can erase local work.
Collect first. Structure next.
Gather candidate terms in the Glossary, then promote them into concepts. Build multilingual labels, definitions, and poly-hierarchies; review proposed terms before approving them.
Connect without losing context
Align vocabularies with five SKOS mapping relations. Review suggested matches, preserve original URIs, and export a pair or an entire federation. Track documents and agents as sources.
See the structure. Ask questions.
Explore concepts, sources, and mappings in the graph. Run SPARQL in your browser, or share a read-only Business view. Plain-language queries use offline rules—not an LLM.
Why it works this way
Source-available, not OSI open-source. Free under the size-based license for organizations with fewer than 75 employees; a written enterprise license is required at 75+. Your taxonomies remain yours.
Runs in your browser
No account or server default. Your work stays close to you.
Standards first
SKOS, SKOS-XL, Dublin Core, ISO 25964, and qSKOS inform the working model.
Collections are not hierarchy
Alternative groupings sit alongside a taxonomy rather than distorting it.
Share by choice
Export portable files or create a read-only link when you are ready.
Keep the work moving
Roadmap
See what is being refined, tested, and planned next.
Discussions
Bring questions, ideas, and practical edge cases into the open.
Request a feature or report a bug
Help improve the workspace with a concrete need, a snag, or a new use case.
Need to integrate? Use the optional REST API for validation and conversion, or the MCP server for assistant tools. Apache Jena Fuseki publishing is optional—the browser editor does not require a server. Cloud sync and an AI taxonomy copilot are planned offerings, not current browser-editor features.
