A171

• Offering

accepted payment methods (0..*)

The gr:PaymentMethod or methods accepted by the gr:BusinessEntity for the given gr:Offering.

• ObjectProperty

Actual product or service instance (DEPRECATED)

DEPRECATED - This class is superseded by gr:Individual. Replace all occurrences of gr:ActualProductOrServiceInstance by gr:Individual, if possible.

• Class

add-on (0..*)

This property points from a gr:Offering to additional offerings that can only be obtained in combination with the first offering. This can be used to model supplements and extensions that are available for a surcharge. Any gr:PriceSpecification attached to the secondary offering is to be understood as an additional charge.

• ObjectProperty

advance booking requirement (0..1)

The minimal and maximal amount of time that is required between accepting the gr:Offering and the actual usage of the resource or service. This is mostly relevant for offers regarding hotel rooms, the rental of objects, or the provisioning of services. The duration is specified relatively to the beginning of the usage of the contracted object. It is represented by attaching an instance of the class gr:QuantitativeValueInteger. The lower and upper boundaries are specified using the properties gr:hasMinValueInteger and gr:hasMaxValueInteger to that instance. The unit of measurement is specified using the property gr:hasUnitOfMeasurement with a string holding a UN/CEFACT code suitable for durations, e.g. MON (months), DAY (days), HUR (hours), or MIN (minutes). The difference to the gr:validFrom and gr:validThrough properties is that those specify the interval during which the gr:Offering is valid, while gr:advanceBookingRequirement specifies the acceptable relative amount of time between accepting the offer and the fulfilment or usage.

• ObjectProperty

American Express (payment method)

Payment by credit or debit cards issued by the American Express network.

• Payment method credit card

amount of this good (1..1)

This property specifies the quantity of the goods included in the gr:Offering via this gr:TypeAndQuantityNode. The quantity is given in the unit of measurement attached to the gr:TypeAndQuantityNode.

• DatatypeProperty

applies to delivery method (0..*)

This property specifies the gr:DeliveryMethod to which the gr:DeliveryChargeSpecification applies.

• ObjectProperty

applies to payment method (1..*)

This property specifies the gr:PaymentMethod to which the gr:PaymentChargeSpecification applies.

• ObjectProperty

availability ends (0..1)

This property specifies the end of the availability of the gr:ProductOrService included in the gr:Offering. The difference to the properties gr:validFrom and gr:validThrough is that those specify the period of time during which the offer is valid and can be accepted. Example: I offer to lease my boat for the period of August 1 - August 31, 2010, but you must accept by offer no later than July 15. A time-zone should be specified. For a time in GMT/UTC, simply add a "Z" following the time: 2008-05-30T09:30:10Z. Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time: 2008-05-30T09:30:10-09:00 or 2008-05-30T09:30:10+09:00. Note: There is another property gr:availableAtOrFrom, which is used to indicate the gr:Location (e.g. store or shop) from which the goods would be available.

• DatatypeProperty

availability starts (0..1)

This property specifies the beginning of the availability of the gr:ProductOrService included in the gr:Offering. The difference to the properties gr:validFrom and gr:validThrough is that those specify the period of time during which the offer is valid and can be accepted. Example: I offer to lease my boat for the period of August 1 - August 31, 2010, but you must accept by offer no later than July 15. A time-zone should be specified. For a time in GMT/UTC, simply add a "Z" following the time: 2008-05-30T09:30:10Z. Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time: 2008-05-30T09:30:10-09:00 or 2008-05-30T09:30:10+09:00. Note: There is another property gr:availableAtOrFrom, which is used to indicate the gr:Location (e.g. store or shop) from which the goods would be available.

• DatatypeProperty

available at or from (0..*)

This states that a particular gr:Offering is available at or from the given gr:Location (e.g. shop or branch).

• ObjectProperty

available delivery methods (0..*)

This specifies the gr:DeliveryMethod or methods available for a given gr:Offering.

• ObjectProperty

billing increment (0..1)

This property specifies the minimal quantity and rounding increment that will be the basis for the billing. The unit of measurement is specified by the UN/CEFACT code attached to the gr:UnitPriceSpecification via the gr:hasUnitOfMeasurement property. Examples: - The price for gasoline is 4 USD per gallon at the pump, but you will be charged in units of 0.1 gallons. - The price for legal consulting is 100 USD per hour, but you will be charged in units of 15 minutes. This property makes sense only for instances of gr:Offering that include not more than one type of good or service.

• DatatypeProperty

Brand

