Early developmentNot everything described here has shipped yet.

All use cases

Government · Public sector

Authority data your whole network can maintain

Public bodies keep the reference data everyone else builds on: place names, classifications, subject headings, registers of institutions. It is fed by many hands, curated by few, and expected to be authoritative. NeoWiki makes it governed structured data: validated at entry, attributed per change, published as linked data, and hosted where your rules require.

Watermillpreferred termstatus approvedMillWikidata itembroader termsame as

Everyone depends on it, nobody quite owns it

Public bodies keep the data other systems key on: place names, classifications, subject headings, registers of institutions, lists of protected sites. Several departments and partner institutions feed it. It has to stay internally consistent, aligned with national and international authority files, and published in the formats downstream systems expect.

Most of it lives in spreadsheets, a legacy thesaurus tool, or a database one person knows how to work. Changes are hard to trace, contributions from outside are hard to accept safely, and publishing is an afterthought done by hand.

What NeoWiki commits to

Each concept, place, institution, or classification is a record with a Schema: which fields exist, which are required, which values are allowed, how it links to broader terms and to its counterparts in external authority files. Contributors work in forms derived from that Schema, your own staff and partner institutions alike, with validation at the point of entry and no syntax to learn. Read and edit permissions are set per record, so a partner maintains its own entries and nothing else.

Every change is attributed and versioned: who asserted a term, when, and what it replaced. Approval workflows apply where you want them. The result is a vocabulary you can stand behind, because the record shows how it came to be.

Publishing is built in. Every record has a stable, dereferenceable URI, exports as RDF, and projects into the vocabularies your partners consume, SKOS among them, and into several at once. Query the whole graph in SPARQL or Cypher: every term without a broader concept, every register entry that lapsed, everything aligned to a given external authority.

It runs where your rules require: on your own infrastructure, or on our managed hosting in the EU. It is open source, and standards-based exports mean the data is never captive.

Where NeoWiki is going

Multilingual values for labels and definitions are in progress. Bulk import from existing files and authority services is on the roadmap.

Want the full picture? See all of NeoWiki's capabilities.

Recognize your situation?

Let's talk through the specifics.