브라우저에서 진짜 SKOS 분류체계를 구축하세요. 타이핑하는 동안 검증되고, 7가지 형식으로 내보내며, 목록 작성자가 검증할 표준을 준수합니다. 계정도 없고, 서버도 없으며, 정적인 페이지만 열어 사용할 수 있습니다.

한번 해보세요: https://jesstalisman-ia.github.io/intentional-arrangement-skos/ 또는 app/ 폴더(세 개의 정적 파일, 빌드 단계는 없음)를 다운로드하고 데스크톱에서 index.html를 열어보세요.

정보 제공 건물이지, 맹목적 건축이 아닙니다. 자동화가 아니라 증강.

왜 이렇게 만들어졌는지 궁금하신가요? → 왜 이렇게 작동하는지 — 브라우저에서 실행하는 방식, 라이선스, SKOS-XL, 컬렉션, 그리고 공유에 대한 생각 때문입니다.

📍 로드맵 · 💬 토론(질문 및 아이디어) · 💡 기능 요청 또는 버그 신고

---

압류 안에 뭐가 있을까

| api/ | 어휘를 검증하고 RDF 직렬화 간 변환을 위한 작은 REST API(Flask + rdflib + pySHACL)입니다. |

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

| 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