Should maximum/minimum have the same fmt/pattern?

I suppose it’s correct:

type: date
format: fmt:%Y
constraints:
  minimum: 2015

And it’s not correct:

type: date
format: fmt:%Y
constraints:
  minimum: 2015-12-12 # bad format

Should be clarified in spec (which one is correct).

For implementations the same format for both is much more preferable way (because minimum/maximum could be cast using the same approach as value). And for now python version acts based on snippet #1 workflow.

[pwalsh]

@roll could you please help me out here, and go through the list of constraints, and not here what is before/after (just to ensure I don’t miss any concerns from implementation perspective). I will then update specs accordingly.

[pwalsh]

@rgrp @roll @akariv @frictionlessdata/specs-working-group

I think we should be explicit about constraints applying to the value before parsing. Implementing code could handle the cases where it is dealing with an already cast value or not.

So, constraints like enum should be arrays of strings, each parsable as the type/format of the field.