This is a conceptual entity that holds together all aspects of the n-ary relation AcceptedPaymentMethods.
An Actual Product or Service Instance is 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 whoses 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: In many cases, product or service instances are not explicitly exposed on the Web but only existentially quantified. For a detailed discussion and practical solutions, see section 3.3.3 of the GoodRelations Technical Report.
This is a conceptual entity that holds together all aspects of the n-ary relation AvailableDeliveryMethods
An instance of this class represents the legal agent making 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 can be attached. The location may be important for finding a supplier within a given distance from our own location. Example: Siemens Austria AG, Volkswagen Ltd., Peter Miller's Cellphone Shop Note: Typical address standards (vcard) and location data should be attached to a business entity. 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 hasGlobalLocationNumber and hasDUNS properties are provided for linking to respective identifiers for business locations.
In domain of - gr:offers gr:hasDUNS gr:legalName
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 Business Entity. 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 Offerings are often meant only for Business Entities of a certain size, legal structure, or role in the value chain. Examples: Consumers, Retailers, Wholesalers, or Public Institutions
In range of - gr:eligibleCustomerTypes
The Business Function specifies the type of activity or access offered by the Business Entity on the Product or Services though the Offering. The idea of standardizing business functions was first put to practice by the UNSPSC Business Functions Identifiers (UNSPSC BFI). We take their basic types of business functions as a starting point. Typical are sell, rental or lease, maintenance or repair, manufacture / produce, recycle / dispose, engineering / construction, or installation 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.
In range of - gr:hasBusinessFunction
The day of the week, used to specify to which the opening hours of an OpeningHoursSpecification refer. Examples: Monday, Tuesday, Wednesday,...
In range of - gr:hasOpeningHoursDayOfWeek
A Delivery Charge Specification is a conceptual entity that specifies the additional costs asked for delivery of a given Offering using a particular Delivery Method by the respective Business Entity. 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) a whether this charge includes local sales taxes, namely VAT. An Offering may be linked to multiple Delivery Charge Specifications 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 surcharge is specified as a float value of hasCurrencyValue. The currency is specified via the hasCurrency datatype property. Whether the price includes VAT or not is indicated by the ValueAddedTaxIncluded datatype property. The Delivery Method to which this charge applies is specified using the appliesToDeliveryMethod object property. The region or regions to which this charge applies is specified using the eligibleRegions datatype property, which uses ISO 3166-1 and ISO 3166-2 codes. If the price can only be given as a range, use hasMaxCurrencyValue and hasMinCurrencyValue for the upper and lower bounds. Important: When querying for the price, always use hasMaxCurrencyValue and hasMinCurrencyValue.
In domain of - gr:appliesToDeliveryMethod
A Delivery Method is a standardized procedure for transferring the Product or Service Instance 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 Business Entity (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
In range of - gr:availableDeliveryMethods gr:appliesToDeliveryMethod
A private parcel service as the delivery mode available for a certain offering. Examples: UPS, DHL
A Location of Sales or Service Provisioning is a location from which the specified Business Function on the particular Product or Service Instance is being offered by the Business Entity. Large enterprises often maintain multiple branches from which the delivery or fulfilment can be provided. In this case, the location of the main office of the Business Entity does not state from where a customer can actually get the Offering. In the case of a chain store, it may be all the actual shops. For mail order companies, the location will usually be the headquarter of the BusinessEntity. Locations of Sales or Service Provisioning are characterized by an address or 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 should be attached to a Location of Sales or Service Provisioning. 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 hasGlobalLocationNumber property is provided for linking to respective identifiers for business locations.
In range of - gr:availableAtOrFrom
This is the superclass for all classes that are placeholders for n-ary relations, which OWL cannot represent.
An Offering represents the public, not necessarily binding, not necessarily exclusive, announcement by a Business Entity to provide a certain Business Function for a certain Product or Service Instance 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 offered (sales, rental, ...), and a set of commercial properties. It can either refer to a clearly specified instance (Product or Service Instance) or to a set of anonymous instances of a given type (existentially quantified Product or Service Instances, 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 the following sections 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
In domain of - gr:hasPriceSpecification gr:hasBusinessFunction gr:hasWarrantyPromise gr:eligibleCustomerTypes gr:availableDeliveryMethods gr:includesObject gr:acceptedPaymentMethods gr:availableAtOrFrom
In range of - gr:offers
This is a conceptual entity that holds together all aspects of the n-ary relation OpeningHoursSpecification, which defines the opening hours for a given DayOfWeek for a given LocationOfSalesOrServiceProvisioning.
In domain of - gr:hasOpeningHoursDayOfWeek gr:opens gr:closes
A Payment Charge Specification is a conceptual entity that specifies the additional costs asked for settling the payment after accepting a given Offering using a particular Payment Method. A Payment 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 Payment Method, and (3) a whether this charge includes local sales taxes, namely VAT. An Offering may be linked to multiple Payment Charge Specifications that specify alternative charges for various Payment Methods. Examples: Payment by VISA or Mastercard costs a fee of 3 Euros including VAT, Payment by bank transfer in advance is free of charge. The total amount of this surcharge is specified as a float value of hasCurrencyValue. The currency is specified via the hasCurrency datatype property. Whether the price includes VAT or not is indicated by the ValueAddedTaxIncluded datatype property. The Payment Method to which this charge applies is specified using the appliesToPaymentMethod object property. If the price can only be given as a range, use hasMaxCurrencyValue and hasMinCurrencyValue for the upper and lower bounds. Important: When querying for the price, always use hasMaxCurrencyValue and hasMinCurrencyValue.
In domain of - gr:appliesToPaymentMethod
A Payment Method is a standardized procedure for transferring the monetary amount for a purchase. Payment Methods are characterized by the legal and technical structures used, and by the organization or group carrying out the transaction. It is mostly used for specifying the types of payment accepted by a Business Entity. Examples: Visa, Mastercard, Diners, Cash, Bank transfer in advance
In range of - gr:appliesToPaymentMethod gr:acceptedPaymentMethods
The subclass of Payment Method represents all variants and brands of credit cards as a standardized procedure for transferring the monetary amount for a purchase. It is mostly used for specifying the types of payment accepted by a Business Entity. Examples: VISA, MasterCard, American Express
The superclass of all price specifications.
In domain of - gr:hasEligibleQuantity gr:hasCurrencyValue gr:hasMinCurrencyValue gr:hasCurrency gr:valueAddedTaxIncluded gr:hasMaxCurrencyValue
In range of - gr:hasPriceSpecification
The superclass of all classes describing products or services types, either by nature or purpose. Examples for such subclasses are "TV set", "vacuum cleaner", etc. All eClassOWL "gen" classes are subclasses of this class. An instance of this class can be either an actual product or service or a placeholder instance for unknown instances of a mass-produces commodity. Since eClassOWL and other large products and services ontologies are used for both describing product and services instances and product and service makes and models, this top-level concept is the union of (1) Actual Product or Service Instances, (2) Product or Service Models, and (3) ProductOrServiceSomeInstances Placeholders. The latter are "dummy" instances representing anonymous productst or services instances (i.e. such that are said to exist but not actually being exposed on the Web). See the GoodRelations Technical Report for more details on this. Examples: a) MyCellphone123, i.e. my personal, tangible cell phone b) Siemens1234, i.e. the Siemens cell phone make and model 123 c) dummyCellPhone123 as a placeholder for actual instances of a certain kind of cellphones.
In domain of - gr:isConsumableFor gr:isAccessoryOrSparePartFor gr:quantitativeProductOrServiceProperty gr:qualitativeProductOrServiceProperty gr:isSimilarTo gr:datatypeProductOrServiceProperty gr:description
In range of - gr:isConsumableFor gr:isAccessoryOrSparePartFor gr:isSimilarTo gr:typeOfGood
From the ontological perspective, a Product or Service Model is an intangible entity that specifies some characteristics of a group of similar, usually mass-produced Products. In case of mass-produces Products, there exists a relation hasMakeAndModel between the Products and Services Instance and the Product or Service Model. However, since eClassOWL and other products and services ontologies don't support this important disctinction, Product or Service Models are a subclass of Product or Service in GoodRelations. Examples: Ford T, Volkswagen Golf, Sony Ericsson W123 cellphone
In range of - gr:hasMakeAndModel
A placeholder instance for unknown instances of a mass-produces commodity. This is used as a computationally cheap workaround for such instances that are not individually exposed on the Web but just stated to exist (i.e., which are existentially quantified). Example: An instance of this class can represent an anonymous set of green Siemens1234 phones. It is different from the ProductOrServiceModel Siemens1234, since this refers to the make and model, and it is different from a particular instance of this make and mode (e.g. my individual phone) since the latter can be sold only once. Siemens1234, i.e. the Siemens cell phone make and model 123 as a placeholder for all actual instances.
A Qualitative Value is an entity that represents the state of a certain qualitative Product or Service Property. Qualitative Values are either Literal Values or Enumerative Values. Literal values are represented just as literals with respective datatype properties. For all other enumerative values, instances of this class are being created. An instance of this class represents a qualitative value for an object property. This is the superclass of all enumerated values in eClassOWL. Examples: the color "green", the power cord plug type "US" Note: Currently. neither value sets nor ordinal relations between values are supported. This can be implemented when needed by importing and refining GoodRelations.
In range of - gr:qualitativeProductOrServiceProperty
A Quantitative Value is a numerical interval that represents the range of a certain quantitative Product or Service Property in terms of the lower and upper bounds for one particular Product Or Service. It is to be interpreted in combination with the respective Unit Of Measurement. Most quantitative values are intervals even if they are in practice often treated as a single point. An instance of this class is an actual value for a quantitative property of a product. This instance is usually characterized by a minimal value, a maximal value, and a unit of measurement. This class is a work-around caused by the fact that OWL does only support binary relations, and that datatype ranges cannot be easily handled in OWL. Example: a weight between 10 and 25 kilogramms, a length between 10 and 15 milimeters
In domain of - gr:hasMinValue gr:hasMaxValue
In range of - gr:quantitativeProductOrServiceProperty gr:hasEligibleQuantity
An instance of this class is an actual float value for a quantitative property of a product. This instance is usually characterized by a minimal value, a maximal value, and a unit of measurement. This class is a work-around caused by the fact that OWL does only support binary relations, and that datatype ranges cannot be easily handled in OWL. Examples: The intervals "between 10.0 and 25.4 kilogramms" or "10.2 and 15.5 milimeters"
In domain of - gr:hasMinValueFloat gr:hasMaxValueFloat
An instance of this class is an actual integer value for a quantitative property of a product. This instance is usually characterized by a minimal value, a maximal value, and a unit of measurement. This class is a work-around caused by the fact that OWL does only support binary relations, and that datatype ranges cannot be easily handled in OWL. Example: A seating capacity between 1 and 8 persons Note: Users must keep in mind that ranges in here mean that ALL possible values in this interval are covered. (Sometimes, the actual commitment may be less than that: we rent cars from 2 - 12 seats does often not really mean that they have cars with 2,3,4,...12 seats.). Someone renting two types of rowing boats, one that fits for 1 or 2 people, and another that must be operated by 4 people cannot claim to rent boats with a seating capacity between 1 and 4 people. He or she is renting two boat types for 1-2 and 4.
In domain of - gr:hasMinValueInteger gr:hasMaxValueInteger
This is a conceptual entity that holds together all aspects of the quaternary relation includesTypeOfGood, namely the Quantity, the Unit of Measurement, the Product or Service, and the Offering to which this belongs. Note: The link between Offering and TypeAndQuantityNode is represented by the object property includesObject. The Unit of Measurement is attached using the hasUnitOfMeasurement datatype property. The quantity is specified using the datatype property amountOfThisGood (float). The specification of the item included is represented by the object property typeOfGood. Example: An offering may consists of 100g Butter and 1 kg of potatoes, or 1 cellphone and 2 headsets.
In domain of - gr:typeOfGood gr:amountOfThisGood
In range of - gr:includesObject
A Price Specification is a conceptual entity that specifies the price asked for a given Offering by the respective Business Entity. An Offering may be linked to multiple Price Specifications that specify alternative prices for non-overlapping sets of conditions (e.g. quantities or sales regions). A Price Specification is characterized by (1) the lower and upper limits and the Unit of Measurement of the eligible quantity, (2) by a monetary amount per unit of the Product or Service Instance in the given Unit of Measurement specified as a literal value of type float in combination with a Currency, and (3) a whether this prices includes local sales taxes, namely VAT. Example: The price, including VAT, for 1 kg of a given material is 5 Euros per kg for 0 - 5 kg and 4 Euros for quantities above 5 kg Note: Due to the complexity of pricing scenarios in various industries, it may be necessary to create extensions of this fundamental model of Price Specifications. Such can be done easily by importing and refining the GoodRelations ontology. A specification of the price per unit. This can be constrained to a certain quantity of products. More complex price specifications can be implemented as subclasses of this class The eligible quantity interval for a given price is specified using the object property hasEligibleQuantity, which points to an instance of Quantitative Value. The currency is specified using the hasCurrency datatype property, which point to an ISO 4217 currency code. The unit of measurement for the eligible quantity is specified using the hasUnitOfMeasurement datatype property, which points to a UN/CEFACT Common Code (3 characters). In most cases, the appropriate unit of measurement is the UN/CEFACT Common Code "C62" for "Unit or piece", since an Offering is defined by the quantity and unit of measurement of all items included (e.g. "1 kg of bananas plus a 2 kg of apples"). As long at the Offering consists of only one item, it is also possible to use an unit of measurement of choice for specifying the price per unit. For bundles, however, only "C62" for "Unit or piece" is a valid unit of measurement . Whether VAT and sales taxes are included in this price is specified using the datatype property valueAddedTaxIncluded (boolean). The price per unit of measurement is specified as a float value of hasCurrencyValue. The currency is specified via the hasCurrency datatype property. Whether the price includes VAT or not is indicated by the ValueAddedTaxIncluded datatype property. The boolean property isListPrice can be used to indicate that the price is a price recommendation only (i.e. a list price). If the price can only be given as a range, use hasMaxCurrencyValue and hasMinCurrencyValue for the upper and lower bounds. Important: When querying for the price, always use hasMaxCurrencyValue and hasMinCurrencyValue.
In domain of - gr:isListPrice
This is a conceptual entity that holds together all aspects of the n-ary relation hasWarrantyPromise. A Warranty Promise is an entity 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 the Product or Service Instance. A Warranty Promise is characterized by its temporal duration (usually starting with the date of purchase) and its Warranty Scope. The Warranty Scope represents the types of services provides (e.g. labor and parts, just parts) of the warranty included in an Offering. The actual services may be provided by the Business Entity making the Offering, by the manufacturer of the Product, or by a third party. There may be multiple Warranty Promises associated with a particular Offering, which differ in duration and scope (e.g. pick-up service during the first 12 months, just parts and labor for 36 months). Examples: 12 months parts and labor, 36 months parts
In domain of - gr:hasWarrantyScope gr:durationOfWarrantyInMonths
In range of - gr:hasWarrantyPromise
The Warranty Scope represents types of services that will be provided free of charge by the vendor or manufacturer in the case of a defect (e.g. labor and parts, just parts), as part of the warranty included in an Offering. The actual services may be provided by the Business Entity making the Offering, by the manufacturer of the Product, or by a third party. Examples: Parts and Labor, Parts
In range of - gr:hasWarrantyScope
The PaymentMethods accepted by the BusinessEntity for the given Offering.
Domain - gr:Offering
Range - gr:PaymentMethod
This property specifies the quantity of the goods included in the Offering via this TypeAndQuantityNode. The quantity is given in the UnitOfMeasurement attached to the TypeAndQuantityNode.
Domain - gr:TypeAndQuantityNode
Range - xsd:float
This property specifies the Delivery Method to which the Delivery Charge Specification applies.
Domain - gr:DeliveryChargeSpecification
Range - gr:DeliveryMethod
This property specifies the Payment Method to which the Payment Charge Specification applies.
Domain - gr:PaymentChargeSpecification
Range - gr:PaymentMethod
This states that a particular Offering is available at or from the given LocationOfSalesOrServiceProvisioning (e.g. shop or branch).
Domain - gr:Offering
This specifies the DeliveryMethods available for a given Offering.
Domain - gr:Offering
Range - gr:DeliveryMethod
The closing hour of the LocationOfSalesOrServiceProvisioning on the given DayOfWeek. If no time-zone suffix is included, the time is given in the local time valid at the 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 or 09:30:10+09:00
Domain - gr:OpeningHoursSpecification
Range - xsd:time
This property is the super property for all pure datatype properties that can be used to describe a product and services instance, or via the instances placeholders, of a set of instances of mass-produces commodities. In eClassOWL and other products and services ontologies, only such properties that are no quantitative properties and that have no predefined 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), and for boolean datatype properties.
Domain - gr:ProductOrService
A short textual description of the product or service. This can be easily extracted by search engines and other applications.
Domain - gr:ProductOrService
Range - xsd:string
This property specifies the duration of the WarrantyPromise in months.
Domain - gr:WarrantyPromise
Range - xsd:int
The types of customers (CustomerType) for which the given Offering is valid.
Domain - gr:Offering
Range - gr:BusinessEntityType
This property specifies the geo-political region or regions for which the offer 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!
Domain -
Range - xsd:string
This specifies the BusinessFunction of the Offering, i.e. whether the BusinessEntity is offering to sell, to lease, or to repair the particular type of product. Note: While it is possible that an entity is offering multiple types of business functions, this should usually not be stated by multiple statements attached to the same offering, since the UnitPriceSpecification for the varying BusinessFunctions will usually be very different.
Domain - gr:Offering
Range - gr:BusinessFunction
The currency for all prices in the PriceSpecification given using the ISO 4217 standard (3 characters).
Domain - gr:PriceSpecification
Range - xsd:string
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 PriceSpecification etc. For a Unit Price Specification, this is the price for one unit or bundle (as specified in the unit of measurement of the UnitPriceSpecification) of the respective ProductOrService. For a Delivery Charge Specification or a Payment Charge Specification, it is the price per delivery or payment. GoodRelations also supports giving price information as intervals only. If this is needed, use hasMaxCurrencyValue for the upper bound and hasMinCurrencyValue for the lower bound. Using hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x hasCurrencyValue y implies x hasMinCurrencyValue y, x hasMaxCurrencyValue y.
Domain - gr:PriceSpecification
Range - xsd:float
The Dan & Bradstreet DUNS number for identifying BusinessEntities. The Dan & Bradstreet DUNS is a ten digit number used to identify legal entities (but usually not branches or locations of logistical importance only).
Domain - gr:BusinessEntity
Range - xsd:string
The EAN UCC-13 code of the given ProductOrService. This code is now officially called GTIN-13 (Gobal 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.
Range - xsd:string
This specifies the interval and unit of measurement of ordering quantities for which the 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 hasEligible Quantity refers to units of this bundle. In other words, "C62" for "Units or pieces" is usually the appropriate UnitOfMeasurement.
Domain - gr:PriceSpecification
Range - gr:QuantitativeValue
The Global Trade Item Number (GTIN-14) of the given ProductOrService.
Range - xsd:string
The Global Location Number (GLN, sometimes also referred to as International Location Number or ILN) of the respective BusinessEntity or LocationOfSalesOrServiceProvisioning. The Global Location Number is a thirteen digit number used to identify parties and physical locations.
Domain -
Range - xsd:string
This states that an actual product instance (ActualProductOrServiceInstance) or a placeholder instance for multiple, unidentified such instances (represented by an instance of ProductOrServicesSomeInstancesPlaceholder) is one occurence of a particular Product or Service Model. Example: myFordT hasMakeAndModel FordT
Domain -
Range - gr:ProductOrServiceModel
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 PriceSpecification etc. For a Unit Price Specification, this is the UPPER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the UnitPriceSpecification) of the respective ProductOrService. For a Delivery Charge Specification or a Payment Charge Specification, it is the UPPER BOUND of the price per delivery or payment. Using hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x hasCurrencyValue y implies x hasMinCurrencyValue y, x hasMaxCurrencyValue y.
Domain - gr:PriceSpecification
Range - xsd:float
This property captures the upper limit of a QuantitativeValue instance.
Domain - gr:QuantitativeValue
This property captures the upper limit of a QuantitativeValueFloat instance.
Domain - gr:QuantitativeValueFloat
Range - xsd:float
This property captures the upper limit of a QuantitativeValueInteger instance.
Domain - gr:QuantitativeValueInteger
Range - xsd:int
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 PriceSpecification etc. For a Unit Price Specification, this is the LOWER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the UnitPriceSpecification) of the respective ProductOrService. For a Delivery Charge Specification or a Payment Charge Specification, it is the LOWER BOUND of the price per delivery or payment. Using hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x hasCurrencyValue y implies x hasMinCurrencyValue y, x hasMaxCurrencyValue y.
Domain - gr:PriceSpecification
Range - xsd:float
This property captures the lower limit of a QuantitativeValue instance.
Domain - gr:QuantitativeValue
This property captures the lower limit of a QuantitativeValueFloat instance.
Domain - gr:QuantitativeValueFloat
Range - xsd:float
This property captures the lower limit of a QuantitativeValueInteger instance.
Domain - gr:QuantitativeValueInteger
Range - xsd:int
This specifies the DayOfWeek to which the OpeningHoursSpecification is related.
Domain - gr:OpeningHoursSpecification
Range - gr:DayOfWeek
This links an Offering to one or more PriceSpecifications. There can be UnitPriceSpecifications, Payment Charge Specifications, and Delivery Charge Specifications. For each type multiple PriceSpecifications for the same Offering are possible, e.g. for different quantity ranges or for different currencies, or for different combinations of Delivery Method and target destination. List prices can be specified by setting the isListPrice property of the UnitPriceSpecification to "true".
Domain - gr:Offering
Range - gr:PriceSpecification
The unit of measurement for a QuantitativeValue, a Unit Price Specification, or a TypeAndQuantityNode given using the UN/CEFACT Common Code (3 characters).
Domain -
Range - xsd:string
This subproperty specifies that the upper and lower limit of the given 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 value and not an interval.
This subproperty specifies that the upper and lower limit of the given 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 value and not an interval.
This specified the WarrantyPromise made by the BusinessEntity for the given Offering.
Domain - gr:Offering
Range - gr:WarrantyPromise
This states the WarrantyScope of a given WarrantyPromise.
Domain - gr:WarrantyPromise
Range - gr:WarrantyScope
This object property links an Offering to one or multiple TypeAndQuantityNode that specify the components that are included in the respective offer.
Domain - gr:Offering
Range - gr:TypeAndQuantityNode
This states that a particular ProductOrService is an accessory or spare part for another ProductOrService.
Domain - gr:ProductOrService
Range - gr:ProductOrService
This states that a particular ProductOrService is a consumable for another ProductOrService.
Domain - gr:ProductOrService
Range - gr:ProductOrService
This boolean attribute indicates whether a UnitPriceSpecification is a list price (usually a vendor recommendation) or not. TRUE indicates it is a list price, FALSE indicates it is not. It is safe to assume by default that a UnitPriceSpecification that lacks this attributes is not list price.
Domain - gr:UnitPriceSpecification
Range - xsd:boolean
This states that a given ProductOrService is similar to another ProductOrService. Of course, this is a subjective statement; when interpreting it, the trust in the origin of the statement should be taken into account.
Domain - gr:ProductOrService
Range - gr:ProductOrService
This links a BusinessEntity to the respective Offering.
Domain - gr:BusinessEntity
Range - gr:Offering
The opening hour of the LocationOfSalesOrServiceProvisioning on the given DayOfWeek. If no time-zone suffix is included, the time is given in the local time valid at the 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 or 09:30:10+09:00
Domain - gr:OpeningHoursSpecification
Range - xsd:time
This is the super property of all qualitative properties for products and services. All eclassOWL properties for which QualitativeValue instances are specified are subproperties of this property.
Domain - gr:ProductOrService
Range - gr:QualitativeValue
This is the super property of all quantitative properties for products and services. All eclassOWL properties that specify quantitative characteristics, for which an interval is at least theoretically an appropriate value, are specified are subproperties of this property.
Domain - gr:ProductOrService
Range - gr:QuantitativeValue
This specifies the type of Product or Service the TypeAndQuantityNode is referring to.
Domain - gr:TypeAndQuantityNode
Range - gr:ProductOrService
This property specifies the beginning of the validity of the Offering. 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.
Domain -
Range - xsd:dateTime
This property specifies the end of the validity of the Offering. 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
Domain -
Range - xsd:dateTime
This property specifies whether the applicable value-added tax (VAT) is included in the prices of the PriceSpecification or not. It determines this feature for all types of PriceSpecifications, i.e. UnitPriceSpecifications, DeliveryChargeSpecifications, and PaymentChargeSpecifications. Note: This is a simple representation which may not properly reflect all details of local taxation.
Domain - gr:PriceSpecification
Range - xsd:boolean