Thing > Intangible > StructuredValue > QuantitativeValue
A point value or interval for product characteristics and other purposes.
Usage: Between 1000 and 10,000 domains
[more...]
| Property | Expected Type | Description |
|---|---|---|
| Properties from QuantitativeValue | ||
additionalProperty
|
PropertyValue | A property-value pair representing an additional characteristics of the entitity, e.g. a product feature or another characteristic for which there is no matching property in schema.org. Note: Publishers should be aware that applications designed to use specific schema.org properties (e.g. http://schema.org/width, http://schema.org/color, http://schema.org/gtin13, ...) will typically expect such data to be provided using those properties, rather than using the generic property/value mechanism. |
maxValue
|
Number | The upper value of some characteristic or property. |
minValue
|
Number | The lower value of some characteristic or property. |
unitCode
|
URL or Text | The unit of measurement given using the UN/CEFACT Common Code (3 characters) or a URL. Other codes than the UN/CEFACT Common Code may be used with a prefix followed by a colon. |
unitText
|
Text | A string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for unitCode. |
value
|
Boolean or StructuredValue or Number or Text | The value of the quantitative value or property value node. For QuantitativeValue, the recommended type for values is 'Number'. For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'. |
valueReference
|
QualitativeValue or QuantitativeValue or Enumeration or StructuredValue or PropertyValue | A pointer to a secondary value that provides additional information on the original value, e.g. a reference temperature. |
| Properties from Thing | ||
additionalType
|
URL | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally. |
alternateName
|
Text | An alias for the item. |
description
|
Text | A short description of the item. |
image
|
URL or ImageObject | An image of the item. This can be a URL or a fully described ImageObject. |
mainEntityOfPage
|
CreativeWork or URL | Indicates a page (or other CreativeWork) for which this thing is the main entity being described.
Many (but not all) pages have a fairly clear primary topic, some entity or thing that the page describes. For example a restaurant's home page might be primarily about that Restaurant, or an event listing page might represent a single event. The mainEntity and mainEntityOfPage properties allow you to explicitly express the relationship between the page and the primary entity. Related properties include sameAs, about, and url. The sameAs and url properties are both similar to mainEntityOfPage. The url property should be reserved to refer to more official or authoritative web pages, such as the item’s official website. The sameAs property also relates a thing to a page that indirectly identifies it. Whereas sameAs emphasises well known pages, the mainEntityOfPage property serves more to clarify which of several entities is the main one for that page. mainEntityOfPage can be used for any page, including those not recognized as authoritative for that entity. For example, for a product, sameAs might refer to a page on the manufacturer’s official site with specs for the product, while mainEntityOfPage might be used on pages within various retailers’ sites giving details for the same product. about is similar to mainEntity, with two key differences. First, about can refer to multiple entities/topics, while mainEntity should be used for only the primary one. Second, some pages have a primary entity that itself describes some other entity. For example, one web page may display a news article about a particular person. Another page may display a product review for a particular product. In these cases, mainEntity for the pages should refer to the news article or review, respectively, while about would more properly refer to the person or product. Inverse property: mainEntity. |
name
|
Text | The name of the item. |
potentialAction
|
Action | Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role. |
sameAs
|
URL | URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Freebase page, or official website. |
url
|
URL | URL of the item. |
Instances of QuantitativeValue may appear as values for the following properties
| Property | On Types | Description |
|---|---|---|
advanceBookingRequirement
|
Demand or Offer | The amount of time that is required between accepting the offer and the actual usage of the resource or service. |
cargoVolume
|
Vehicle | The available volume for cargo or luggage. For automobiles, this is usually the trunk volume. Typical unit code(s): LTR for liters, FTQ for cubic foot/feet Note: You can use minValue and maxValue to indicate ranges. |
deliveryLeadTime
|
Demand or Offer | The typical delay between the receipt of the order and the goods leaving the warehouse. |
depth
|
VisualArtwork or Product | The depth of the item. |
durationOfWarranty
|
WarrantyPromise | The duration of the warranty promise. Common unitCode values are ANN for year, MON for months, or DAY for days. |
eligibleDuration
|
Demand or Offer | The duration for which the given offer is valid. |
eligibleQuantity
|
Demand or PriceSpecification or Offer | The interval and unit of measurement of ordering quantities for which the offer or price specification is valid. This allows e.g. specifying that a certain freight charge is valid only for a certain quantity. |
fuelConsumption
|
Vehicle | The amount of fuel consumed for traveling a particular distance or temporal duration with the given vehicle (e.g. liters per 100 km). Note 1: There are unfortunately no standard unit codes for liters per 100 km. Use unitText to indicate the unit of measurement, e.g. L/100 km. Note 2: There are two ways of indicating the fuel consumption, fuelConsumption (e.g. 8 liters per 100 km) and fuelEfficiency (e.g. 30 miles per gallon). They are reciprocal. Note 3: Often, the absolute value is useful only when related to driving speed ("at 80 km/h") or usage pattern ("city traffic"). You can use valueReference to link the value for the fuel consumption to another value. |
fuelEfficiency
|
Vehicle | The distance traveled per unit of fuel used; most commonly miles per gallon (mpg) or kilometers per liter (km/L). Note 1: There are unfortunately no standard unit codes for miles per gallon or kilometers per liter. Use unitText to indicate the unit of measurement, e.g. mpg or km/L. Note 2: There are two ways of indicating the fuel consumption, fuelConsumption (e.g. 8 liters per 100 km) and fuelEfficiency (e.g. 30 miles per gallon). They are reciprocal. Note 3: Often, the absolute value is useful only when related to driving speed ("at 80 km/h") or usage pattern ("city traffic"). You can use valueReference to link the value for the fuel economy to another value. |
height
|
VisualArtwork or MediaObject or Product or Person | The height of the item. |
inventoryLevel
|
Demand or Offer or SomeProducts | The current approximate inventory level for the item or items. |
mileageFromOdometer
|
Vehicle | The total distance travelled by the particular vehicle since its initial production, as read from its odometer. Typical unit code(s): KMT for kilometers, SMI for statute miles |
numAdults
|
LodgingReservation | The number of adults staying in the unit. |
numChildren
|
LodgingReservation | The number of children staying in the unit. |
numberOfAxles
|
Vehicle | The number of axles. Typical unit code(s): C62 |
numberOfDoors
|
Vehicle | The number of doors. Typical unit code(s): C62 |
numberOfEmployees
|
Organization or BusinessAudience | The number of employees in an organization e.g. business. |
numberOfForwardGears
|
Vehicle | The total number of forward gears available for the transmission system of the vehicle. Typical unit code(s): C62 |
numberOfPlayers
|
VideoGameSeries or Game | Indicate how many people can play this game (minimum, maximum, or range). |
numberOfPreviousOwners
|
Vehicle | The number of owners of the vehicle, including the current one. Typical unit code(s): C62 |
partySize
|
TaxiReservation or FoodEstablishmentReservation | Number of people the reservation should accommodate. |
valueReference
|
QualitativeValue or PropertyValue or QuantitativeValue | A pointer to a secondary value that provides additional information on the original value, e.g. a reference temperature. |
vehicleSeatingCapacity
|
Vehicle | The number of passengers that can be seated in the vehicle, both in terms of the physical space available, and in terms of limitations set by law. Typical unit code(s): C62 for persons |
weight
|
Product or Person | The weight of the product or person. |
width
|
VisualArtwork or MediaObject or Product | The width of the item. |
yearlyRevenue
|
BusinessAudience | The size of the business in annual revenue. |
yearsInOperation
|
BusinessAudience | The age of the business. |
Acknowledgements
This class is derived from the GoodRelations Vocabulary for E-Commerce, created by Martin Hepp. GoodRelations is a data model for sharing e-commerce data on the Web that can be expressed in a variety of syntaxes, including RDFa and HTML5 Microdata. More information about GoodRelations can be found at http://purl.org/goodrelations/.Schema Version 2.0

