Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a new README.md for FDO schema #83

Merged
merged 2 commits into from
Feb 19, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions data-model/fdo-profiles/0.1.0/README.md
Original file line number Diff line number Diff line change
@@ -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.

sharifX marked this conversation as resolved.
Show resolved Hide resolved

### 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.
Loading