How are BCOs packaged or transferred? #24
Labels
discuss
Discussion/opinions requested
Documetation
Relating to documentation, not code or functionality
LifeSpan 1
This issue has been passed from one milestone to the next
LifeSpan 2
Milestone
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 or Research Object?
The text was updated successfully, but these errors were encountered: