The following is an AI chat conversation regarding the topic stated in the title.
Depending on the quality of the conversation, modifications may have been made. Modifications may or may not be stated in this page.
The type of https://schema.org/inventoryLevel is https://schema.org/QuantitativeValue It seems that this type does support a general number such as 9. Is this really true?
According to the document, schema.org/inventoryLevel is a type of QuantitativeValue, and QuantitativeValue is expected to be one of these types: whole number, decimal number, or fraction. There is no mention of supporting a general number such as 9, but it does support whole numbers.
I can’t find any reference to numbers being allowed for https://schema.org/QuantitativeValue Please elaborate.
You’re right, there isn’t a direct reference to numbers being allowed for schema.org/QuantitativeValue. The schema.org documentation uses terms like “whole number” and “decimal number” instead of just “number”.
Here’s a breakdown of what the documentation implies:
- QuantitativeValue represents a measurement.
- Measurements typically involve a value and a unit.
- The value can be a whole number (e.g., 10), a decimal number (e.g., 3.14), or a fraction.
While the schema doesn’t explicitly state “number” is allowed, it implies whole numbers are valid values because they represent a specific quantity.
Here are some resources from schema.org that support this:
- QuantitativeValue definition: https://schema.org/QuantitativeValue mentions the value being a number for QuantitativeValue and MonetaryAmount.
- unitText property: https://schema.org/unitText is used to specify the unit of measurement for a numerical value.
However, it’s important to note that some discussion exists about using QuantitativeValue for product dimensions:
- There are open issues on the schema.org Github regarding using QuantitativeValue for product dimensions with units (https://schema.org/QuantitativeValue)
In conclusion, while schema.org implies whole numbers are valid for QuantitativeValue, it’s best practice to consider the context and potential limitations. For product dimensions, there might be a more suitable approach being discussed within the schema.org community.
My issue is that the schema.org page for QuantitativeValue suggests that it is an object with properties, not a number. Where is it stated that normal numbers are allowed?
According to the document, schema.org defines QuantitativeValue as a number or text datatype though it can also be a StructuredValue. schema.org
This suggests that schema.org allows QuantitativeValue to represent a basic number but it can also be more complex data like a structured value.
I checked the page but can not find where it says that. Where does it state that a number can be used?
While the schema.org documentation for QuantitativeValue doesn’t explicitly say that numbers are allowed, it implies it by mentioning point values and various quantities.
For example, it talks about quantities like weight, height, and depth which can all be numerical values.
Also, a search on the web confirms that schema.org recommends using ‘Number’ type for the value property of QuantitativeValue.