Field datatype not locked down by JSON Schema

[martinjoconnor]

We do not lock down the datatypes of fields in the JSON Schema @type specification for fields.

For example, here is the specification for the @value and @type fields for date field instances:

      "properties": {
        "@value": { "type": [ "string", "null" ] },
        "rdfs:label": { "type": [ "string", "null" ] },
        "@type": { "type": "string", "format": "uri" }
      },
      "required": [ "@value", "@type" ],

The @type field is restricted to a URI only when it should be restricted to xsd:date.

[johardi]

We don't lock down the @type value to a specific data type (i.e., using enum) to give users the freedom to set their own data type

[martinjoconnor]

But that should be locked down by the template. A date field instance, for example, should only have the type xsd:date. The only place a user has freedom to set the value for the @type is for templates and element.

[martinjoconnor]

I will agree that this may be tricky to do in practice because we would need a different specification for each type of field. Which is why I didn't put it in the 2.3 milestone. We can discuss to see if the extra effort is worth it.