A brand is the identity of a specific product, service, or business. Use foaf:logo for attaching a brand logo and gr:name or rdfs:label for attaching the brand name. (Source: Wikipedia, the free encyclopedia, see http://en.wikipedia.org/wiki/Brand)

• Class

Business (business entity type)

The gr:BusinessEntityType representing such agents that are themselves offering commercial services or products on the market. Usually, businesses are characterized by the fact that they are officially registered with the public administration and strive for profits by their activities.

• Business entity type

Business entity

An instance of this class represents the legal agent making (or seeking) a particular offering. This can be a legal body or a person. A business entity has at least a primary mailing address and contact details. For this, typical address standards (vCard) and location data (geo, WGS84) can be attached. Note that the location of the business entity is not necessarily the location from which the product or service is being available (e.g. the branch or store). Use gr:Location for stores and branches. Example: Siemens Austria AG, Volkswagen Ltd., Peter Miller's Cell phone Shop LLC Compatibility with schema.org: This class is equivalent to the union of http://schema.org/Person and http://schema.org/Organization.

• Class

Business entity type

A business entity type is a conceptual entity representing the legal form, the size, the main line of business, the position in the value chain, or any combination thereof, of a gr:BusinessEntity. From the ontological point of view, business entity types are mostly roles that a business entity has in the market. Business entity types are important for specifying eligible customers, since a gr:Offering is often valid only for business entities of a certain size, legal structure, or role in the value chain. Examples: Consumers, Retailers, Wholesalers, or Public Institutions

• Class

Business function

The business function specifies the type of activity or access (i.e., the bundle of rights) offered by the gr:BusinessEntity on the gr:ProductOrService through the gr:Offering. Typical are sell, rental or lease, maintenance or repair, manufacture / produce, recycle / dispose, engineering / construction, or installation. Licenses and other proprietary specifications of access rights are also instances of this class. Examples: A particular offering made by Miller Rentals Ltd. says that they (1) sell Volkswagen Golf convertibles, (2) lease out a particular Ford pick-up truck, and (3) dispose car wrecks of any make and model.

• Class

Buy (business function, DEPRECATED)

This gr:BusinessFunction indicates that the gr:BusinessEntity is in general interested in purchasing the specified gr:ProductOrService. DEPRECATED. Use gr:seeks instead.

• Business function

By bank transfer in advance (payment method)

Payment by bank transfer in advance, i.e., the offering gr:BusinessEntity will inform the buying party about their bank account details and will deliver the goods upon receipt of the due amount. This is equivalent to payment by wire transfer.

• Payment method

By invoice (payment method)

Payment by bank transfer after delivery, i.e., the offering gr:BusinessEntity will deliver first, inform the buying party about the due amount and their bank account details, and expect payment shortly after delivery.

• Payment method

COD (payment method)

Collect on delivery / Cash on delivery - A payment method where the recipient of goods pays at the time of delivery. Usually, the amount of money is collected by the transportation company handling the goods.

• Payment method

Cash (payment method)

Payment by cash upon delivery or pickup.

• Payment method

category (0..*)

The name of a category to which this gr:ProductOrService, gr:Offering, gr:BusinessEntity, or gr:Location belongs. Note 1: For products, it is better to add an rdf:type statement referring to a GoodRelations-compliant ontology for vertical industries instead, but if you just have a short text label, gr:category is simpler. Note 2: You can use greater signs or slashes to informally indicate a category hierarchy, e.g. "restaurants/asian_restaurants" or "cables > usb_cables"

• DatatypeProperty

Check in advance (payment method)

Payment by sending a check in advance, i.e., the offering gr:BusinessEntity will deliver the goods upon receipt of a check over the due amount. There are variations in handling payment by check - sometimes, shipment will be upon receipt of the check as a document, sometimes the shipment will take place only upon successful crediting of the check.

• Payment method

closes (1..1)

The closing hour of the gr:Location on the given gr:DayOfWeek. If no time-zone suffix is included, the time is given in the local time valid at the gr:Location. For a time in GMT/UTC, simply add a "Z" following the time: 09:30:10Z. Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time: 09:30:10-09:00 09:30:10+09:00. Note 1: Use 00:00:00 for the first second of the respective day and 23:59:59 for the last second of that day. Note 2: If a store opens at 17:00 on Saturdays and closes at 03:00:00 a.m. next morning, use two instances of this class, one with 17:00:00 - 23:59:59 for Saturday and another one with 00:00:00 - 03:00:00 for Sunday. Note 3: If the shop re-opens on the same day of the week or set of days of the week, you must create a second instance of gr:OpeningHoursSpecification.

• DatatypeProperty

color (0..1)

The color of the product.

• DatatypeProperty

condition (0..1)

A textual description of the condition of the product or service, or the products or services included in the offer (when attached to a gr:Offering)

• DatatypeProperty

Construction / installation (business function)

This gr:BusinessFunction indicates that the gr:BusinessEntity offers (or seeks) the construction and/or installation of the specified gr:ProductOrService at the customer's location.

• Business function

contributor

• AnnotationProperty

creator

• AnnotationProperty

DHL (delivery method)

Delivery via the parcel service DHL.

• Delivery mode parcel service

datatype product or service property (0..*)

This property is the super property for all pure datatype properties that can be used to describe a gr:ProductOrService. In products and services ontologies, only such properties that are no quantitative properties and that have no predefined gr:QualitativeValue instances are subproperties of this property. In practice, this refers to a few integer properties for which the integer value represents qualitative aspects, for string datatypes (as long as no predefined values exist), for boolean datatype properties, and for dates and times.

• DatatypeProperty

Day of week

The day of the week, used to specify to which day the opening hours of a gr:OpeningHoursSpecification refer. Examples: Monday, Tuesday, Wednesday,...

• Class

Delivery charge specification

A delivery charge specification is a conceptual entity that specifies the additional costs asked for the delivery of a given gr:Offering using a particular gr:DeliveryMethod by the respective gr:BusinessEntity. A delivery charge specification is characterized by (1) a monetary amount per order, specified as a literal value of type float in combination with a currency, (2) the delivery method, (3) the target country or region, and (4) whether this charge includes local sales taxes, namely VAT. A gr:Offering may be linked to multiple gr:DeliveryChargeSpecification nodes that specify alternative charges for disjoint combinations of target countries or regions, and delivery methods. Examples: Delivery by direct download is free of charge worldwide, delivery by UPS to Germany is 10 Euros per order, delivery by mail within the US is 5 Euros per order. The total amount of this charge is specified as a float value of the gr:hasCurrencyValue property. The currency is specified via the gr:hasCurrency datatype property. Whether the price includes VAT or not is indicated by the gr:valueAddedTaxIncluded property. The gr:DeliveryMethod to which this charge applies is specified using the gr:appliesToDeliveryMethod object property. The region or regions to which this charge applies is specified using the gr:eligibleRegions property, which uses ISO 3166-1 and ISO 3166-2 codes. If the price can only be given as a range, use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue for the upper and lower bounds. Important: When querying for the price, always use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue.

• Class

delivery lead time (0..1)

This property can be used to indicate the promised delay between the receipt of the order and the goods leaving the warehouse. The duration is specified by attaching an instance of gr:QuantitativeValueInteger. The lower and upper boundaries are specified using the properties gr:hasMinValueInteger and gr:hasMaxValueInteger to that instance. A point value can be modeled with the gr:hasValueInteger property. The unit of measurement is specified using the property gr:hasUnitOfMeasurement with a string holding a UN/CEFACT code suitable for durations, e.g. MON (months), DAY (days), HUR (hours), or MIN (minutes).

• ObjectProperty

Delivery method

A delivery method is a standardized procedure for transferring the product or service to the destination of fulfilment chosen by the customer. Delivery methods are characterized by the means of transportation used, and by the organization or group that is the contracting party for the sending gr:BusinessEntity (this is important, since the contracted party may subcontract the fulfilment to smaller, regional businesses). Examples: Delivery by mail, delivery by direct download, delivery by UPS

• Class

Delivery mode direct download (delivery method)

Delivery of the goods via direct download from the Internet, i.e., the offering gr:BusinessEntity provides the buying party with details on how to retrieve the goods online. Connection fees and other costs of using the infrastructure are to be carried by the buying party.

• Delivery method

Delivery mode freight (delivery method)

Delivery by an unspecified air, sea, or ground freight carrier or cargo company.

• Delivery method

Delivery mode mail (delivery method)

Delivery via regular mail service (private or public postal services).

• Delivery method

Delivery mode own fleet (delivery method)

Delivery of the goods by using a fleet of vehicles either owned and operated or subcontracted by the gr:BusinessEntity.

• Delivery method

Delivery mode parcel service

A private parcel service as the delivery mode available for a certain offering. Examples: UPS, DHL

• Class

Delivery mode pick up (delivery method)

Delivery of the goods by picking them up at one of the stores etc. (gr:Location) during the opening hours as specified by respective instances of gr:OpeningHoursSpecification.

• Delivery method

depiction

• ObjectProperty

deprecated

• AnnotationProperty

depth (0..1)

The depth of the product. Typical unit code(s): CMT for centimeters, INH for inches

• ObjectProperty

description

• DatatypeProperty

description (0..1)

A short textual description of the resource. This property is semantically equivalent to rdfs:comment and just meant as a handy shortcut for marking up data.

• DatatypeProperty

Diners Club (payment method)

Payment by credit or debit cards issued by the Diner's Club network.

• Payment method credit card

Direct debit (payment method)

Payment by direct debit, i.e., the buying party will inform the offering gr:BusinessEntity about its bank account details and authorizes the gr:BusinessEntity to collect the agreed amount directly from that account.

• Payment method

Discover (payment method)

Payment by credit or debit cards issued by the Discover network.

• Payment method credit card

display position (0..1)

The position at which the option or element should be listed in a menu or user dialog, lower numbers come first. The main usage of this property are the days of the week (gr:DayOfWeek), but it is also possible to apply it e.g. to product features or any other conceptual element. Note: Rely on this property only for data originating from a single RDF graph; otherwise, unpredictable results are possible.

• AnnotationProperty

Dispose (business function)

This gr:BusinessFunction indicates that the gr:BusinessEntity offers (or seeks) the acceptance of the specified gr:ProductOrService for proper disposal, recycling, or any other kind of allowed usages, freeing the current owner from all rights and obligations of ownership.

• Business function

duration of warranty in months (0..1)

This property specifies the duration of the gr:WarrantyPromise in months.

• DatatypeProperty

eligible customer types (0..*)

The types of customers (gr:BusinessEntityType) for which the given gr:Offering is valid.

• ObjectProperty

eligible duration (0..1)

The minimal and maximal duration for which the given gr:Offering or gr:License is valid. This is mostly used for offers regarding accommodation, the rental of objects, or software licenses. The duration is specified by attaching an instance of gr:QuantitativeValue. The lower and upper boundaries are specified using the properties gr:hasMinValue and gr:hasMaxValue to that instance. If they are the same, use the gr:hasValue property. The unit of measurement is specified using the property gr:hasUnitOfMeasurement with a string holding a UN/CEFACT code suitable for durations, e.g. MON (months), DAY (days), HUR (hours), or MIN (minutes). The difference to the gr:validFrom and gr:validThrough properties is that those specify the absiolute interval during which the gr:Offering or gr:License is valid, while gr:eligibleDuration specifies the acceptable duration of the contract or usage.

• ObjectProperty

eligible regions (0..*)

This property specifies the geo-political region or regions for which the gr:Offering, gr:License, or gr:DeliveryChargeSpecification is valid using the two-character version of ISO 3166-1 (ISO 3166-1 alpha-2) for regions or ISO 3166-2 , which breaks down the countries from ISO 3166-1 into administrative subdivisions. Important: Do NOT use 3-letter ISO 3166-1 codes!

• DatatypeProperty

eligible transaction volume (0..1)

This property can be used to indicate the transaction volume, in a monetary unit, for which the gr:Offering or gr:PriceSpecification is valid. This is mostly used to specify a minimal purchasing volume, to express free shipping above a certain order volume, or to limit the acceptance of credit cards to purchases above a certain amount. The object is a gr:PriceSpecification that uses the properties gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue to indicate the lower and upper boundaries and gr:hasCurrency to indicate the currency using the ISO 4217 standard (3 characters).

• ObjectProperty

Enduser (business entity type)

The gr:BusinessEntityType representing such agents that are purchasing the good or service for private consumption, in particular not for resale or for usage within an industrial enterprise. By default, a Business Entity is an Enduser.

• Business entity type

equal (0..*)

This ordering relation for qualitative values indicates that the subject is equal to the object.

• ObjectProperty
• SymmetricProperty
• TransitiveProperty

Federal Express (delivery method)

Delivery via the parcel service Federal Express.

• Delivery mode parcel service

Friday (day of week)

Friday as a day of the week.

• Day of week

GoodRelations Ontology

The GoodRelations ontology provides the vocabulary for annotating e-commerce offerings (1) to sell, lease, repair, dispose, or maintain commodity products and (2) to provide commodity services. GoodRelations allows describing the relationship between (1) Web resources, (2) offerings made by those Web resources, (3) legal entities, (4) prices, (5) terms and conditions, and the aforementioned ontologies for products and services (6). For more information, see http://purl.org/goodrelations/ Note: The base URI of GoodRelations is http://purl.org/goodrelations/v1. Please make sure you are only using element identifiers in this namespace, e.g. http://purl.org/goodrelations/v1#BusinessEntity. There may be copies of the ontology file on the Web which can be retrieved from other locations, BUT THOSE LOCATIONS MUST NOT BE USED AS THE BASIS OF IDENTIFIERS. If you use GoodRelations for scientific purposes, please cite our paper: Hepp, Martin: GoodRelations: An Ontology for Describing Products and Services Offers on the Web, Proceedings of the 16th International Conference on Knowledge Engineering and Knowledge Management (EKAW2008), September 29 - October 3, 2008, Acitrezza, Italy, Springer LNCS, Vol. 5268, pp. 332-347. PDF at http://www.heppnetz.de/publications/

• Ontology

Google Checkout (payment method)

Payment via the Google Checkout payment service.

• Payment method

greater (0..*)

This ordering relation for qualitative values indicates that the subject is greater than the object.

• ObjectProperty
• TransitiveProperty

greater or equal (0..*)

This ordering relation for qualitative values indicates that the subject is greater than or equal to the object.

• ObjectProperty
• TransitiveProperty

has DUNS (0..1)

The Dun & Bradstreet DUNS number for identifying a gr:BusinessEntity. The Dun & Bradstreet DUNS is a nine-digit number used to identify legal entities (but usually not branches or locations of logistical importance only).

• DatatypeProperty

has EAN/UCC-13 (0..*)

The EAN·UCC-13 code of the given gr:ProductOrService or gr:Offering. This code is now officially called GTIN-13 (Global Trade Identifier Number) or EAN·UCC-13. Former 12-digit UPC codes can be converted into EAN·UCC-13 code by simply adding a preceeding zero. Note 1: When using this property for searching by 12-digit UPC codes, you must add a preceeding zero digit. Note 2: As of January 1, 2007, the former ISBN numbers for books etc. have been integrated into the EAN·UCC-13 code. For each old ISBN-10 code, there exists a proper translation into EAN·UCC-13 by adding "978" or "979" as prefix. Since the old ISBN-10 is now deprecated, GoodRelations does not provide a property for ISBNs.

• DatatypeProperty

has GTIN-14 (0..*)

The Global Trade Item Number (GTIN-14) of the given gr:ProductOrService or gr:Offering.

• DatatypeProperty

has GTIN-8 (0..*)

The 8-digit Global Trade Item Number (GTIN-8) of the given gr:ProductOrService or gr:Offering, also known as EAN/UCC-8 (8-digit EAN).

• DatatypeProperty

has Global Location Number (0..1)

The Global Location Number (GLN, sometimes also referred to as International Location Number or ILN) of the respective gr:BusinessEntity or gr:Location. The Global Location Number is a thirteen-digit number used to identify parties and physical locations.

• DatatypeProperty

has ISIC v4 (0..*)

The International Standard of Industrial Classification of All Economic Activities (ISIC), Revision 4 code for a particular gr:BusinessEntity or gr:Location. See http://unstats.un.org/unsd/cr/registry/isic-4.asp for more information. Note: While ISIC codes are sometimes misused for classifying products or services, they are designed and suited only for classifying business establishments.

• DatatypeProperty

has MPN (0..*)

The Manufacturer Part Number or MPN is a unique identifier for a product, service, or bundle from the perspective of a particular manufacturer. MPNs can be assigned to products or product datasheets, or bundles. Accordingly, the domain of this property is the union of gr:ProductOrService (the common superclass of goods and datasheets), and gr:Offering. Important: Be careful when assuming two products or services instances or offering instances to be identical based on the MPN. Since MPNs are unique only for the same gr:BusinessEntity, this holds only when the two MPN values refer to the same gr:BusinessEntity. Such can be done by taking into account the provenance of the data. Usually, the properties gr:hasEAN_UCC-13 and gr:hasGTIN-14 are much more reliable identifiers, because they are globally unique. See also http://en.wikipedia.org/wiki/Part_number

• DatatypeProperty

has NAICS (0..*)

The North American Industry Classification System (NAICS) code for a particular gr:BusinessEntity. See http://www.census.gov/eos/www/naics/ for more details. Note: While NAICS codes are sometimes misused for classifying products or services, they are designed and suited only for classifying business establishments.

• DatatypeProperty

has POS (0..*)

This property states that the respective gr:Location is a point of sale for the respective gr:BusinessEntity. It allows linking those two types of entities without the need for a particular gr:Offering.

• ObjectProperty

has Stock Keeping Unit (0..*)

The Stock Keeping Unit, or SKU is a unique identifier for a product, service, or bundle from the perspective of a particular supplier, i.e. SKUs are mostly assigned and serialized at the merchant level. Examples of SKUs are the ordering or parts numbers used by a particular Web shop or catalog. Consequently, the domain of gr:hasStockKeepingUnit is the union of the classes gr:Offering and gr:ProductOrService. If attached to a gr:Offering, the SKU will usually reflect a merchant-specific identifier, i.e. one valid only for that particular retailer or shop. If attached to a gr:ProductOrServiceModel, the SKU can reflect either the identifier used by the merchant or the part number used by the official manufacturer of that part. For the latter, gr:hasMPN is a better choice. Important: Be careful when assuming two products or services instances or offering instances to be identical based on the SKU. Since SKUs are unique only for the same gr:BusinessEntity, this can be assumed only when you are sure that the two SKU values refer to the same business entity. Such can be done by taking into account the provenance of the data. As long as instances of gr:Offering are concerned, you can also check that the offerings are being offered by the same gr:Business Entity. Usually, the properties gr:hasEAN_UCC-13 and gr:hasGTIN-14 are much more reliable identifiers, because they are globally unique. See also http://en.wikipedia.org/wiki/Stock_Keeping_Unit.

• DatatypeProperty

has brand (0..*)

This specifies the brand or brands (gr:Brand) associated with a gr:ProductOrService, or the brand or brands maintained by a gr:BusinessEntity.

• ObjectProperty

has business function (1..*)

This specifies the business function of the gr:Offering, i.e. whether the gr:BusinessEntity is offering to sell, to lease, or to repair the particular type of product. In the case of bundles, it is also possible to attach individual business functions to each gr:TypeAndQuantityNode. The business function of the main gr:Offering determines the business function for all included objects or services, unless a business function attached to a gr:TypeAndQuantityNode overrides it. Note: While it is possible that an entity is offering multiple types of business functions for the same set of objects (e.g. rental and sales), this should usually not be stated by attaching multiple business functions to the same gr:Offering, since the gr:UnitPriceSpecification for the varying business functions will typically be very different.

• ObjectProperty

has currency (1..1)

The currency for all prices in the gr:PriceSpecification given using the ISO 4217 standard (3 characters).

• DatatypeProperty

has currency value (0..1)

This property specifies the amount of money for a price per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc. For a gr:UnitPriceSpecification, this is the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the price per delivery or payment. GoodRelations also supports giving price information as intervals only. If this is needed, use gr:hasMaxCurrencyValue for the upper bound and gr:hasMinCurrencyValue for the lower bound. Using gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y.

• DatatypeProperty

has eligible quantity (0..1)

This specifies the interval and unit of measurement of ordering quantities for which the gr:Offering or gr:PriceSpecification is valid. This allows e.g. specifying that a certain freight charge is valid only for a certain quantity. Note that if an offering is a bundle, i.e. it consists of more than one unit of a single type of good, or if the unit of measurement for the good is different from unit (Common Code C62), then gr:hasEligibleQuantity refers to units of this bundle. In other words, "C62" for "Units or pieces" is usually the appropriate unit of measurement.

• ObjectProperty

has inventory level (0..1)

This property specifies the current approximate inventory level for gr:SomeItems. The unit of measurement and the point value or interval are indicated using the attached gr:QuantitativeValueFloat instance. This property can also be attached to a gr:Offering in cases where the included products are not modeled in more detail.

• ObjectProperty

has make and model (0..1)

This states that an actual product instance (gr:Individual) or a placeholder instance for multiple, unidentified such instances (gr:SomeItems) is one occurence of a particular gr:ProductOrServiceModel. Example: myFordT hasMakeAndModel FordT.

• ObjectProperty

has manufacturer (0..1)

This object property links a gr:ProductOrService to the gr:BusinessEntity that produces it. Mostly used with gr:ProductOrServiceModel.

• ObjectProperty

has max currency value (1..1)

This property specifies the UPPER BOUND of the amount of money for a price RANGE per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc. For a gr:UnitPriceSpecification, this is the UPPER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the UPPER BOUND of the price per delivery or payment. Using gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y.

• DatatypeProperty

has max value (0..1)

This property captures the upper limit of a gr:QuantitativeValue instance.

• DatatypeProperty

has max value float (1..1)

This property captures the upper limit of a gr:QuantitativeValueFloat instance.

• DatatypeProperty

has max value integer (1..1)

This property captures the upper limit of a gr:QuantitativeValueInteger instance.

• DatatypeProperty

has min currency value (1..1)

This property specifies the LOWER BOUND of the amount of money for a price RANGE per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc. For a gr:UnitPriceSpecification, this is the LOWER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the LOWER BOUND of the price per delivery or payment. Using gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y.

• DatatypeProperty

has min value (0..1)

This property captures the lower limit of a gr:QuantitativeValue instance.

• DatatypeProperty

has min value float (1..1)

This property captures the lower limit of a gr:QuantitativeValueFloat instance.

• DatatypeProperty

has min value integer (1..1)

This property captures the lower limit of a gr:QuantitativeValueInteger instance.

• DatatypeProperty

has next (0..1)

This ordering relation for gr:DayOfWeek indicates that the subject is directly followed by the object. Example: Monday hasNext Tuesday Since days of the week are a cycle, this property is not transitive.

• ObjectProperty

has opening hours day of week (1..*)

This specifies the gr:DayOfWeek to which the gr:OpeningHoursSpecification is related. Note: Use multiple instances of gr:OpeningHoursSpecification for specifying the opening hours for multiple days if the opening hours differ.

• ObjectProperty

has opening hours specification (0..*)

This property links a gr:Location to a gr:OpeningHoursSpecification.

• ObjectProperty

has previous (0..1)

This ordering relation for gr:DayOfWeek indicates that the subject is directly preceeded by the object. Example: Tuesday hasPrevious Monday Since days of the week are a cycle, this property is not transitive.

• ObjectProperty

has price specification (0..*)

This links a gr:Offering to a gr:PriceSpecification or specifications. There can be unit price specifications, payment charge specifications, and delivery charge specifications. For each type, multiple specifications for the same gr:Offering are possible, e.g. for different quantity ranges or for different currencies, or for different combinations of gr:DeliveryMethod and target destinations. Recommended retail prices etc. can be marked by the gr:priceType property of the gr:UnitPriceSpecification.

• ObjectProperty

has unit of measurement (1..1)

The unit of measurement for a gr:QuantitativeValue, a gr:UnitPriceSpecification, or a gr:TypeAndQuantityNode given using the UN/CEFACT Common Code (3 characters).

• DatatypeProperty

has value (0..1)

This subproperty specifies that the upper and lower limit of the given gr:QuantitativeValue are identical and have the respective value. It is a shortcut for such cases where a quantitative property is (at least practically) a single point value and not an interval.

• DatatypeProperty

has value float (0..1)

This subproperty specifies that the upper and lower limit of the given gr:QuantitativeValueFloat are identical and have the respective float value. It is a shortcut for such cases where a quantitative property is (at least practically) a single point value and not an interval.

• DatatypeProperty

has value integer (0..1)

This subproperty specifies that the upper and lower limit of the given gr:QuantitativeValueInteger are identical and have the respective integer value. It is a shortcut for such cases where a quantitative property is (at least practically) a single point value and not an interval.

• DatatypeProperty

has warranty promise (0..*)

This specifies the gr:WarrantyPromise made by the gr:BusinessEntity for the given gr:Offering.

• ObjectProperty

has warranty scope (0..1)

This states the gr:WarrantyScope of a given gr:WarrantyPromise.

• ObjectProperty

height (0..1)

The height of the product. Typical unit code(s): CMT for centimeters, INH for inches

• ObjectProperty

homepage

• AnnotationProperty

image

• ObjectProperty

includes (0..1)

This object property is a shortcut for the original gr:includesObject property for the common case of having exactly one single gr:ProductOrService instance included in an Offering. When linking to an instance of gr:SomeItems or gr:Individual, it is equivalent to using a gr:TypeAndQuantityNode with gr:hasUnitOfMeasurement="C62"^^xsd:string and gr:amountOfThisGood="1.0"^^xsd:float for that good. When linking to a gr:ProductOrServiceModel, it is equivalent to 1. defining an blank node for a gr:SomeItems 2. linking that blank node via gr:hasMakeAndModel to the gr:ProductOrServiceModel, and 3. linking from the gr:Offering to that blank node using another blank node of type gr:TypeAndQuantityNode with gr:hasUnitOfMeasurement="C62"^^xsd:string and gr:amountOfThisGood="1.0"^^xsd:float for that good.

• ObjectProperty

includes object (0..*)

This object property links a gr:Offering to one or multiple gr:TypeAndQuantityNode or nodes that specify the components that are included in the respective offer.

• ObjectProperty

Individual

A gr:Individual is an actual product or service instance, i.e., a single identifiable object or action that creates some increase in utility (in the economic sense) for the individual possessing or using this very object (product) or for the individual in whose favor this very action is being taken (service). Products or services are types of goods in the economic sense. For an overview of goods and commodities in economics, see Milgate (1987). Examples: MyThinkpad T60, the pint of beer standing in front of me, my Volkswagen Golf, the haircut that I received or will be receiving at a given date and time. Note 1: In many cases, product or service instances are not explicitly exposed on the Web but only claimed to exist (i.e. existentially quantified). In this case, use gr:SomeItems. Note 2: This class is the new, shorter form of the former gr:ActualProductOrServiceInstance. Compatibility with schema.org: This class is a subclass of http://schema.org/Product.

• Class

is accessory or spare part for (0..*)

This states that a particular gr:ProductOrService is an accessory or spare part for another product or service.

• ObjectProperty

is consumable for (0..*)

This states that a particular gr:ProductOrService is a consumable for another product or service.

• ObjectProperty

is list price (DEPRECATED)

This boolean attribute indicates whether a gr:UnitPriceSpecification is a list price (usually a vendor recommendation) or not. "true" indicates it is a list price, "false" indicates it is not. DEPRECATED. Use the gr:priceType property instead.

• DatatypeProperty

is similar to (0..*)

This states that a given gr:ProductOrService is similar to another product or service. Of course, this is a subjective statement; when interpreting it, the trust in the origin of the statement should be taken into account.

• ObjectProperty

is variant of (0..1)

This states that a particular gr:ProductOrServiceModel is a variant of another product or service model. It is pretty safe to infer that the variant inherits all gr:quantitativeProductOrServiceProperty, gr:qualitativeProductOrServiceProperty, and gr:datatypeProductOrServiceProperty values that are defined for the first gr:ProductOrServiceModel. Example: foo:Red_Ford_T_Model gr:isVariantOf foo:Ford_T_Model

• ObjectProperty

JCB (payment method)

Payment by credit or debit cards issued by the JCB network.

• Payment method credit card

Labor / bring-in (warranty scope)

In case of a defect or malfunction, the buying party has the right to transport the good to a service location determined by the the selling gr:BusinessEntity and will be charged only for parts and materials needed to fix the problem. Labor will be covered by the selling business entity or one of its partnering business entities. Note: This is just a rough classification for filtering offers. It is up to the buying party to check the exact scope and terms and conditions of the gr:WarrantyPromise.

• Warranty scope

Lease Out (business function)

This gr:BusinessFunction indicates that the gr:BusinessEntity offers (or seeks) the temporary right to use the specified gr:ProductOrService.

• Business function

legal name (0..1)

The legal name of the gr:BusinessEntity.

• DatatypeProperty

lesser (0..*)

This ordering relation for gr:QualitativeValue pairs indicates that the subject is lesser than the object.

• ObjectProperty
• TransitiveProperty

lesser or equal (0..*)

This ordering relation for gr:QualitativeValue pairs indicates that the subject is lesser than or equal to the object.

• ObjectProperty
• TransitiveProperty

license

• AnnotationProperty

License

A license is the specification of a bundle of rights that determines the type of activity or access offered by the gr:BusinessEntity on the gr:ProductOrService through the gr:Offering. Licenses can be standardized (e.g. LPGL, Creative Commons, ...), vendor-specific, or individually defined for a single offer or product. Whether there is a fee for obtaining the license is specified using the gr:UnitPriceSpecification attached to the gr:Offering. Use foaf:page for linking to a document containing the license, e.g. in PDF or HTML.

• Class

Location

A location is a point or area of interest from which a particular product or service is available, e.g. a store, a bus stop, a gas station, or a ticket booth. The difference to gr:BusinessEntity is that the gr:BusinessEntity is the legal entity (e.g. a person or corporation) making the offer, while gr:Location is the store, office, or place. A chain restaurant will e.g. have one legal entity but multiple restaurant locations. Locations are characterized by an address or geographical position and a set of opening hour specifications for various days of the week. Example: A rental car company may offer the Business Function Lease Out of cars from two locations, one in Fort Myers, Florida, and one in Boston, Massachussetts. Both stations are open 7:00 - 23:00 Mondays through Saturdays. Note: Typical address standards (vcard) and location data (geo, WGC84) should be attached to a gr:Location node. Since there already exist established vocabularies for this, the GoodRelations ontology does not provide respective attributes. Instead, the use of respective vocabularies is recommended. However, the gr:hasGlobalLocationNumber property is provided for linking to public identifiers for business locations. Compatibility with schema.org: This class is equivalent to http://schema.org/Place.

• Class

Location of sales or service provisioning (DEPRECATED)

DEPRECATED - This class is superseded by gr:Location. Replace all occurrences of gr:LocationOfSalesOrServiceProvisioning by gr:Location, if possible.

• Class

Maintain (business function)

This gr:BusinessFunction indicates that the gr:BusinessEntity offers (or seeks) typical maintenance tasks for the specified gr:ProductOrService. Maintenance tasks are actions that undo or compensate for wear or other deterioriation caused by regular usage, in order to restore the originally intended function of the product, or to prevent outage or malfunction.

• Business function

manufacturer

• ObjectProperty

MasterCard (payment method)

Payment by credit or debit cards issued by the MasterCard network.

• Payment method credit card

Monday (day of week)

Monday as a day of the week.

• Day of week

N-ary relations (DEPRECATED)

This is the superclass for all classes that are placeholders for n-ary relations, which OWL cannot represent. DEPRECATED. Do not use this class in data or queries.

• Class

name

• DatatypeProperty

name (0..1)

A short text describing the respective resource. This property is semantically equivalent to dcterms:title and rdfs:label and just meant as a handy shortcut for marking up data.

• DatatypeProperty

non equal (0..*)

This ordering relation for gr:QualitativeValue pairs indicates that the subject is not equal to the object.

• ObjectProperty
• SymmetricProperty

Offer

• Class

Offering

An offering represents the public, not necessarily binding, not necessarily exclusive, announcement by a gr:BusinessEntity to provide (or seek) a certain gr:BusinessFunction for a certain gr:ProductOrService to a specified target audience. An offering is specified by the type of product or service or bundle it refers to, what business function is being offered (sales, rental, ...), and a set of commercial properties. It can either refer to (1) a clearly specified instance (gr:Individual), (2) to a set of anonymous instances of a given type (gr:SomeItems), (3) a product model specification (gr:ProductOrServiceModel), see also section 3.3.3 of the GoodRelations Technical Report. An offering may be constrained in terms of the eligible type of business partner, countries, quantities, and other commercial properties. The definition of the commercial properties, the type of product offered, and the business function are explained in other parts of this vocabulary in more detail. Example: Peter Miller offers to repair TV sets made by Siemens, Volkswagen Innsbruck sells a particular instance of a Volkswagen Golf at $10,000. Compatibility with schema.org: This class is a superclass to http://schema.org/Offer, since gr:Offering can also represent demand.

• Class

offers (0..*)

This links a gr:BusinessEntity to the offers (gr:Offering) it makes. If you want to express interest in receiving offers, use gr:seeks instead.

• ObjectProperty