Warning: This tool or project is no longer maintained and kept available only for archival purposes. Since GoodRelations and schema.org have evolved significantly in the past years, the current status available on this page is unlikely to function as expected. We take no responsibility for any damage caused by the use of this outdated work, to the extent legally possible.

Due to a lack of resources, we are unable to provide support for this project outside of consulting projects or sponsored research. Please contact us if you can contribute resources to update and enhance these resources.

GoodRelations - The Web Vocabulary for E-Commerce

This is the archive of the goodrelations dicussion list

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. This increases the visibility of your products and services in the latest generation of search engines, recommender systems, and other novel applications.

[goodrelations] Pitfall when creating GoodRelations data: HTML entity names in XML

Martin Hepp (UniBW) martin.hepp at ebusiness-unibw.org
Wed Mar 24 14:52:43 CET 2010

Dear all:

When you create GoodRelations data in RDF/XML syntax from existing Web 
applications, there is a potential pitfall:

Your data may contain HTML entity names that are fine for a browser but 
will result in invalid XML,
because not every HTML entity is also a valid XML entity.

Example: The text "£ 100" for 100 GBP may be encoded in HTML as "£ 

However, "£ 100" is not a valid literal value in RDF/XML 
documents, e.g. the following element breaks the XML code:

rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Coverage from 
£1,000 up to a limit of £5,000</rdfs:comment>

Luckily, it's relatively easy to avoid that problem:

Option 1: Use the numeric entity encoding (£) instead of the entity 
name (£). This will work for both HTML and RDF/XML.

Option 2: Use the UTF-8 character "£" directly instead of with HTML 
entity names.

You may have to update data in the source database in both cases.

This will mostly be a problem when augmenting older, HTML 4.x-based 
applications or data sources originating from those.

Thanks to Andreas Radinger for spotting this problem!

Best wishes

Martin Hepp

martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  hepp at ebusiness-unibw.org
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
         http://www.heppnetz.de/ (personal)
skype:   mfhepp 
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!

Project page:

Resources for developers:

Overview - http://www.heppnetz.de/projects/goodrelations/webcast/
How-to   - http://vimeo.com/7583816

Recipe for Yahoo SearchMonkey:

Talk at the Semantic Technology Conference 2009: 
"Semantic Web-based E-Commerce: The GoodRelations Ontology"

Overview article on Semantic Universe:

Tutorial materials:
ISWC 2009 Tutorial: The Web of Data for E-Commerce in Brief: A Hands-on Introduction to the GoodRelations Ontology, RDFa, and Yahoo! SearchMonkey 

More information about the goodrelations mailing list