We're getting started in 10 minutes with @b_fiive presenting @qri_io's decentralized open data platform https://talk.fission.codes/t/qri-an-open-source-version-control-and-sharing-system-for-datasets-built-on-ipfs-with-brendan-obrien/626
Grab the Zoom link from our chat https://fission.codes/discord
Grab the Zoom link from our chat https://fission.codes/discord
The @qri_io project thinks of itself not just as heavy @IPFSbot, bu also libP2P.
They are dedicated to building a data commons.
They are dedicated to building a data commons.
" @qri_io accepts messy data, but not _invalid_ data". Usually CSV ingest, which "upgrades" to SQL queryable.
Schema inference, column names
Dataset document format is common - metadata, README, commit info
Schema inference, column names
Dataset document format is common - metadata, README, commit info
Git recommends files no larger than 100MB. @qri_io works on datasets that are much larger, IPFS is a good fit for versioning / content addressing, and block-level storage and sharing.
Biggest difference between data sets and code in version control, is that data sets get much much bigger -- GBs in size.
@qri_io came up with logbook -- append only log, informed by operational transforms / CRDTs. Kind of like git reflog, but tuned for datasets
@qri_io came up with logbook -- append only log, informed by operational transforms / CRDTs. Kind of like git reflog, but tuned for datasets
Built in structured data diff'ing support, including in @qri_io desktop
Wrapping up now with some discussion. Excited to see where @FISSIONcodes and @qri_io can work together on shared open source specs and code.
See sprint boards: https://github.com/orgs/qri-io/projects/31
And RFCs: https://github.com/qri-io/rfcs
See sprint boards: https://github.com/orgs/qri-io/projects/31
And RFCs: https://github.com/qri-io/rfcs
Because we're already getting pings on this, yes the main presentation was recorded, and we'll post it later today with a link in this thread.
Thanks @ricogardaphe and @b_fiive for joining us today!
Thanks @ricogardaphe and @b_fiive for joining us today!