ENG-1584 Add draft status to ontology files

[maparent]

https://linear.app/discourse-graphs/issue/ENG-1584/add-draft-status-to-ontology-files

---

[linear]

ENG-1584 Add draft status to ontology files

[supabase]

This pull request has been ignored for the connected project zytfjzqyijgagqxrzbmz because there are no changes detected in packages/database/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 4 additional findings in Devin Review.

[devin-ai-integration]

🟡 dc:modified is not a valid Dublin Core Elements 1.1 property

The dc: prefix is bound to http://purl.org/dc/elements/1.1/ (line 4), which defines exactly 15 properties — modified is not one of them. Using dc:modified creates a triple with the IRI http://purl.org/dc/elements/1.1/modified, which is undefined in any standard vocabulary. Standard-aware RDF/OWL tools looking for modification dates expect dcterms:modified from http://purl.org/dc/terms/. This means the modification date won't be discoverable by any tool following standard vocabulary conventions.

Note: the same incorrect pattern pre-exists in apps/roam/src/utils/jsonld.ts:23, but this PR extends it to a published Turtle schema file.

Prompt for agents

In apps/website/public/schema/dg_core.ttl, add a new prefix declaration for Dublin Core Terms:
  @prefix dcterms: <http://purl.org/dc/terms/> .

Then on line 16, change:
  dc:modified "2026-03-26" ;
to:
  dcterms:modified "2026-03-26" ;

Also consider fixing the same issue in apps/roam/src/utils/jsonld.ts line 23 where `modified` is mapped to `dc:modified`. It should either add a `dcterms` prefix mapping to `http://purl.org/dc/terms/` and map `modified` to `dcterms:modified`, or keep the current behavior if intentional for internal consistency.

---

Was this helpful? React with 👍 or 👎 to provide feedback.