install (download/import) command #3
Comments
@sballesteros merged notes from chat other day here |
update here: |
@sballesteros is install from url working? I'd love to use that! |
@rgrp I am still trying to figure out how to do
Maybe we should force that (listing all the files) in the spec. There is the files property of package.json (for npm) but it allows directories. Of course all of this is trivial if we only support github URLs but I would like a more generic solution here. EDIT: to be clear, here I am talking about files not listed in |
IMO the default should be to clone entire paths/repos/folder unless there is a specific manifest defined |
so if you have a really bare
and it is served from e.g. it doesn't define any resources, and also has no json-ld context, how about we look for these default files, in order, until we find one: archives:
(more common/sensible defaults welcome) if the |
@sballesteros I think we're putting too much obligations on dpm. We could be assuming that whomever publishes takes care of pushing scripts or they use e.g. git (so you git clone then get data urls if they aren't in the git repo). I think we want to do the simplest thing we can at the start that gets us working and if we miss out scripts we live with it (note: couldn't we reuse the scripts tag from commonjs for some of this?) |
@rgrp I agree. Currently refactoring a lot of stuff. |
@maxogden I wonder if allowing for default behaviour like this is making a rod for our backs down the line. Why not oblige data package creators to list resources if they exist ... (its not that hard to add one entry ...) |
@rgrp what negatives do you see? one is that if publishers arent required to provide a file manifest that they could publish a package that accidentally doesn't include any data. This is easy to fix though -- we have a pre-publish step that throws if no default data file can be found. |
@maxogden the downsides I see (in addition to the one you mention) are:
That said I do see plus here of making it even easier and faster to publish - a major concern at this early stage :-) So I'm probably a -0.5 at this point but do see the benefits ... |
"install" (download/import) a data package onto disk (note integration in other apps is outside of scope here).
Motivating user story: I'm building an app, doing some analysis etc and I want to get a bunch of data from data packages into my project
Questions
datapackages/{datapackage-name}/...
The text was updated successfully, but these errors were encountered: