Use registry in datapackage-validate

[pwalsh]

Currently is hardcoded for the default Data Package schema.

Need to:

• Allow passing in any (valid) data package schema
• Support datapackage-registry directly?

[gvidon]

@pwalsh currently datapackage-validate takes just data package json as a param and validate it over limited set of predefined schemas. Perhaps would be good to have second param for validation — schema . This way datapackage-validate will never deal with a schema but get everything from params. Not sure if it brake any design concepts.

[pwalsh]

Yes, I think we will do something like that. The benefit of us publishing datapackage-registry on NPM, and then using that to get a schema on datapackage-validate, is that we ensure our "official" packages are always available to the validator. But I do think we should also change datapackage-validate to accept any schema that gets passed to it from the calling code.

In any event, we'll get back to this a bit later - perhaps in the next milestone.

[pwalsh]

This is is replaced by #27 and openknowledge-archive/datapackage-validate-js#6