Consider support for JSON References

[Hypercubed]

As discussed in #293 we should consider adding a $schema tag to the JSON Table Schema spec to distinguish between JSON Schema and JSON Table Schemas. Subsequently, I suggest that the Data Package spec support specifying JSON Schemas for arbitrary data. To do this I believe the Data Package spec should include support for JSON References.

[pwalsh]

I think JSON Reference support is useful.

I think we should consider this for a post v1 feature of the specs.

[rufuspollock]

Generally a +1 though may be post v1 as @pwalsh suggests.

[rufuspollock]

@Hypercubed could you give a bit more detail on how you anticipate this working in the spec and being interpreted by tools.

[Hypercubed]

I think the point is that if Data Package spec is to support JSON Schemas (in addition to JSON Table Schemas) then JSON Pointer support is needed. From draft-wright-json-schema-00:

Any time a subschema is expected, a schema may instead use an object containing a "$ref" property. The value of the $ref is a URI Reference. Resolved against the current URI base, it identifies the URI of a schema to use. All other properties in a "$ref" object MUST be ignored.

[rufuspollock]

@Hypercubed so you imagine in a resource object something like this:

"schema": {
  "$ref": URI reference ...
}

[pwalsh]

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