From 176b02146cb96bcc2c70bef385a6f23c05bdf45d Mon Sep 17 00:00:00 2001
From: Sharif Islam <50382675+sharifX@users.noreply.github.com>
Date: Fri, 9 Feb 2024 13:33:46 +0100
Subject: [PATCH] Create README for FDO Profiles

---
 data-model/fdo-profiles/0.1.0/README.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 data-model/fdo-profiles/0.1.0/README.md

diff --git a/data-model/fdo-profiles/0.1.0/README.md b/data-model/fdo-profiles/0.1.0/README.md
new file mode 100644
index 0000000..805d411
--- /dev/null
+++ b/data-model/fdo-profiles/0.1.0/README.md
@@ -0,0 +1,14 @@
+## FDO Profile schemas
+
+This folder contains a collection of FAIR Digital Object Profiles (FDO Profiles) specific to DiSSCo data model elements. 
+Each folder represents a distinct profile for various digital objects like annotations, digital specimens, media objects, organisations. We also have profiles for DOI and Handle kernel, for mapping, machine annation service 
+(mas), and digital object tomstone pages. These profiles are crucial for implementing FAIR principles and ensuring machine-actionability.
+
+
+### Why separate FDO Profiles?
+
+While some common metadata exists across profiles, distinct FDOs offer several advantages:
+
+- Granularity: Tailored profiles cater to specific data object types, ensuring the most relevant metadata is captured.
+- Extensibility: Profiles can be extended or inherit from others, promoting reusability and avoiding redundancy.
+- Governance: Separate profiles facilitate the governance and maintenance of digital object types.