Allow CSV resource schema to be string

It seems that the base spec allows a resource’s schema to be an object or a string, but the jsontable and tabular data spec insists that it be an object.

Would it be reasonable to allow this to be a string? It would help keep the individual resource objects small when there are many separate resources (ie different years) with the same columns.

http://data.okfn.org/tools/validate?url=https%3A%2F%2Fraw.githubusercontent.com%2Fpeel-datasets%2Fland-tenure%2Fmaster%2Fdatapackage.json

[pwalsh]

@danfowler yes, thanks.

@rgrp I think we should remove, at least for V1, the various options for setting a schema. It is too flexible. I’d prefer something simple and explicit: schema property on a resource can be an object (the schema) or a url (to a schema object as json).

[rufuspollock]

FIXED.

To summarize the issue here as it got a bit confused: TDP was not clear that schema follows Data Package spec in allowing the value of schema property to be specified both inline and out of line. This has now been corrected. (Tabular Data Package was clear that schema value had to be a JSON Table Schema.)

Note: #295 etc is something different and can be considered quite separately.