Closed killerbgt closed 7 years ago
From a schema validation standpoint, strings in my experience provide the forward-compatible functionality when you outgrow integers.
I used to manage an API where we eventually moved from integer-based ids to GUIDS, and the backed in schema acceptance (instead of just client checking) made that a pain.
My 2 cents. In general, I'm a :+1: to the schema/high level details being pretty open, and then let individual implementations or versions add additional restrictions/validations.
I agree that this may be an area where we could be less prescriptive
Allow ids to be either strings or integers