Repository navigation
IIIF numbers and JSON numbers #148
Description
Links
- Original Issue: Floating point numbers in the Presentation API api#2492
- Pull Request: Avoid 'floating point or integer' distinction for JSON number values api#2495
- Preview: https://preview.iiif.io/api/floating-point-numbers/presentation/4.0/model/
Background and Summary
Recipes suggested that numbers that could take a non-integer number should explicitly state the number with .0 at the end even when a whole number (e.g., number of seconds in a duration property). This led to a more general issue about numbers across the specification.
Proposed Solution
Generally, use "number" rather than "floating point number", and specify in Terminology section that "Where a value is required to be an integer, this is stated explicitly, and the value MUST be a number without a fractional part."
Reacted by Simeon Warner, TuulaP, Trey Pendragon, Pierre, Trip Kirkpatrick, Mark Baggett, Dan Brennan, Ruven, Glen Robson, marii¨ and 8 more
Activity
glenrobson commentedon Nov 12, 2026
Issue 148 (IIIF numbers and JSON numbers)
+1: 18 [LlGC-iir TuulaP akrishnan15 danieltbrennan glenrobson jcoyne jkunze markpbaggett marlo-longley mnyrop nfreire peteredwards pierrz ruven tpendragon triplingual tristanr-cogapp zimeon]
0: 0 []
-1: 0 []
Not TRC: 0 []
Ineligible: 0 []
Result: 18 / 18 = 1.00
Super majority is in favor, issue is approved
glenrobson commentedon Nov 12, 2026
Issue 148 (IIIF numbers and JSON numbers)
+1: 18 [LlGC-iir TuulaP akrishnan15 danieltbrennan glenrobson jcoyne jkunze markpbaggett marlo-longley mnyrop nfreire peteredwards pierrz ruven tpendragon triplingual tristanr-cogapp zimeon]
0: 0 []
-1: 0 []
Not TRC: 0 []
Ineligible: 0 []
Result: 18 / 18 = 1.00
Super majority is in favor, issue is approved