Skip to content

Clarify child Dataset relationships - #155

Merged
NicolasCARPi merged 1 commit into
TheELNConsortium:masterfrom
CAOShurong:codex/clarify-child-datasets
Aug 12, 2026
Merged

Clarify child Dataset relationships#155
NicolasCARPi merged 1 commit into
TheELNConsortium:masterfrom
CAOShurong:codex/clarify-child-datasets

Conversation

@CAOShurong

Copy link
Copy Markdown
Contributor

What changed

  • replace the contradictory prohibition on child Dataset references with the relationship described in issue Property to link parent with child experiments #116
  • distinguish a parent/child relationship from the root ./ import list
  • add a minimal JSON-LD example showing a parent and child that are both selected for import

Why

The current specification first says that child datasets can be referenced and must also appear in the root import list, then says that datasets must not contain other datasets in hasPart. This makes the intended parent/child representation impossible to follow. The new wording keeps both roles explicit: nested hasPart records the relationship, while direct root membership marks a dataset for import.

Closes #116.

Validation

  • git diff --check
  • python -m pytest — 6 passed

@NicolasCARPi NicolasCARPi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

@NicolasCARPi
NicolasCARPi merged commit 19028dd into TheELNConsortium:master Aug 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Property to link parent with child experiments

2 participants