BioCompute Object: Difference between revisions

Content deleted Content added
Kee007ney (talk | contribs)
Kee007ney (talk | contribs)
Line 35:
 
== Format ==
The BioCompute Object is in [[JSON|json]] format and, at a minimum, contains all the software versions and parameters necessary to evaluate or verify a computational pipeline. It may also contain input data as files or links, reference genomes, or executable Docker components. A BioCompute Object can be integrated with [[FHIR|HL7 FHIR]] as a Provenance Resource.<ref>{{Cite web|url=https://www.hl7.org/fhir/provenance-example-biocompute-object.html|title=Provenance-example-biocompute-object|website=HL7 FHIR Release 3 (STU)}}</ref>. TheMultiple effortjoint isimplementations seenare byalso many{{who}}under todevelopment bethat redundantleverage andBCO's unnecessaryreport-centric asformat, theincluding bioinformaticsCWL community(one hasof alreadywhich embraced{{Citationis needed}}part theof [[Commonan Workflowactive Language]]government whichfunded containspublic allcontract ofwith these,a andcofounder superiorof capabilities,CWL despiteto thepilot BCOand objective{{Citationgenerate needed}}documentation tofor treata thejoint BCO-CWL, as awell [[Researchas Object]].examples) and RO<ref>{{Citation|last=Soiland-Reyes|first=Stian|title=hive-cwl-examples: ExamplePackaging BioCompute asObjects Researchusing Object with CWLRO-Crate|date=20162020-1209-1901|url=https://biocompute-objects.github.comio/stain/hivebco-cwlro-examples|accessdate=2017-12-21crate/}}</ref>.
 
== BCO Consortium ==