From 013c4f993cd86a5e7266ca203399c59c3e07d701 Mon Sep 17 00:00:00 2001
From: Michael Hanke <michael.hanke@gmail.com>
Date: Sun, 24 Dec 2023 22:03:39 +0100
Subject: [PATCH] Expand the key setup for a Commit

---
 src/linkml/git-provenance-schema.yaml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/src/linkml/git-provenance-schema.yaml b/src/linkml/git-provenance-schema.yaml
index dfd02fc..625abbe 100644
--- a/src/linkml/git-provenance-schema.yaml
+++ b/src/linkml/git-provenance-schema.yaml
@@ -44,6 +44,24 @@ classes:
       gitsha:
         description: >-
           SHA1 identifier of the commit object.
+      meta_id:
+        pattern: "^gitsha:[0-9a-f]{40}$"
+        description: >-
+          SHA1 identifier written as a CURIE in an explicit
+          `gitsha:` namespace.
+
+    unique_keys:
+      gitsha:
+        description: >-
+          A commit's GITSHA is a globally unique, content-based identifier
+          of that commit.
+        notes:
+          - The `gitsha` slot could have been labled to be the one identifier
+            of a Commit-type object. However, we use `meta_type` for
+            consistency and use its CURIE-format to assign an explicit
+            namespace.
+        unique_key_slots:
+          - gitsha
 
   CommitProvenance:
     mixin: true