GoodRelationsQuickstart

From Wiki of the E-Business and Web Science Research Group

GoodRelations is a standardized vocabulary for product, price, and company data that can be embedded into existing static and dynamic Web pages.

Project Main Page Vocabulary Documentation Developer's Wiki GoodRelations Cookbook

GoodRelations Quickstart Guide

GoodRelations is a standardized vocabulary for product, price, and company data that can (1) be embedded into existing static and dynamic Web pages and that (2) can be processed by other computers.

If you add GoodRelations to your Web pages, you improve the visibility of your offers in the latest generation of search engines and recommender systems, and other novel applications.

Traditional Search Engine Optimization (SEO) tries to put you on top of all search results, but quite clearly, that can work only for one company. GoodRelations puts you on top of Web visibility for people who are looking for exactly your products or services.

Companies using GoodRelations include:

BestBuy,
Yahoo,
O'Reilly,
OpenLink Software,

and many more.

1 How Can I Use GoodRelations?
2 HTML Patterns for Rich Markup
3 Connecting the Dots – Linking the Data
- 3.1 Linking from Offers / Products to the Company
- 3.2 Linking from the Company to its Stores / Shops / Restaurants.
4 Updating the XHTML/HTML Page Header
5 Further Information

How Can I Use GoodRelations?

It's incredibly simple:

Customize and insert the patterns of additional HTML markup into your Web pages.
Add links between the patterns.
Modify the header information of the respective pages.

That's it. You will be all set.

HTML Patterns for Rich Markup

In this section, you find ready-to-use snippets for adding rich meta-data about a company, a store, or a product / offer to existing Web pages.

Company

Insert the additional HTML markup given below anywhere in the body section of your main Web page and fill the following elements with your correct data:

"Hepp's Bagel Bakery Ltd. ": The official legal name of your company or business.
"Germany": Your country.
"Munich": The city in which your business is registered.
"85577": The zip code of your residence.
"1234 Main Street": The street and number of your residence
"+1 408 970-6104": The phone number, including the international prefix.
"http://www.hepps-bagels.com/image_or_logo.png": The Web address (URL) of a logo or image.

 
<!-- in RDFa 1.1, you can use the abbreviation: <div profile="http://www.heppnetz.de/grprofile/"> -->
<div xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" 
	xmlns="http://www.w3.org/1999/xhtml" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:gr="http://purl.org/goodrelations/v1#" 
	xmlns:vcard="http://www.w3.org/2006/vcard/ns#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
 
   <div about="#company" typeof="gr:BusinessEntity">
      <div property="gr:legalName" content="Hepp's Bagel Bakery Ltd. "></div>
      <div rel="vcard:adr">
         <div typeof="vcard:Address">
            <div property="vcard:country-name" content="Germany"></div>
            <div property="vcard:locality" content="Munich"></div>
            <div property="vcard:postal-code" content="85577"></div>
            <div property="vcard:street-address" content="1234 Main Street"></div>
         </div>
      </div>
      <div property="vcard:tel" content="+1 408 970-6104"></div>
      <div rel="foaf:depiction" resource="http://www.hepps-bagels.com/image_or_logo.png"></div>
      <div rel="foaf:page" resource=""></div>
   </div>
</div>

Statistics:

16 lines of markup
less than 1000 characters of extra code

Shop, Restaurant, or Store, and Opening Hours

Insert the additional HTML markup given below anywhere in the body section of the Web page describing your shop(s), restaurant(s), or store(s), and fill the following elements with your correct data:

"Pizzeria La Mamma": The name of the store or location.
"Germany": Your country.
"Munich": The city for the location.
"85577": The zip code for the location.
"1234 Main Street": The street and number for the location.
"+33 408 970-6104": A phone number, including the international prefix.
"http://www.pizza-la-mamma.com/image_or_logo.png": The Web address (URL) of a logo or image.
"48.08" / "11.64": The geo position of the store as longitude and latitude (Unknown? Find it here!).
"08:00:00" / "18:00:00": The opening hours for Monday through Friday.
"08:30:00" / "14:00:00": The opening hours for Saturday.

If you have multiple shops, but just one page, simply copy the snippet multiple times and replace all ocurrences of the three elements

"#store", "#mon_fri", and "#sat"

inside the same snippet by

"#store1", "#mon_fri1", and "#sat1"
"#store2", "#mon_fri2", and "#sat2"
"#store3", "#mon_fri3", and "#sat3"

