A structured value representing the duration and scope of services that will be provided to a customer free of charge in case of a defect or malfunction of a product.
Usage: Between 100 and 1000 domains
|Properties from WarrantyPromise|
||QuantitativeValue||The duration of the warranty promise. Common unitCode values are ANN for year, MON for months, or DAY for days.|
||WarrantyScope||The scope of the warranty promise.|
|Properties from Thing|
||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.|
||Text||An alias for the item.|
||Text||A short description of the item.|
URL or |
|An image of the item. This can be a URL or a fully described ImageObject.|
CreativeWork or |
|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.
||Text||The name of the item.|
||Action||Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.|
||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 of the item.|
Instances of WarrantyPromise may appear as values for the following properties
|The warranty promise(s) included in the offer. Supersedes warrantyPromise.|
AcknowledgementsThis 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