Intentional Arrangement SKOS
Build a real SKOS taxonomy in your browser. It validates as you type, exports to seven formats, and sticks to the standards a cataloguer would check it against. No account, no server — a static page you open and use.
Try it: https://jesstalisman-ia.github.io/intentional-arrangement-skos/
Or download the app/ folder (three static files, no build step) and open index.html from your desktop.
Informed building, not blind building. Augmentation, not automation.
Curious why it's built this way? → Why it works this way — the thinking behind running in the browser, the license, SKOS-XL, collections, and sharing.
📍 Roadmap · 💬 Discussions (questions & ideas) · 💡 Request a feature or report a bug
What's in the repo
| Folder | What it is |
|---|
app/ | The browser app — index.html (UI) + core.js (the shared standards engine) + vocab-data.js (bundled reference vocabularies). Static, no build step. |
| api/ | A small REST API (Flask + rdflib + pySHACL) to validate a vocabulary and convert between RDF serializations. |
| mcp-server/ | An MCP server exposing the same engine as tools, so an assistant like Claude can validate/convert/profile a vocabulary. |
| connectors/ | Bridges that pull external vocabularies into the editor as SKOS. First one: SharePoint Term Store → SKOS (Microsoft Graph or an offline export). Example/reference software — see its README's disclaimer before any live use. |
| deploy/ | Optional Apache Jena Fuseki server for the app's "Publish to server" feature — a Dockerfile that builds Fuseki 5.6.0 from the official distribution (base image pinned by digest, tarball by SHA-512). Not required; review deploy/README.md and harden before deploying. |
| docs/ | Documentation hub: install, using the editor, workspace, spreadsheet import, SKOS reference, hosting Fuseki, and the API/MCP guides. |
Where's Jena/Fuseki? Fuseki is a separate Java server; deploy/ builds it from the official Apache distribution (Jena 5.6.0, pinned by digest + checksum) for the optional "Publish to server" feature, with a hardening checklist. The app itself never needs it — it runs fully client-side.
What the app does
-
Editor. Concepts get URIs, one preferred label per language, alternate and hidden labels, an optional rdfs:label alternate name and rdfs:comment, and the run of SKOS notes: definition, scope, change, history, editorial, example. The hierarchy is real poly-hierarchy — a concept can sit under two parents. Adding a skos:related link is reciprocal, the way SKOS defines it (owl:SymmetricProperty) — it applies both ways and shows in the graph. Click a linked concept in any relationship picker to jump straight to it in the tree. Identifiers are readable slugs or opaque RFC 9562 UUIDv7 — time-ordered, canonical dashed lowercase (8-4-4-4-12), your call. Language tags are BCP 47: pick one from a code · Name dropdown or type any valid tag (nl-BE, zh-Hant), and the editor normalises letter case (NL-be → nl-BE) without changing the language. Retire a concept instead of deleting it: mark it owl:deprecated, point at its successor with dcterms:isReplacedBy, and it keeps its URI and its place in the scheme.
-
ISO 25964 thesaurus relations (opt-in). Turn on ISO 25964 mode to get the specialised hierarchy alongside plain skos:broader: iso-thes:broaderGeneric (is-a), broaderPartitive (part-of), and broaderInstantial (instance-of), with their narrower inverses. All three assert their skos:broader super-property — as the iso-thes ontology declares — so plain-SKOS tools always read the hierarchy.
-
Sources — documents & agents. A Sources tab for reusable foaf:Document records (dcterms:title, foaf:page, rdfs:comment) that concepts cite with dcterms:source, and prov:Agent records — prov:Person / prov:Organization / prov:SoftwareAgent with foaf:name/foaf:homepage — that you can credit as the scheme's creator, contributor, or publisher. Laid out like Build: a tree of Documents and Agents on the left, an editor on the right; renaming a record keeps its place in the export.
-
Crosswalk (thesaurus building). Align taxonomies from your workspace with the five SKOS mapping relations. Auto-match proposes links from identical/near labels; confirm or draw your own in a visual side-by-side view. Three exports, each in Turtle, RDF/XML, or JSON-LD: the crosswalk alone (mapping triples — this scope also exports , the mapping-interchange standard, with set metadata, auto-minted CURIEs and a justification per row), the federated thesaurus (the current pair + mappings), or — every taxonomy networked by mappings, in one file (available from the Crosswalk tab and from a dedicated card in the Export tab; step-by-step instructions in ). Mappings also ride along in normal exports.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