etc.

 
<!-- in RDFa 1.1, you can use the abbreviation: <div profile="http://www.heppnetz.de/grprofile/"> -->
<div xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
     xmlns="http://www.w3.org/1999/xhtml" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:gr="http://purl.org/goodrelations/v1#" 
     xmlns:vcard="http://www.w3.org/2006/vcard/ns#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
 
  <div about="#store" typeof="gr:LocationOfSalesOrServiceProvisioning">
    <div property="rdfs:label" content="Pizzeria La Mamma"></div>
    <div rel="vcard:adr">
      <div typeof="vcard:Address">
        <div property="vcard:country-name" content="Germany"></div>
        <div property="vcard:locality" content="Munich"></div>
        <div property="vcard:postal-code" content="85577"></div>
        <div property="vcard:street-address" content="1234 Main Street"></div>
      </div>
    </div>
    <div property="vcard:tel" content="+33 408 970-6104"></div>
    <div rel="foaf:depiction" resource="http://www.pizza-la-mamma.com/image_or_logo.png"></div>
    <div rel="vcard:geo">
      <div>
        <div property="vcard:latitude" content="48.08" datatype="xsd:float"></div>
        <div property="vcard:longitude" content="11.64" datatype="xsd:float"></div>
      </div>
    </div>
    <div rel="gr:hasOpeningHoursSpecification">
      <div about="#mon_fri" typeof="gr:OpeningHoursSpecification">
        <div property="gr:opens" content="08:00:00" datatype="xsd:time"></div>
        <div property="gr:closes" content="18:00:00" datatype="xsd:time"></div>
        <div rel="gr:hasOpeningHoursDayOfWeek" resource="http://purl.org/goodrelations/v1#Friday"></div>
        <div rel="gr:hasOpeningHoursDayOfWeek" resource="http://purl.org/goodrelations/v1#Thursday"></div>
        <div rel="gr:hasOpeningHoursDayOfWeek" resource="http://purl.org/goodrelations/v1#Wednesday"></div>
        <div rel="gr:hasOpeningHoursDayOfWeek" resource="http://purl.org/goodrelations/v1#Tuesday"></div>
        <div rel="gr:hasOpeningHoursDayOfWeek" resource="http://purl.org/goodrelations/v1#Monday"></div>
      </div>
    </div>
    <div rel="gr:hasOpeningHoursSpecification">
      <div about="#sat" typeof="gr:OpeningHoursSpecification">
        <div property="gr:opens" content="08:30:00" datatype="xsd:time"></div>
        <div property="gr:closes" content="14:00:00" datatype="xsd:time"></div>
        <div rel="gr:hasOpeningHoursDayOfWeek" resource="http://purl.org/goodrelations/v1#Saturday"></div>
      </div>
    </div>
    <div rel="foaf:page" resource=""></div>
  </div>
</div>

Statistics:

41 lines of markup
less than 2,500 characters of extra code

Offer / Product

Insert the additional HTML markup given below anywhere in the body section of your Web page template for individual products, and fill the following elements with the correct data for the respective product:

"Canon Rebel T2i (EOS 550D) $899" : The name of the product.
"The Rebel T2i EOS 550D is Cannon's top-of-the-line ...": The long description of the product.
xml:lang="en": Replace "en" by the ISO 639-1 code for the language of the name or description if the text is not in English.
"013803123784": The EAN-13, 13-digit UPC, or 13-digit ISBN code for the product. This code is now officially called GTIN-13. 10-digit ISBNs and 12-digit UPC codes can be converted, see here for converting ISBNs. Converting 12-digit UPCs into GTIN13 is simpler, just add a preceeding zero.
That code is optional for GoodRelations, but highly recommended, since it increases the visibility of your items a lot.
"USD" and "899": The currency and price for the product (899 US$ in our example). Use 3-letter ISO 4217 codes for currencies, e.g. EUR for euro.

 
<!-- in RDFa 1.1, you can use the abbreviation: <div profile="http://www.heppnetz.de/grprofile/"> -->
<div xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
     xmlns="http://www.w3.org/1999/xhtml" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:gr="http://purl.org/goodrelations/v1#"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
 
  <div about="#offering" typeof="gr:Offering">
    <div property="rdfs:label" content="Canon Rebel T2i (EOS 550D) $899" xml:lang="en"></div>
    <div property="rdfs:comment" content="The Rebel T2i EOS 550D is Cannon's top-of-the-line consumer digital SLR camera.
It can shoot up to 18 megapixel resolution photos and features an ISO range of 100-6400. Now just $ 899 $" xml:lang="en"></div>
    <div rel="foaf:depiction" resource="http://a.img-dpreview.com/previews/CanonEOS550D/images/intro.jpg"></div>
    <div rel="gr:hasBusinessFunction" resource="http://purl.org/goodrelations/v1#Sell"></div>
    <div property="gr:hasEAN_UCC-13" content="013803123784" datatype="xsd:string"></div>
    <div rel="gr:hasPriceSpecification">
      <div typeof="gr:UnitPriceSpecification">
        <div property="gr:hasCurrency" content="USD" datatype="xsd:string"></div>
        <div property="gr:hasCurrencyValue" content="899" datatype="xsd:float"></div>
      </div>
    </div>
    <div rel="gr:acceptedPaymentMethods" resource="http://purl.org/goodrelations/v1#PayPal"></div>
    <div rel="gr:acceptedPaymentMethods" resource="http://purl.org/goodrelations/v1#MasterCard"></div>
    <div rel="foaf:page" resource="http://myshop.com/canon-rebel-t2i/"></div>
  </div>
</div>

