Skip to content
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

What's different from datapackage-read-js + datapackage-init-js? #15

Open
rufuspollock opened this issue Apr 30, 2016 · 2 comments
Open

Comments

@rufuspollock
Copy link

@pwalsh could you clarify what's in here vs

https://github.com/okfn/datapackage-read-js

https://github.com/okfn/datapackage-init-js

I have a sense that this and especially https://github.com/okfn/datapackage-read-js could / should be one thing ...

@rufuspollock rufuspollock changed the title What's the different from datapackage-read-js + datapackage-init-js? What's different from datapackage-read-js + datapackage-init-js? Apr 30, 2016
@pwalsh
Copy link
Contributor

pwalsh commented Apr 30, 2016

This is almost unrelated to those two libs: It maps a remote resource into a DP. It was written for DataPackagist to read a CKAN/DKAN resource and automap to a DP: https://github.com/frictionlessdata/datapackagist#integrations

@rufuspollock
Copy link
Author

@pwalsh ah ok - i note that datapackage-read-js loads datapackages fro remote so there could be some overlap / integration here. It seems to be to the extent that a "read" or "load-remote" should exist standalone it would be worth maybe loading other stuff and normalizing. Anyway, thanks for clarification and food for thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants