Consider removing dataDependencies for v1

[pwalsh]

dataDependencies has an implicit dependency on packages available at data.okfn.org. It is also unclear how a package can depend on other package, which is the main rationale for having the property.

I think this is a potentially powerful feature, but, in the absence of an actual use case, and the ambiguity of the property and how it should be implemented, I suggest we remove it from v1.

We also should allow dependencies to live at any URI, and not only be identifiers for packages on data.okfn.org

[rufuspollock]

@pwalsh i agree. Let's remove this and reintroduce as a pattern for now.

[pwalsh]

We won't merge #337 until we can support all the changes in the core implementations we maintain. So closing this as it is implemented in #337 , as leaving it open creates confusion.

[smartcaveman]

If dataDependencies is deprecated, Is there a revised protocol for referencing dependent data packages?

[rufuspollock]

@smartcaveman i'd suggest still using dataDependencies - it just isn't an official part of the v1.0 spec - but it is a pattern and is up for inclusion in v1.1 assuming enough interest.

[rufuspollock]

Now in patterns: http://specs.frictionlessdata.io/patterns/#data-dependencies