Type of minimum/maximum constraint should be the same of the field

According to the spec, the type of the minimum/maximum constraint should be the same as the constrained field. The examples given in the official table-schema respect this principle. Here is the example given in the official schema for an integer:

   {
         "name": "age", 
         "type": "integer",
         "constraints": {
             "unique": true, 
             "minimum": 100, 
             "maximum": 9999
         }
    }

However, the spec for the minimum and maximum constraint expect their type to be string all the time. For example the spec for the minimum constraint of an integer:

{
    "minimum": {
        "type": "string",
        "description": "A minimum value for the property, context specific for the property type, and conforming with the format for the property.",
        "context": "This is different to `minLength`, which checks the number of items in the value. A `minimum` value constraint checks whether a field value is greater than or equal to the specified value."
    }
}

Shouldn’t ☝️ be "type": "integer"?

Same is true for other field types with minimum and maximum constraints.

[roll]

@georgiana-b It just has been added to the specs:

All constraints MUST be tested against the logical representation of data, and the physical representation of constraint values MAY be primitive types as possible in JSON, or represented as strings that are castable with the type and format rules of the field.

And on implementation level you just treat field’s data value and constraint value the same - https://github.com/frictionlessdata/tableschema-py/blob/master/tableschema/field.py#L153-L167

For example you have field:

name: name
type: integer
constraints:
  maximum: 20 or '20'

with data

50
'40'
30

So you first just cast constraint to field type (‘20’ -> 20) and then compare to values also cast to data type (‘40’ -> 40).

[roll]

@pwalsh Both will work for implementations for now. But if you’re in the mood for second option (i.e. have time=) it will be better. Though enum is also not typed.