-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First draft for compressed data packages #198
Conversation
@sabas apologies for slowness on merging - i have been looking at this and just been mulling some points over. @danfowler - i'd also invite you to do a quick review here :-) |
@mfenner would you like to review this? |
It's just a draft for discussion :-) The problem of discovering the metadata is interesting, something like the jar manifest? https://en.wikipedia.org/wiki/JAR_(file_format)#Manifest |
@sabas wouldn't the |
Yes @pwalsh I linked it as a reference for a possible implementation. The datapackage manifest would be the datapackage.json |
In the spirit of keeping things simple I wouldn't provide two options ( |
Pebble watch files are another example: http://www.pebbledev.org/wiki/Applications/ |
I'll second @mfenner 's suggestion to exhaust all possible existing alternatives before defining a new format. If you are forced to define something new, I'd strongly consider using zip instead of tar, since every other container format in the world from JAR to EPUB to Research Object Bundle has settled on it. There's an old overview of a bunch of the zip-based formats here: http://broadcast.oreilly.com/2009/01/packaging-formats-of-famous-ap.html |
OK, it sounds like we do want to go with zip. I'm going to close this PR for the time being and suggest we move discussion back to the main issue at #132 |
This spec states only how to archive or compress and which extension to use.
See #132