name	community-ontology-contribution
description	Add a contributor ontology to catalogue/community/. Use when a community member submits an RDF/OWL file and wants it listed in the Playground catalogue under their GitHub username.

Community Ontology Contribution Skill

Goal

Place a contributor's ontology under the correct catalogue path and produce a valid, compilable community entry.

CRITICAL: Directory Structure

The catalogue compiler scans exactly three levels deep:

catalogue/community/<github-username>/<slug>/

Both the <github-username> folder and the <slug> subfolder are required. Files placed directly in catalogue/community/<github-username>/ will be silently skipped by the compiler and the ontology will never appear in the catalogue.

✅ Correct

catalogue/community/jane-doe/supply-chain/
├── metadata.json
└── ontology.rdf        ← or ontology.owl

❌ Wrong — silently skipped

catalogue/community/jane-doe/
├── metadata.json       ← wrong depth
└── ontology.rdf        ← wrong depth

Step-by-Step Workflow

1. Determine the username and slug

<github-username> — the contributor's GitHub username (lowercased, as-is)
<slug> — short kebab-case name for this ontology (e.g. supply-chain, hr-system)

2. Create the directory

mkdir -p catalogue/community/<github-username>/<slug>/

3. Place the RDF/OWL file

Copy the file in and rename it ontology.rdf (or ontology.owl):

cp <source-file> catalogue/community/<github-username>/<slug>/ontology.rdf

4. Create `metadata.json`

Required fields (name, description, category) — missing any one causes a compile error:

{
  "name": "Human-Readable Ontology Name",
  "description": "One-sentence description of the domain.",
  "category": "general",
  "icon": "🏭",
  "tags": ["tag1", "tag2"],
  "author": "<github-username>"
}

No extra fields are allowed (additionalProperties: false in the schema). The fabric_forum_user_name and author_linkedin fields are not in the schema — omit them unless the schema is updated first.

5. Validate

npx tsx scripts/compile-catalogue.ts

Look for:

✔ community/<slug>

If you see a compile error or the entry is absent, re-check:

Directory depth (username folder + slug subfolder both present?)
All three required fields in metadata.json (name, description, category)
Valid category value
No extra fields in metadata.json

6. Full build check

npm run build

Common Mistakes (from real PRs)

Mistake	Effect	Fix
Files at `community/<username>/` with no slug subfolder	Silently skipped — entry never appears	Add `<slug>/` subfolder
Missing `name` field in `metadata.json`	Compile error	Add `"name": "..."`
Invalid `category` value	Compile error	Use one of the allowed values
Extra fields (`fabric_forum_user_name`, etc.)	Compile error (`additionalProperties`)	Remove the extra fields
Ontology file named something other than `ontology.rdf/.owl`	Not picked up	Rename to `ontology.rdf`

Done Criteria

npx tsx scripts/compile-catalogue.ts outputs ✔ community/<slug>
npm run build passes with no TypeScript or Vite errors
Entry appears in public/catalogue.json with correct name, description, category
source field in compiled entry is "community"

name	community-ontology-contribution
description	Add a contributor ontology to catalogue/community/. Use when a community member submits an RDF/OWL file and wants it listed in the Playground catalogue under their GitHub username.