biocompute-objects / biocompute-objects/BCO_Documentation

How are BCOs packaged or transferred?

Open
#24 4 comments 1 reaction 3 assignees Claimed by @skeeney01 View on GitHub
discuss Documetation LifeSpan 1 LifeSpan 2
Dominant language
HTML
Stars
17
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Relates a bit to #23 - how are BCOs serialized and transferred?

Is there a conventional file name for the BCO JSON? (`bco.json` springs to mind)

Is there a conventional path structure to contain a BCO and its sub-resources"? (e.g. `data/` ? )

Are BCO sub-resources (scripts, inputs, outputs) webby or contained in some kind of package? (alternative: snapshots of the webby resources)

It has been briefly mentioned that BCOs are meant to be submitted to FDA in the form of physical hard-drives. What form does this take? (We can rule it out of scope for this spec)

Should BCO packaging reuse existing standards like [bagit](https://tools.ietf.org/html/draft-kunze-bagit-17) or [Research Object](http://www.researchobject.org/)?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.