GoodRelations is an Ontology for eCommerce, enabling web sites to publish details of their products and services in a way that is friendly to search engines, mobile applications and browser extensions.
GoodRelations is fully integrated with schema.org, the markup vocabulary backed by Google, Yahoo!, Bing/Microsoft and Yandex . All GoodRelations types and properties can be used directly from the schema.org namespace to expose more granular information for search engines and other clients, including delivery charges, quantity discounts, and product features. These details can be embedded into a web site using either HTML5 Microdata and RDFa. (Details of the integration of GoodRelations and schema.org are described in the article GoodRelations Fully Integrated with Schema.org)
How the GoodRelations ontology in RDFa syntax articulates your value proposition with Semantic Web technology is shown succinctly in the one page presentation GoodRelations Principles: E-Commerce Data as Page Payload.
This growing importance is also reflected in the popularity of the GoodRelations ontology on the web. The PingTheSemanticWeb namespace statistics list the GoodRelations namespace http://purl.org/goodrelations/v1# as second only to Friend of a Friend ( http://xmlns.com/foaf/0.1/ ) and in the type statistics the GoodRelations classes
GoodRelations is also recommended in the Unified Service Description Language XG Final Report as the vocabulary for modeling key business aspects of services in SOA settings, in particular Web Services.
The Linked Open Commerce's SPARQL endpoint (http://linkedopencommerce.com/sparql) contains the largest repository of GoodRelations data available on the web.
SPARQL Endpoints with GoodRelations data include:
PREFIX gr: <http://purl.org/goodrelations/v1#>
GoodRelations Compliant Software
GoodRelations Case Studies and Examples
Industry Classification Systems
Industry Classification Systems directly supported by GoodRelations include:
"Note that GoodRelations provides the gr:hasISICv4 and the gr:hasNAICS
properties for linking a gr:BusinessEntity to the proper ISIC/NAICS
category code for that company.
For a more precise description of the range of skills or products offered, one should use the regular gr:Offering pattern, though, because a one-dimensional industry classification is pretty much limited.
The International Standard of Industrial Classification of All Economic Activities (ISIC), Revision 4 code for a particular Business Entity. 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 North American Industry Classification System (NAICS) code for a particular Business Entity. 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 well-known "RDF Book Mashup" at http://www4.wiwiss.fu-berlin.de/bizer/bookmashup/ , a cornerstone of the Linked Data cloud and movement, is now exposing offer data using GoodRelations.
Ontologies for Products and Services
GoodRelations provides an upper ontology for types of products and services, and their features but is not an ontology for products and services. See Vocabularies for Products and Services Types and Features for a list of products and services ontologies.
GoodRelations compliant Domain Ontologies for Vertical Industries include:
eClassOWL defines 30,000+ classes for products and 5,000+ properties .
Vehicle Sales Ontology
FreeClassOWL - Ontology of Construction and Building Materials
a) ClassOWL 5.1.4 Products and Services Ontology
* OWL or HTML: http://www.ebusiness-unibw.org/ontologies/eclass/5.1.4/
(Warning: The file is very large - 38.3 MB for RDF/XML and 71.8 MB
* ZIP: OWL+HTML:
(eClassOWL 5.1.4 ontology and documentation, compressed - OWL +
HTML, zip, 4.7 MB):
c) Consumer Electronics Ontology (CEO)
(add .html / .owl if content negotiation should fail)