Add a $schema key, or similar, to Table Schema so it is machine identifiable

[Hypercubed]

This will help distinguish JSON Table Schemas from other types of JSON schema files.

See The "$schema" keyword

[rufuspollock]

@Hypercubed good point. In the basic case how does one tell whether the schema value is a JTS or a simple JSON schema.

As discussed on chat one option is to look to the profile. However, that might not help where you have resources of different kinds in the same package.

We've thought for a while that the profile registry might include a registry both of DP profiles and Schema profiles (including profiles of JTS ...).

My concern is growing complexity here. In terms of an immediate way forward why don't you try out using the $schema tag and report back on how you do it and how it goes?

[pwalsh]

I see the use case. I'm not sure this is an issue for the specs themselves, but rather one for implementing code.

I think the utility of this in JSON Schema is for disambiguation between different versions of the spec.

If we realise we need this for JSON Table Schema after a v1, then surely we should look at the same implementation.

[rufuspollock]

@pwalsh this is not disambiguating different versions of same spec so much as different uses of schema attribute: e.g. for JTS or for simple JSON Schema (when describing JSON data).

[roll]

DONE as a part of Data Package (v2) versioning