Add additional or delete existing lines of the form

 
<div rel="gr:acceptedPaymentMethods" resource="http://purl.org/goodrelations/v1#PayPal"></div>

for indicating the accepted payment methods. The following payment methods are currently supported by GoodRelations:

If you have multiple products within the same Web page, simply copy the snippet multiple times and replace all ocurrences of the element

"#offer"

inside the same snippet by

"#offer1"
"#offer2"
"#offer3"

Statistics:

18 lines of markup
less than 1,500 characters of extra code

Connecting the Dots – Linking the Data

Once you have added the structured data to the Web page markup, you have to link them so that search engines and recommender system can find them. Two types of links are important:

Links from offers / products to the company.
Links from the company to its stores / restaurants.

Linking from Offers / Products to the Company

1. Find out the final main Web address (URL) under which the page with the company markup will be available.

Examples:

If there are multiple ways to access the page, use the shortest and most official one. Let's assume it is

http://www.hepps-bagels.com/

in our example.

Now add "#company" to that address, which gives us

http://www.hepps-bagels.com/#company

as the identifier for the company data.

2. Insert the following additional line to the data markup for each product / offer page:

 
<div rev="gr:offers" resource="http://www.hepps-bagels.com/#company"></div>

Instead of http://www.hepps-bagels.com/#company, use the correct URL determined in step 1.

This additional line must follow directly after the element

 
<div about="#offering" typeof="gr:Offering">

So the correct markup in our example would be

 
<div about="#offering" typeof="gr:Offering">
    <div rev="gr:offers" resource="http://www.hepps-bagels.com/#company"></div>
    <div property="rdfs:label" content="Canon Rebel T2i (EOS 550D) $899" xml:lang="en"></div>
...

Linking from the Company to its Stores / Shops / Restaurants.

1. Determine the complete Web address (URL, including "#company") of the company as before. In our example, we use

http://www.hepps-bagels.com/#company

as the identifier for the company data.

2. Insert the following additional line to the data markup for each store page:

 
<div rev="gr:hasPOS" resource="http://www.hepps-bagels.com/#company"></div>

Instead of http://www.hepps-bagels.com/#company, use the correct URL determined in step 1.

This additional line must follow directly after the element

 
<div about="#store" typeof="gr:LocationOfSalesOrServiceProvisioning">

So the correct markup in our example would be

 
<div about="#store" typeof="gr:LocationOfSalesOrServiceProvisioning">
    <div rev="gr:hasPOS" resource="http://www.hepps-bagels.com/#company"></div>
    <div property="rdfs:label" content="Pizzeria La Mamma"></div>
...

Updating the XHTML/HTML Page Header

Add a "xmlns" attribute with the value "http://www.w3.org/1999/xhtml" and a "version" attribute with the value "HTML+RDFa 1.0" to the <html> element of your document:

 
<html xmlns="http://www.w3.org/1999/xhtml" version="HTML+RDFa 1.0" xml:lang="en">

This is enough for basic access to your rich meta-data.

Your data is, however, much more visible and useful if your page is compliant with the XHTML 1.0 strict specification. If you meet that requirement, you should instead update the page header as follows:

1. Change the DOCTYPE in the header to "XHTML+RDFa"

 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">

2. Add a "xmlns" attribute with the value "http://www.w3.org/1999/xhtml" and a "version" attribute with the value "XHTML+RDFa 1.0" to the <html> element of your document:

 
<html xmlns="http://www.w3.org/1999/xhtml" version="XHTML+RDFa 1.0" xml:lang="en">

3. Check that the <head> element includes the proper content type and encoding for XHTML:

 
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
    <title>Your page title blabla...</title>
</head>

Further Information

Remarks

We use vcard:tel with plain literals in those examples, since this is the form expected by Yahoo. This is in part contradicting the official VCard Ontology specification but maximizes the visibility of your data. Should Google or any other major application require the official VCard modeling, we will change the recipe accordingly. Currently, Google recommends its own vocabulary and "tel" property.

Contact

Univ.-Prof. Dr. Martin Hepp

E-Business and Web Science Research Group
Chair of General Management and E-Business
Universität der Bundeswehr München
Werner-Heisenberg-Weg 39
D-85579 Neubiberg, Germany Phone: +49 89 6004-4217
eMail: mhepp(at)computer.org (preferred mode of communication)
Web: http://www.heppnetz.de/
Web: http://www.unibw.de/ebusiness/

Retrieved from "http://www.ebusiness-unibw.org/wiki/GoodRelationsQuickstart"

GoodRelationsQuickstart

From Wiki of the E-Business and Web Science Research Group

Contents

How Can I Use GoodRelations?

HTML Patterns for Rich Markup

Company

Shop, Restaurant, or Store, and Opening Hours

Offer / Product

Connecting the Dots – Linking the Data

Linking from Offers / Products to the Company

Linking from the Company to its Stores / Shops / Restaurants.

Updating the XHTML/HTML Page Header

Further Information

Remarks

Links

Contact

Views

Personal tools

Navigation

Search

Toolbox