This requires a discussion @apdavison @bweyers @olinux : How do we deal with file compression formats?
Write now we either ignore them (e.g. for nifit, where we just include the typical compression in the extension list), or we register them as separate content types (e.g. zip.jsonld, or vnd.espina.seg+zip.jsonld.
I'm not sure if we could deal with compressed formats a bit more elegantly than just registering them for any possible type.
For example: would it make sense to separate this from format within the file schema? Or include typical compression for file formats in the content type?
format: text/plain
compression: application/gzip
NOTE: the txt.gz is a missing format at the moment that I need to register soonish. Please let me know your thoughts as soon as you can.
This requires a discussion @apdavison @bweyers @olinux : How do we deal with file compression formats?
Write now we either ignore them (e.g. for nifit, where we just include the typical compression in the extension list), or we register them as separate content types (e.g. zip.jsonld, or vnd.espina.seg+zip.jsonld.
I'm not sure if we could deal with compressed formats a bit more elegantly than just registering them for any possible type.
For example: would it make sense to separate this from format within the file schema? Or include typical compression for file formats in the content type? format: text/plain compression: application/gzip
NOTE: the txt.gz is a missing format at the moment that I need to register soonish. Please let me know your thoughts as soon as you can.