Instance této třídy je abstraktní informační entitou o veřejné zakázce. Obsahuje všechny aktuálně známé informace o zakázce, tj. např. o zadavateli veřejné zakázky, službách či dodávkách, které ve veřejné zakázce nakupuje, a o podmínkách nákupu (termíny, očekávané ceny, atd.). Dále obsahuje informace o nabídkách od zájemců o zakázku a o vybrané nabídce. Pokud již byla zakázka realizována, obsahuje i informace o skutečné ceně za realizaci apod.
An instance of this class is an abstract information entity about a public contract. It consists of all currently known information about a contract, e.g., a contracting authority, services or supplies which shall be purchased, and contract conditions (e.g., important dates, expected price, etc.). It also informs about tenders received from particular bidders and about an accepted tender. If the contract has already been realized it also informs about an actual price of realization, etc.
Třída pro popis rámcové smlouvy
Class for decribing a framework agreement
Základní třída pro popis nabídky zájemce o zakázku
Basic class for decribing a tender submitted by a bidder
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.
Třída pro popis kombinace kritérií pro posuzování nabídek zájemců o zakázku
Class for description of criteria combination used for tender evaluation
Třída pro popis jednoho kritéria a jeho váhy.
Class for description of one criterion and its weight
Opening of tenders submitted for a public contract
Otevírání nabídek zaslaných pro veřejnou zakázku
Vlastnost pro datum přidělení zakázky dodavateli. Kardinalita 0..1
Property for date of contract award to a bidder. Cardinality 0..1
Vlastnost pro kontaktní údaje na místo nebo osobu určenou pro komunikaci s veřejností a zájemci o zakázku. Pokud je kontaktních míst či osob více (např. pro vyzvednutí dokumentace k veřejné zakázce), je pro každou uveden samostatný kontakt. Kardinalita 0..*
Property for contact information for a person or place responsible for a communication with the public and bidders. If there are more contact places or persons (e.g., for collecting documentation to the public contract), there is a separate contact for each person. Cardinality 0..*
Kategorie veřejné zakázky specifikuje základní zaměření veřejné zakázky na stavební práce, dodávku zboží nebo služby. Lze použít pouze jeden z předdefinovaných SKOS konceptů. Kardinalita 0..1
Kind of a public contract specifies a basic focus of the contract on works, supplies or services. Only a predefined SKOS concept can be used. Cardinality 0..1
Druh řízení veřejné zakázky specifikuje proceduru, podle které je zakázka uveřejňována a podle které je vybírán dodavatel. Lze použít pouze jednu z předdefinovaných hodnot. Kardinalita 0..1
Type of procedure of a public contract specifies a procedure which is applied to publish information about the contract and choose a supplier. Only a predefined value can be used. Cardinality 0..1
Instituce, která vypisuje veřejnou zakázku, přijímá nabídky a vybírá vhodného dodavatele na základě pravidel stanovených zakázkou. Kardinalita 0..1
Institution which issues a public contract, receives tenders to the contract and chooses a suitable supplier on the base of the conditions given by the contract. Cardinality 0..1
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.
Položka poptávaná v rámci veřejné zakázky. Může být kombinací několika produktů či služeb, což lze vyjádřit pomocí vlastností gr:Offering. Kardinalita 0..*
An item inquired by a public contract. It can be a combination of several products or services which can be expressed using properties of gr:Offering. Cardinality 0..*
CPV (Common Procurement Vocabulary) kód popisující hlavní předmět veřejné zakázky. Kardinalita 0..1
CPV (Common Procurement Vocabulary) code describing the main object of a public contract. Cardinality 0..1
CPV (Common Procurement Vocabulary) kód popisující doplňující předmět veřejné zakázky. Kardinalita 0..*
CPV (Common Procurement Vocabulary) code describing an additional object of a public contract. Cardinality 0..*
Místo, kde dojde k dodání produktu nebo plnění služby nasmlouvané ve veřejné zakázce. Kardinalita 0..*
Place of delivery of contracted product or performance of contracted service. Cardinality 0..*
Abstraktní vlastnost pro cenu přiřazené k veřejné zakázce
Abstract property for price of public contract
The superclass of all price specifications.
Vlastnost pro cenu zadávací dokumentace k zakázce. Kardinalita 0..1
Property for price of documentation for public contract. Cardinality 0..1
Vlastnost pro odhadovanou cenu veřejné zakázky. Může jít o přesně odhadovanou částku nebo interval. Kardinalita 0..1
Property for estimated price of public contract. It can be an exact estimation or an interval. Cardinality 0..1
Vlastnost pro lhůtu pro doručení nabídek nebo přijetí žádostí o účast. Kardinalita 0..1
Property for time limit for receipt of tenders or requests to participate. Cardinality 0..1
Vlastnost pro lhůtu pro vyžádání dokumentace k veřejné zakázce. Kardinalita 0..1
Property for time limit for receipt of requests for documentation. Cardinality 0..1
Vlastnost pro dobu trvání zakázky. Doba trvání může být uvedena ve dnech, měsících, letech apod. Kardinalita 0..1
Property for duration of contract. The duration may be described in days, months, years, etc. Cardinality 0..1
Vlastnost pro vyjádření minimální doby, po kterou je uchazeč svou nabídkou vázán. Doba trvání může být uvedena ve dnech, měsících, letech apod. Kardinalita 0..1
Property for expressing minimum time frame during which the tenderer must maintain the tender. The duration may be described in days, months, years, etc. Cardinality 0..1
Vlastnost pro datum začátku realizace zakázky, které je uvedené ve smlouvě. Kardinalita 0..1
Property for start date of public contract realization coming from the contract's text. Cardinality 0..1
Vlastnost pro očekávané datum konce realizace zakázky. Kardinalita 0..1
Property for estimated end date of public contract realization. Cardinality 0..1
Vlastnost pro skutečné datum konce realizace zakázky. Kardinalita 0..1
Property for actual end date of public contract's realization. Cardinality 0..1
Vlastnost pro nastavení kombinace kritérií pro hodnocení nabídek zájemců o zakázku. Kardinalita 0..1
Property for criteria combination for tender evaluation. Cardinality 0..1
Vlastnost pro specifikaci části zakázky. Zakázku rozděluje na části zadavatel, pokud je zakázka přiliš velká. Zájemci o zakázku podávají nabídky na každou část odděleně a pro každou část zakázky je vybrán samostatný dodavatel. Pro samotnou zakázku nabídky nejsou podávány. Kardinalita 0..*
Property for specifying contract lot. When contract is too big, it is split to lots by contracting authority. Bidders then tender each lot separately. For each lot the authority awards a separate tender. The contract itself has no tenders. Cardinality 0..*
Vlastnost pro rámcovou smlouvu, na jejímž základě byla veřejná zakázka zadána. Kardinalita 0..1
Property for a framework agreement on which base a public contract was issued. Cardinality 0..1
Vlastnost pro počet obdržených nabídek. Kardinalita 0..1
Property for number of tenders received. Cardinality 0..1
Vlastnost pro nabídku zájemce o zakázku. Kardinalita 0..*
Property for a tender submitted by a bidder. Cardinality 0..*
Vlastnost pro vítěznou nabídku zájemce o zakázku. Kardinalita 0..1
Property for awarded tender submitted by a bidder. Cardinality 0..1
Vlastnost pro dotaci použitou pro zakázku. Kardinalita 0..*
Property for used tender subsidy. Cardinality 0..*
Vlastnost pro cenu napsanou na smlouvě s dodavatelem. Kardinalita 0..1
Property for a price stated on the contract with the supplier. Cardinality 0..1
Vlastnost pro skutečnou cenu zaplacenou za zakázku. Kardinalita 0..1
Property for actual price of the public contract. Cardinality 0..1
Vlastnost pro připojení ostatních příloh. Zadávací dokumentaci připojte pomocí pc:specification, smlouvu pomocí pc:agreement. Kardinalita 0..*
Property for attachment of other documents. For attachment of contract specification use pc:specification. For attachment of contract agreement use pc:agreement. Cardinality 0..*
Vlastnost pro připojení dokumentů obsahujících zadávací dokumentaci veřejné zakázky. Kardinalita 0..*
Property for attachment of documents containing the contract specification. Cardinality 0..*
Vlastnost pro připojení dokumentů obsahujících smlouvy na veřejnou zakázku uzavřené mezi zadavatelem a dodavatelem. Kardinalita 0..*
Property for attachment of documents containing the agreement between supplier and contractor. Cardinality 0..*
Vlastnost pro nastavení jednoho kritéria pro hodnocení nabídek zájemců o zakázku. Kardinalita 0..*
Property for setting a criterion for tender evaluation. Cardinality 0..*
Očekávaný počet účastníků rámcové smlouvy. Kardinalita 0..1
Expected number of operators of framework agreement. Cardinality 0..1
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. 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. Compatibility with schema.org: This class is a subclass of http://schema.org/Quantity.
Vlastnost pro internetovou adresu profilové stránky zadavatele veřejných zakázek (URL).
Property for the internet address of the profile of contracting authority (URL).
Vlastnost pro druh zadavatele. Lze použít pouze jeden z předdefinovaných SKOS konceptů. Kardinalita 0..1
Property for a kind of a contracting authority. Only a predefined SKOS concept can be used. Cardinality 0..1
Vlastnost pro hlavní aktivitu zadavatele. Lze použít pouze jeden z předdefinovaných SKOS konceptů. Kardinalita 0..1
Property for main activity of contracting authority. Only a predefined SKOS concept can be used. Cardinality 0..1
Vlastnost pro cenu nabídnutou zájemcem o zakázku. Kardinalita 0..1
Property for price offered by supplier. Cardinality 0..1
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.
Vlastnost pro zájemce o zakázku podávajícího nabídku. Kardinalita 0..1
Property for bidder submitting the tender. Cardinality 0..1
Public contract, for which tenders are opened
Veřejná zakázka, pro níž jsou otevírány nabídky
Vlastnost pro připojení kritéria, které je váženo. Kardinalita 0..1
Property for attaching criterion that is weighted. Cardinality 0..1
Vlastnost pro specifikaci váhy kritéria pro hodnocení nabídky. Kardinalita 0..1
Property for criterion weight for tender evaluation. Cardinality 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.
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/
This states that a particular gr:Offering is available at or from the given gr:Location (e.g. shop or branch).
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.
The Tax / Fiscal ID of the gr:BusinessEntity, e.g. the TIN in the US or the CIF/NIF in Spain. It is usually assigned by the country of residence
This links a gr:BusinessEntity to gr:Offering nodes that describe what the business entity is interested in (i.e., the buy side). If you want to express interest in offering something, use gr:offers instead. Note that this substitutes the former gr:BusinessFunction gr:Buy, which is now deprecated.
The gr:BusinessEntityType representing such agents that are purchasing the scope of products included in the gr: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.
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
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.
This class collates all the information about a gr:ProductOrService included in a bundle. If a gr:Offering contains just one item, you can directly link from the gr:Offering to the gr:ProductOrService using gr:includes. If the offering contains multiple items, use an instance of this class for each component to indicate the quantity, unit of measurement, and type of product, and link from the gr:Offering via gr:includesObject. Example: An offering may include of 100g of Butter and 1 kg of potatoes, or 1 cell phone and 2 headsets.
The serial number or any alphanumeric identifier of a particular product. Note that serial number are unique only for the same brand or the same model, so you cannot infer from two occurrences of the same serial number that the objects to which they are attached are identical. This property can also be attached to a gr:Offering in cases where the included products are not modeled in more detail.
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.
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.
The opening 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 or 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 17:00:00 - 23:59:59 for Saturday and 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.
This is a conceptual entity that holds together all information about the opening hours on a given day (gr:DayOfWeek).
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.
The legal name of the gr:BusinessEntity.
Delivery via the parcel service Federal Express.
A private parcel service as the delivery mode available for a certain offering. Examples: UPS, DHL
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
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. An instance of this class can be either an actual product or service (gr:Individual), a placeholder instance for unknown instances of a mass-produced commodity (gr:SomeItems), or a model / prototype specification (gr:ProductOrServiceModel). When in doubt, use gr:SomeItems. Examples: a) MyCellphone123, i.e. my personal, tangible cell phone (gr:Individual) b) Siemens1234, i.e. the Siemens cell phone make and model 1234 (gr:ProductOrServiceModel) c) dummyCellPhone123 as a placeholder for actual instances of a certain kind of cell phones (gr:SomeItems) Note: Your first choice for specializations of gr:ProductOrService should be http://www.productontology.org. Compatibility with schema.org: This class is (approximately) equivalent to http://schema.org/Product.
The Value-added Tax ID of the gr:BusinessEntity. See http://en.wikipedia.org/wiki/Value_added_tax_identification_number for details.
Delivery via the parcel service DHL.
Delivery via regular mail service (private or public postal services).
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
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"
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.
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.
The types of customers (gr:BusinessEntityType) for which the given gr:Offering is valid.
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.
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. This element is mostly used for specifying the types of payment accepted by a gr:BusinessEntity. Examples: VISA, MasterCard, Diners, cash, or bank transfer in advance.
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.
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. Examples: The intervals "between 10.0 and 25.4 kilogramms" or "10.2 and 15.5 milimeters". Compatibility with schema.org: This class is a subclass of http://schema.org/Quantity.
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 gr:ProductOrServiceModel Siemens1234, since this refers to the make and model, and it is different from a particular instance of this make and model (e.g. my individual phone) since the latter can be sold only once. Note: This class is the new, shorter form of the former gr:ProductOrServicesSomeInstancesPlaceholder. Compatibility with schema.org: This class is (approximately) a subclass of http://schema.org/Product.
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.
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.
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.
This property links a gr:Location to a gr:OpeningHoursSpecification.
This property specifies the end of the validity of the gr:Offering, gr:PriceSpecification, gr:License, or gr:OpeningHoursSpecification. 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 1: If multiple contradicting instances of a gr:Offering, gr:PriceSpecification, or gr:OpeningHoursSpecification exist, it is a good heuristics to assume that 1. Information with validity information for the respective period of time ranks higher than information without validity information. 2. Among conflicting nodes both having validity information, the one with the shorter validity span ranks higher. Note 2: For Google, attaching a gr:validThrough statement to a gr:UnitPriceSpecification is mandatory.
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.
Payment by credit or debit cards issued by the American Express network.
The subclass of gr:PaymentMethod represents all variants and brands of credit or debit 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 gr:Business Entity. Examples: VISA, MasterCard, or American Express.
This property specifies the gr:PaymentMethod to which the gr:PaymentChargeSpecification applies.
A payment charge specification is a conceptual entity that specifies the additional costs asked for settling the payment after accepting a given gr:Offering using a particular gr:PaymentMethod. 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. A gr: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 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 datatype property. The gr:PaymentMethod to which this charge applies is specified using the gr:appliesToPaymentMethod object property. 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.
This states that a particular gr:ProductOrService is a consumable for another product or service.
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.
This property captures the upper limit of a gr:QuantitativeValueFloat instance.
This property captures the upper limit of a gr:QuantitativeValue instance.
This property captures the lower limit of a gr:QuantitativeValueFloat instance.
This property captures the lower limit of a gr:QuantitativeValue instance.
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.
Payment via the PaySwarm distributed micropayment service.
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.
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).
This property specifies the duration of the gr:WarrantyPromise in months.
This is a conceptual entity that holds together all aspects of the n-ary relation gr: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 gr:ProductOrService. A warranty promise is characterized by its temporal duration (usually starting with the date of purchase) and its gr:WarrantyScope. The warranty scope represents the types of services provided (e.g. labor and parts, just parts) of the warranty included in an gr:Offering. The actual services may be provided by the gr:BusinessEntity 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
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.
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
A product or service model is a intangible entity that specifies some characteristics of a group of similar, usually mass-produced products, in the sense of a prototype. In case of mass-produced products, there exists a relation gr:hasMakeAndModel between the actual product or service (gr:Individual or gr:SomeItems) and the prototype (gr:ProductOrServiceModel). GoodRelations treats product or service models as "prototypes" instead of a completely separate kind of entities, because this allows using the same domain-specific properties (e.g. gr:weight) for describing makes and models and for describing actual products. Examples: Ford T, Volkswagen Golf, Sony Ericsson W123 cell phone Note: An actual product or service (gr:Individual) by default shares the features of its model (e.g. the weight). However, this requires non-standard reasoning. See http://wiki.goodrelations-vocabulary.org/Axioms for respective rule sets. Compatibility with schema.org: This class is (approximately) a subclass of http://schema.org/Product.
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).
In case of a defect or malfunction, the buying party has the right to request from the selling gr: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 gr:WarrantyPromise.
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 gr:Offering. The actual services may be provided by the gr:BusinessEntity making the offering, by the manufacturer of the product, or by a third party. Examples: Parts and Labor, Parts
Payment by credit or debit cards issued by the JCB network.
The depth of the product. Typical unit code(s): CMT for centimeters, INH for inches
A quantitative value is a numerical interval that represents the range of a certain gr:quantitativeProductOrServiceProperty in terms of the lower and upper bounds for a particular gr:ProductOrService. 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 value. Example: a weight between 10 and 25 kilogramms, a length between 10 and 15 milimeters. Compatibility with schema.org: This class is equivalent to http://schema.org/Quantity.
This is the super property of all quantitative properties for products and services. All properties in product or service ontologies that specify quantitative characteristics, for which an interval is at least theoretically an appropriate value, are subproperties of this property.
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.
This property captures the lower limit of a gr:QuantitativeValueInteger instance.
This property captures the upper limit of a gr:QuantitativeValueInteger instance.
This object property links a gr:ProductOrService to the gr:BusinessEntity that produces it. Mostly used with gr:ProductOrServiceModel.
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.
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)
The day of the week, used to specify to which day the opening hours of a gr:OpeningHoursSpecification refer. Examples: Monday, Tuesday, Wednesday,...
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.
A qualitative value is a predefined value for a product characteristic. Examples: the color "green" or the power cord plug type "US"; the garment sizes "S", "M", "L", and "XL". Note: Value sets are supported by creating subclasses of this class. Ordinal relations between values (gr:greater, gr:lesser, ...) are provided directly by GoodRelations. Compatibility with schema.org: This class is equivalent to http://schema.org/Enumeration.
A unit price specification is a conceptual entity that specifies the price asked for a given gr:Offering by the respective gr: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) or with differing validity periods. 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, 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 gr:hasEligibleQuantity, which points to an instance of gr:QuantitativeValue. The currency is specified using the gr:hasCurrency property, which points to an ISO 4217 currency code. The unit of measurement for the eligible quantity is specified using the gr: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 a gr: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. You can assume that the price is given per unit or piece if there is no gr:hasUnitOfMeasurement property attached to the price. Whether VAT and sales taxes are included in this price is specified using the property gr:valueAddedTaxIncluded (xsd:boolean). The price per unit of measurement 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 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 gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue for the upper and lower bounds. Important: When querying for the price, always use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue. Note 1: 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. Note 2: For Google, attaching a gr:validThrough statement to a gr:UnitPriceSpecification is mandatory.
Payment by cash upon delivery or pickup.
Payment by credit or debit cards issued by the Diner's Club network.
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.
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.
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.
The color of the product.
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.
This states that a particular gr:ProductOrService is an accessory or spare part for another product or service.
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).
This specifies the gr:ProductOrService that the gr:TypeAndQuantityNode is referring to.
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).
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.
This is the super property of all qualitative properties for products and services. All properties in product or service ontologies for which gr:QualitativeValue instances are specified are subproperties of this property.
This specifies the gr:DeliveryMethod or methods available for a given gr:Offering.
This gr:BusinessFunction indicates that the gr:BusinessEntity offers (or seeks) the evaluation of the chances for repairing, and, if positive, repair of the specified gr:ProductOrService. Repairing means actions that restore the originally intended function of a product that suffers from outage or malfunction.
Payment via the Google Checkout payment service.
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.
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.
This gr:BusinessFunction indicates that the gr:BusinessEntity offers to permanently transfer all property rights on the specified gr:ProductOrService.
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.
This specifies the brand or brands (gr:Brand) associated with a gr:ProductOrService, or the brand or brands maintained by a gr:BusinessEntity.
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.
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.
This attribute can be used to distinguish multiple different price specifications for the same gr:Offering. It supersedes the former gr: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.
Delivery of the goods by using a fleet of vehicles either owned and operated or subcontracted by the gr:BusinessEntity.
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!
Payment by credit or debit cards issued by the VISA network.
The superclass of properties that link a gr:QuantitativeValue or a gr:QualitativeValue to a second gr:QuantitativeValue or a gr:QualitativeValue that provides additional information on the original value. A good modeling practice is to define specializations of this property (e.g. foo:referenceTemperature) for your particular domain.
This property specifies the beginning of the validity of the gr:Offering, gr:PriceSpecification, gr:License, or gr:OpeningHoursSpecification. 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: If multiple contradicting instances of a gr:Offering, gr:PriceSpecification, or gr:OpeningHoursSpecification exist, it is a good heuristics to assume that 1. Information with validity information for the respective period of time ranks higher than information without validity information. 2. Among conflicting nodes both having validity information, the one with the shorter validity span ranks higher.
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 via the parcel service UPS.
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.
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.
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.
This specifies the gr:WarrantyPromise made by the gr:BusinessEntity for the given gr:Offering.
The Global Trade Item Number (GTIN-14) of the given gr:ProductOrService or gr:Offering.
This gr:BusinessFunction indicates that the gr:BusinessEntity offers (or seeks) the temporary right to use the specified gr:ProductOrService.
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.
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.
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.
The currency for all prices in the gr:PriceSpecification given using the ISO 4217 standard (3 characters).
This gr:BusinessFunction indicates that the gr:BusinessEntity is in general interested in purchasing the specified gr:ProductOrService. DEPRECATED. Use gr:seeks instead.
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.
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 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 gr:WarrantyPromise.
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.
The URI of a SOAP or REST Web Service from which additional information about the gr:BusinessEntity, gr:Offering, gr:PriceSpecification, or gr:ProductOrService, or any other element, can be obtained. The recommended range is xsd:anyURI 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 this gr:relatedWebService property.
A placeholder for all official public holidays at the gr:Location. 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.
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.
This property specifies whether the applicable value-added tax (VAT) is included in the price of the gr:PriceSpecification or not. Note: This is a simple representation which may not properly reflect all details of local taxation.
The gr:PaymentMethod or methods accepted by the gr:BusinessEntity for the given gr:Offering.
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.
This states the gr:WarrantyScope of a given gr:WarrantyPromise.
The weight of the gr:ProductOrService. Typical unit code(s): GRM for gram, KGM for kilogram, LBR for pound
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.
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.
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.
This ordering relation for qualitative values indicates that the subject is equal to the object.
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.
The height of the product. Typical unit code(s): CMT for centimeters, INH for inches
The width of the gr:ProductOrService. Typical unit code(s): CMT for centimeters, INH for inches
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.
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.
Delivery by an unspecified air, sea, or ground freight carrier or cargo company.
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.
Payment via the PayPal payment service.
This ordering relation for gr:QualitativeValue pairs indicates that the subject is not equal to the object.
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)
The gr:BusinessEntityType representing such agents that are part of the adminstration or owned by the public.
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.
Payment by credit or debit cards issued by the Discover network.
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.
This gr:BusinessFunction indicates that the gr:BusinessEntity 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 gr:ProvideService is to be used with such goods that are services, while gr:Maintain and gr: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 the service car maintenance" or "maintain cars".
This property specifies the gr:DeliveryMethod to which the gr:DeliveryChargeSpecification applies.
This property indicates that a particular person or business owns a particular product. It can be used to expose the products in one's posession in order to empower recommender systems to suggest matching offers. Note that the product must be an instance of the class gr:Individual. This property can also be safely applied to foaf:Agent instances.
Payment by credit or debit cards issued by the MasterCard network.
The unit of measurement for a gr:QuantitativeValue, a gr:UnitPriceSpecification, or a gr:TypeAndQuantityNode given using the UN/CEFACT Common Code (3 characters).
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.
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.
Wednesday as a day of the week.
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.
Thursday as a day of the week.
Friday as a day of the week.
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.
Tuesday as a day of the week.
Monday as a day of the week.
This ordering relation for gr:QualitativeValue pairs indicates that the subject is lesser than the object.
This ordering relation for qualitative values indicates that the subject is greater than the object.
DEPRECATED - This class is superseded by gr:Location. Replace all occurrences of gr:LocationOfSalesOrServiceProvisioning by gr:Location, if possible.
DEPRECATED - This class is superseded by gr:SomeItems. Replace all occurrences of gr:ProductOrServicesSomeInstancesPlaceholder by gr:SomeItems, if possible.
This property indicates that the subject is a previous, often discontinued variant of the gr:ProductOrServiceModel used as the object. Example: Golf III predecessorOf Golf IV This relation is transitive.
This property indicates that the subject is a newer, often updated or improved variant of the gr:ProductOrServiceModel used as the object. Example: Golf III successorOf Golf II This relation is transitive.
Sunday as a day of the week.
Saturday as a day of the week.
DEPRECATED - This class is superseded by gr:Individual. Replace all occurrences of gr:ActualProductOrServiceInstance by gr:Individual, if possible.
This ordering relation for qualitative values indicates that the subject is greater than or equal to the object.
This ordering relation for gr:QualitativeValue pairs indicates that the subject is lesser than or equal to the object.
Veřejná zakázka
Public contract
Rámcová smlouva
Framework agreement
Nabídka
Tender
Offering
Kombinace kritérií pro hodnocení dodaných nabídek
Combination of contract award criteria
Vážené kritérium pro udělení zakázky
Contract award weighted criterion
Tenders' opening
Otevírání nabídek
Datum přidělení zakázky
Date of contract award
Kontaktní osoba
Contact person
Kategorie zakázky
Contract kind
Druh řízení
Procedure type
Zadavatel
Contracting authority
Business entity
Hlavní předmět zakázky
Main object of contract
Další předmět zakázky
Additional object of contract
Místo uskutečnění zakázky
Place of contract's realization
Cena
Price
Price specification
Cena zadávací dokumentace k zakázce
Price of documentation for public contract
Odhadovaná cena zakázky
Exact estimated price
Lhůta pro doručení nabídek nebo přijetí žádostí o účast
Time-limit for receipt of tenders or requests to participate
Lhůta pro vyžádání dokumentace k veřejné zakázce
Time-limit for receipt of requests for documentation
Doba trvání zakázky
Duration of contract
Doba trvání nabídky
Duration of tender validity
Datum začátku realizace zakázky
Start date of contract
Očekávané datum konce realizace zakázky
Estimated end date of contract
Skutečné datum konce realizace zakázky
Actual end date of contract realization
Kombinace kritérií pro hodnocení nabídek zájemců o zakázku.
Criteria combination for tender evaluation.
Část zakázky
Contract lot
Na základě rámcové smlouvy
On the base of a framework agreement
Počet obdržených nabídek
Number of tenders received
Vybraná nabídka
Awarded tender
Dotace použitá pro zakázku
Subsidy supplemented for contract
Smluvní cena
Agreed price
Skutečná cena po realizaci zakázky
Actual price after contract realization
Příloha k zakázce
Contract attachment
Zadávací dokumentace zakázky
Contract specification
Smlouva na veřejnou zakázku
Contract agreement
Kritérium pro zadání zakázky.
Criterion for contract award.
Critères d'attribution
Vergabekriterien
Očekávaný počet účastníků rámcové smlouvy
Expected number of operators of framework agreement
Quantitative value integer
Profilová stránka zadavatele
Profile web site of contracting authority
Druh zadavatele
Kind of contracting authority
Hlavní aktivita
Main activity
Nabídnutá cena v nabídce
Offered price in tender
has price specification (0..*)
Zájemce o zakázku
Tender bidder
Vážené kritérium
Weighted criterion
Váha kritéria pro výběr dodavatele zakázky
Contract award criterion weight
availability starts (0..1)
GoodRelations Ontology
available at or from (0..*)
Location
Tax ID (0..1)
seeks (0..*)
Reseller (business entity type)
Business entity type
amount of this good (1..1)
Type and quantity node
serial number (0..*)
Individual
has ISIC v4 (0..*)
opens (1..1)
Opening hours specification
has NAICS (0..*)
legal name (0..1)
Federal Express (delivery method)
Delivery mode parcel service
has MPN (0..*)
Product or service
VAT ID (0..1)
DHL (delivery method)
Delivery mode mail (delivery method)
Delivery method
category (0..*)
has POS (0..*)
availability ends (0..1)
eligible customer types (0..*)
By invoice (payment method)
Payment method
has inventory level (0..1)
Quantitative value float
Some items
is similar to (0..*)
Maintain (business function)
Business function
has opening hours specification (0..*)
valid through (0..1)
License
American Express (payment method)
Payment method credit card
applies to payment method (1..*)
Payment charge specification
is consumable for (0..*)
has value float (0..1)
has max value float (1..1)
has max value (0..1)
has min value float (1..1)
has min value (0..1)
closes (1..1)
PaySwarm (payment method)
advance booking requirement (0..1)
eligible transaction volume (0..1)
duration of warranty in months (0..1)
Warranty promise
has Global Location Number (0..1)
is variant of (0..1)
Product or service model
has GTIN-8 (0..*)
Parts and labor / pick up (warranty scope)
Warranty scope
JCB (payment method)
depth (0..1)
Quantitative value
quantitative product or service property (0..*)
has value integer (0..1)
has min value integer (1..1)
has max value integer (1..1)
has manufacturer (0..1)
description (0..1)
Brand
Day of week
Delivery charge specification
Qualitative value
Unit price specification
Cash (payment method)
Diners Club (payment method)
Dispose (business function)
billing increment (0..1)
is list price (DEPRECATED)
color (0..1)
datatype product or service property (0..*)
is accessory or spare part for (0..*)
has DUNS (0..1)
type of good (1..1)
delivery lead time (0..1)
has Stock Keeping Unit (0..*)
qualitative product or service property (0..*)
available delivery methods (0..*)
Repair (business function)
Google Checkout (payment method)
includes (0..1)
Business (business entity type)
Sell (business function)
has value (0..1)
has brand (0..*)
By bank transfer in advance (payment method)
has opening hours day of week (1..*)
price type (0..1)
Delivery mode own fleet (delivery method)
eligible regions (0..*)
VISA (payment method)
value reference (0..*)
valid from (0..1)
Delivery mode direct download (delivery method)
UPS (delivery method)
Construction / installation (business function)
Check in advance (payment method)
name (0..1)
has warranty promise (0..*)
has GTIN-14 (0..*)
Lease Out (business function)
has currency value (0..1)
has min currency value (1..1)
has max currency value (1..1)
has currency (1..1)
Buy (business function, DEPRECATED)
has make and model (0..1)
Parts and labor / bring-in (warranty scope)
Enduser (business entity type)
related Web Service (0..*)
Public holidays (day of week)
display position (0..1)
value added tax included (0..1)
accepted payment methods (0..*)
has business function (1..*)
has warranty scope (0..1)
weight (0..1)
includes object (0..*)
has EAN/UCC-13 (0..*)
N-ary relations (DEPRECATED)
equal (0..*)
Labor / bring-in (warranty scope)
height (0..1)
width (0..1)
COD (payment method)
has eligible quantity (0..1)
Delivery mode freight (delivery method)
eligible duration (0..1)
PayPal (payment method)
non equal (0..*)
condition (0..1)
Public institution (business entity type)
Delivery mode pick up (delivery method)
Discover (payment method)
Direct debit (payment method)
Provide service (business function)
applies to delivery method (0..*)
owns (0..*)
MasterCard (payment method)
has unit of measurement (1..1)
offers (0..*)
add-on (0..*)
Wednesday (day of week)
has next (0..1)
Thursday (day of week)
Friday (day of week)
has previous (0..1)
Tuesday (day of week)
Monday (day of week)
lesser (0..*)
greater (0..*)
Location of sales or service provisioning (DEPRECATED)
Product or services some instances placeholder (DEPRECATED)
predecessor of (0..*)
successor of (0..*)
Sunday (day of week)
Saturday (day of week)
Actual product or service instance (DEPRECATED)
greater or equal (0..*)
lesser or equal (0..*)
Public Contracts Ontology
Ontologie pro veřejné zakázky
Ontologie pro veřejné zakázky poskytuje vyjadřovací prostředky pro popis zakázek zadávaných institucemi veřejné správy.
Public Contracts Ontology offers a means of expression for describing public contracts in the public sector.
Use for labelling states of public contracts (instances of pc:Contract). The domain is pc:Contract.
Use for attaching plain text description of public contracts (instances of pc:Contract). The domain is pc:Contract.
Use for attaching identifiers (instances of adms:Identifier) to contracting authorities and bidders (instances of gr:BusinessEntity). The property should be used for official numbers assigned to public contracts in national public procurement systems, reference numbers of public contracts assigned by their contracting authorities, notice number in EU TED, etc. The domain is a union of gr:BusinessEntity and pc:Contract.
Use for date and time, when tenders are opened. The domain is pc:TendersOpening. Cardinality 0..1
Používejte pro datum a čas otevření nabídek. Definičním oborem je pc:TendersOpening. Kardinalita 0..1
Use for location, where tenders are opened. The domain is pc:TendersOpening. Cardinality 0..1
Místo, kde dojde k otevření obálek s nabídkami pro veřejnou zakázku. Definičním oborem je pc:TendersOpening. Kardinalita 0..1
The GoodRelations Vocabulary for Semantic Web-based E-Commerce
E-Commerce, E-Business, GoodRelations, Microdata, Ontology, Semantic SEO, RDFa, Linked Data, RDF, Semantic Web, Recommender Systems
Martin Hepp
V 1.0, Release 2011-10-01
The GoodRelations ontology is available under the Creative Commons Attribution 3.0 Unported license; see http://creativecommons.org/licenses/by/3.0/. In a nutshell, you are free to copy, distribute and transmit the work; to remix/adapt the work (e.g. to import the ontology and create specializations of its elements), as long as you attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Proper Attribution: Simply include the statement "This work is based on the GoodRelations ontology, developed by Martin Hepp" and link back to http://purl.org/goodrelations/
Work on the GoodRelations ontology and related research and development has been partly supported by the Austrian BMVIT/FFG under the FIT-IT Semantic Systems project myOntology (grant no. 812515/9284), by a Young Researcher's Grant (Nachwuchsfoerderung 2005-2006) from the Leopold-Franzens-Universitaet Innsbruck, by the European Commission under the project SUPER (FP6-026850), and by the German Federal Ministry of Research (BMBF) by a grant under the KMU Innovativ program as part of the Intelligent Match project (FKZ 01IS10022B). The