Ontology Description

Base URI of GoodRelations: http://purl.org/goodrelations/v1#.

For examples and background information, please see the GoodRelations Primer.

GoodRelations Ontology ( rdf:type owl:Ontology )

Classes

    • rdfs:label -- ActualProductOrServiceInstance
    • rdfs:comment -- 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 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: In many cases, product or service instances are not explicitly exposed on the Web but only claimed to exist (i.e. existentially quantified). For a detailed discussion and practical solutions, see section 3.3.3 of the GoodRelations Technical Report.
    • rdfs:subClassOf -- #ProductOrService
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  5. DayOfWeek ( rdf:type owl:Class )
    • rdfs:label -- DeliveryChargeSpecification
    • rdfs:comment -- A Delivery Charge Specification is a conceptual entity that specifies the additional costs asked for the 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) 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 charge is specified as a float value of the hasCurrencyValue property. 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.
    • rdfs:subClassOf -- #PriceSpecification
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  11. Offering ( rdf:type owl:Class )
    • rdfs:label -- PaymentChargeSpecification
    • rdfs:comment -- 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 the hasCurrencyValue property. 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.
    • rdfs:subClassOf -- #PriceSpecification
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- ProductOrServiceModel
    • rdfs:comment -- 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-produced Products, there exists a relation hasMakeAndModel between the Products and Services Instance and the Product or Service Model. 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. This allows using the same properties for (e.g. "hasWeight") for product models and actual products. Examples: Ford T, Volkswagen Golf, Sony Ericsson W123 cell phone Note: An Actual Product or Service Instance of which is known via a relation hasMakeAndModel that it is of a certain Product Or Service Model should by default share the features of this model (e.g. the weight). However, this requires non-standard reasoning. See the GoodRelations Wiki at http://www.ebusiness-unibw.org/wiki/GoodRelations for respective rule sets.
    • rdfs:subClassOf -- #ProductOrService
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- ProductOrServicesSomeInstancesPlaceholder
    • rdfs:comment -- A placeholder instance for unknown instances of a mass-produced commodity. This is used as a computationally cheap work-around 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.
    • rdfs:subClassOf -- #ProductOrService
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- QuantitativeValueFloat
    • rdfs:comment -- 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".
    • rdfs:subClassOf -- #QuantitativeValue
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- QuantitativeValueInteger
    • rdfs:comment -- 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 sell cars from 2 - 12 seats" does often not really mean that they have cars with 2,3,4,...12 seats.). Someone renting out 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 offering two boat types for 1-2 and 4 persons.
    • rdfs:subClassOf -- #QuantitativeValue
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- TypeAndQuantityNode
    • rdfs:comment -- 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 consist of 100g Butter and 1 kg of potatoes, or 1 cell phone and 2 headsets.
    • rdfs:subClassOf -- #N-Ary-Relations
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- UnitPriceSpecification
    • rdfs:comment -- A Unit 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 Unit Price Specifications that specify alternative prices for non-overlapping sets of conditions (e.g. quantities or sales regions). A Unit 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) 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. 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 points to an ISO 4217 currency code. The unit of measurement for the eligible quantity is specified using the hasUnitOfMeasurement datatype property, which points to an 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 the hasCurrencyValue property. The currency is specified via the hasCurrency datatype property. Whether the price includes VAT or not is indicated by the valueAddedTaxIncluded datatype property. The property priceType can be used to indicate that the price is a retail 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. 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.
    • rdfs:subClassOf -- #PriceSpecification
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- WarrantyPromise
    • rdfs:comment -- 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 provided (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
    • rdfs:subClassOf -- #N-Ary-Relations
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1

Properties

Annotation Properties

    • rdfs:label -- relatedWebService (0..*)
    • rdfs:comment -- The URI of a SOAP or REST Web service from which additional information about the BusinessEntity, Offering, PriceSpecification, or ProductOrService instance can be gained. The recommended domain is Offering, PriceSpecification, or ProductOrService. The recommended range is rdf:resource, i.e., the URI of a SOAP or REST Web service. In principle, any existing or upcoming vocabulary for Web Services can be used in combination with GoodRelations, because the association between (a) the service description and (b) the GoodRelations description can be found via the Web Service URI value used with the gr:relatedWebService property.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1

Object Properties

    • rdfs:label -- hasEligibleQuantity (0..1)
    • rdfs:comment -- This specifies the interval and unit of measurement of ordering quantities for which the Price Specification 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 hasEligibleQuantity refers to units of this bundle. In other words, "C62" for "Units or pieces" is usually the appropriate Unit Of Measurement.
    • rdfs:domain -- #PriceSpecification
    • rdfs:range -- #QuantitativeValue
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- hasPriceSpecification (0..*)
    • rdfs:comment -- This links an Offering to one or more Price Specifications. There can be Unit Price Specifications, Payment Charge Specifications, and Delivery Charge Specifications. For each type multiple specifications 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. Recommended retail prices etc. can be marked by the priceType property of the Unit Price Specification to "true".
    • rdfs:domain -- #Offering
    • rdfs:range -- #PriceSpecification
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- isVariantOf (0..1)
    • rdfs:comment -- This states that a particular Product Or Service Model instance is a variant of another Product Or Service Model. It is pretty safe to infer that the variant inherits all quantitativeProductOrServiceProperties, qualitativeProductOrServiceProperties, and datatypeProductOrServiceProperties that are defined for the first Product Or Service Model. Example: foo:Red_Ford_T_Model gr:isVariantOf foo:Ford_T_Model
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1

Datatype Properties

    • rdfs:label -- datatypeProductOrServiceProperty (0..*)
    • rdfs:comment -- 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-produced commodities. In products and services ontologies, only such properties that are no quantitative properties and that have no predefined Qualitative Value 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.
    • rdfs:domain -- #ProductOrService
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- hasEAN_UCC-13 (0..*)
    • rdfs:comment -- The EAN·UCC-13 code of the given Product Or Service or 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.
    • rdfs:domain --
    • rdfs:range -- http://www.w3.org/2001/XMLSchema#string
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- hasMaxCurrencyValue (1..1)
    • rdfs:comment -- 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 Price Specification 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 Unit Price Specification) of the respective Product Or Service. 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.
    • rdfs:domain -- #PriceSpecification
    • rdfs:range -- http://www.w3.org/2001/XMLSchema#float
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- hasMinCurrencyValue (1..1)
    • rdfs:comment -- 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 Price Specification 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 Unit Price Specification) of the respective Product Or Service. 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.
    • rdfs:domain -- #PriceSpecification
    • rdfs:range -- http://www.w3.org/2001/XMLSchema#float
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- hasStockKeepingUnit (0..*)
    • rdfs:comment -- 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 hasStockKeepingUnit is the union of the classes Offering and Product Or Service. If attached to an 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 Product Or Service Model, the SKU should reflect the identifier / part number used by the official manufacturer of that part. 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 Business Entity, 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 Offering are concerned, you can also check that the offerings are being offered by the same Business Entity. Usually, the properties hasEAN_UCC-13 and hasGTIN-14 are much more reliable identifiers, because they are globally unique. See also http://en.wikipedia.org/wiki/Stock_Keeping_Unit.
    • rdfs:domain --
    • rdfs:range -- http://www.w3.org/2001/XMLSchema#string
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- priceType (0..1)
    • rdfs:comment -- This attribute can be used to distinguish multiple different Price Specifications for the same Product or Service. It supersedes the former isListPrice property. The following values are recommended: The absence of this property marks the actual sales price. SRP: "suggested retail price" - applicable for all sorts of a non-binding retail price recommendations, e.g. such published by the manufacturer or the distributor. This value replaces the former gr:isListPrice property. INVOICE: The invoice price, mostly used in the car industry - this is the price a dealer pays to the manufacturer, excluding rebates and charges.
    • rdfs:domain -- #UnitPriceSpecification
    • rdfs:range -- http://www.w3.org/2001/XMLSchema#string
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  33. description (DEPRECATED) ( rdf:type owl:DatatypeProperty )
  34. isListPrice (DEPRECATED) ( rdf:type owl:DatatypeProperty )

