Questions about QuantitativeValue
From Martin Hepp:
1. For quantitative values, it is straightforward to model open intervals for any datatype:
https://schema.org/QuantitativeValue
Simply use ONLY minValue or maxValue and you are all set.
It works perfectly for seconds (unit code "SEC"), hours ("HUR"), days ("DAY"). So you can use this to express that something takes at least a day or less than 30 minutes.
Ranges will of course also work ("20 - 45 minutes"). The potential of https://schema.org/QuantitativeValue is vastly underutilized.
Historically, we excluded absolute time and date values from the range of value, minValue, and maxValue, because respective time intervals with dates and time-zones can be complicated.
- Demand
- JobPosting
- LocationFeatureSpecification
- MonetaryAmount
- Offer
- OpeningHoursSpecification
- PriceSpecification
can be open using the very same pattern, either use
OR
https://schema.org/validThrough
Maybe these patterns can be reused for additional purposes.
BTW: "value" is designed to be a subproperty of "minValue" and "maxValue". So an RDFS-style reasoner would automatically translate a point value into an interval with matching lower and upper boundary.