Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

This section describes the RO-Crate profiles used in EMO-BON.

old text, relocated from data-products/crates/md

RO-Crate Profiles

EMO-BON defines specific profiles that describe the expected structure and content of different crate types:

Profiles are themselves RO-Crates that formally describe the layout/structure of crates that declare conformance to them.

What are RO-Profiles?

An RO-Profile is itself an RO-Crate that formally describes the layout and structure of other RO-Crates that declare conformance to it. Profiles ensure consistency and interoperability across EMO-BON data products.

EMO-BON Profiles

Observatory Profile

Repository: https://github.com/emo-bon/observatory-profile

URI: https://data.emobon.embrc.eu/observatory-profile/latest/

Purpose: Defines the structure and required metadata for observatory crates.

Key Components:

Conforming Crates: All observatory-{obsid}-crate repositories conform to this profile.

Analysis Results Profile

Status: In development

Purpose: Will define the structure for analysis results crates.

Planned Components:

Conforming Crates: analysis-results-{cluster}-crate repositories will conform to this profile.

Sequencing Profile

Status: Planned

Purpose: Will define the structure for sequencing metadata.

Planned Components:

Conforming Crates: The sequencing-logistics-crate repository will conform to this profile.

Profile Structure

Each profile contains:

  1. Profile Metadata: Information about the profile itself (version, description, etc.)

  2. Schema Definitions: Formal specifications of required and optional fields

  3. Semantic Templates: Templates for generating RDF triples from data

  4. Validation Rules: SHACL shapes or other validation specifications

  5. Documentation: Human-readable descriptions and examples

Using Profiles

Profiles are used in the EMO-BON workflow to:

Profile Versioning

Profiles follow semantic versioning (vM.m.p):

The latest version always points to the most recent stable release.