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

First attempt at a data provisioning specification #175

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mih
Copy link
Contributor

@mih mih commented May 6, 2024

The idea here is to use a "dataset description", unmodified, also as a "download specification". The difference is that rather being an exhaustive description, only the minimal information necessary is included to:

  • drive a generic data provisioning tool
  • precisely identify which data subsets are needed

The included specification asks to provision:

  • a Git worktree matching a particular commit
  • a particular Git blob from the same repository, presented as a README.md file in the worktree.

Closes #174

The idea here is to use a "dataset description", unmodified, also as a
"download specification". The difference is that rather being an
exhaustive description, only the minimal information necessary is
included to:

- drive a generic data provisioning tool
- precisely identify which data subsets are needed

The included specification asks to provision:

- a Git worktree matching a particular commit
- a particular Git blob from the same repository, presented as a
  `README.md` file in the worktree.
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.

Example of a data provisioning specification
1 participant