Individuals

    • rdfs:label -- Business (BusinessEntityType)
    • rdfs:comment -- The Business Entity Type 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.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  3. Buy ( rdf:type BusinessFunction )
    • rdfs:label -- ByBankTransferInAdvance (PaymentMethod)
    • rdfs:comment -- Payment by bank transfer in advance, i.e., the offering Business Entity 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.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  5. ByInvoice ( rdf:type PaymentMethod )
  6. COD ( rdf:type PaymentMethod )
  7. Cash ( rdf:type PaymentMethod )
    • rdfs:label -- CheckInAdvance (PaymentMethod)
    • rdfs:comment -- Payment by sending a check in advance, i.e., the offering Business Entity 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.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- DeliveryModeDirectDownload (DeliveryMethod)
    • rdfs:comment -- Delivery of the goods via direct download from the Internet, i.e., the offering Business Entity 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.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  17. DirectDebit ( rdf:type PaymentMethod )
  19. Dispose ( rdf:type BusinessFunction )
    • rdfs:label -- Dispose (BusinessFunction)
    • rdfs:comment -- This Business Function indicates that the Business Entity offers (or seeks) the acceptance of the specified Product for proper disposal, recycling, or any other kind of allowed usages, freeing the current owner from all rights and obligations of ownership.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  22. Friday ( rdf:type DayOfWeek )
    • rdfs:label -- Labor-BringIn (WarrantyScope)
    • rdfs:comment -- 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 Business Entity 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 Warranty Promise.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  24. LeaseOut ( rdf:type BusinessFunction )
  25. Maintain ( rdf:type BusinessFunction )
    • rdfs:label -- Maintain (BusinessFunction)
    • rdfs:comment -- This Business Function indicates that the Business Entity offers (or seeks) typical maintenance tasks for the specified Product. 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.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  27. Monday ( rdf:type DayOfWeek )
    • rdfs:label -- PartsAndLabor-BringIn (WarrantyScope)
    • rdfs:comment -- 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 Business Entity and will not be be charged for labor, parts, and materials needed to fix the problem. All those costs 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 Warranty Promise.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- PartsAndLabor-PickUp (WarrantyScope)
    • rdfs:comment -- In case of a defect or malfunction, the buying party has the right to request from the selling Business Entity to pick-up the good from its current location to a suitable service location, where the functionality of the good will be restored. All transportation, labor, parts, and materials needed to fix the problem 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 Warranty Promise.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  30. PayPal ( rdf:type PaymentMethod )
    • rdfs:label -- ProvideService (BusinessFunction)
    • rdfs:comment -- This Business Function indicates that the Business Entity offers (or seeks) the respective type of Service. Note: Maintain and Repair are also types of Services. However, products and services ontologies often provide classes for tangible products as well as for types of services. The business function Provide Service is to be used with such goods that are Services, while Maintain and Repair can be used with goods for which only the class of product exists in the ontology, but not the respective type of service. Example: Car maintenance could be expressed both as "Provide Service Car Maintenance" or "Maintain Cars". Since existing ontologies for goods often tangle products and services, it seems beneficial to include Provide Service as a business function.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  32. PublicHolidays ( rdf:type DayOfWeek )
    • rdfs:label -- PublicHolidays (DayOfWeek)
    • rdfs:comment -- A placeholder for all official public holidays at the Location Of Sales Or Service Provisioning. This allows specifying the opening hours on public holidays. If a given day is a public holiday, this specification supersedes the opening hours for the respective day of the week.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  34. Repair ( rdf:type BusinessFunction )
    • rdfs:label -- Repair (BusinessFunction)
    • rdfs:comment -- This Business Function indicates that the Business Entity offers (or seeks) the evaluation of the chances for repairing, and, if positive, repair of the specified Product. Repairing means actions that restore the originally intended function of a product that suffers from outage or malfunction.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
    • rdfs:label -- Reseller (BusinessEntityType)
    • rdfs:comment -- The Business Entity Type representing such agents that are purchasing the scope of products included in the Offering for resale on the market. Resellers are also businesses, i.e., they are officially registered with the public administration and strive for profits by their activities.
    • rdfs:isDefinedBy -- http://purl.org/goodrelations/v1
  36. Saturday ( rdf:type DayOfWeek )
  37. Sell ( rdf:type BusinessFunction )
  38. Sunday ( rdf:type DayOfWeek )
  39. Thursday ( rdf:type DayOfWeek )
  40. Tuesday ( rdf:type DayOfWeek )
  43. Wednesday ( rdf:type DayOfWeek )