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] GoodRelations: Site relaunch, service update

Martin Hepp martin.hepp at ebusiness-unibw.org
Thu Jun 9 00:44:22 CEST 2011

Dear all:

We just deployed the new GoodRelations Web site and a GoodRelations Service Update at


Please refresh your caches and repositories.

The relaunch is a major step to a more developer-friendly environment. Here is a summary of the changes:

- Social Web functionality for each individual GoodRelations element - you can easily share and refer friends to each and every element directly
- Tight integration with popular developer forums, like Quora, StackOverflow, answers.semanticweb.com, so that questions related to parts of GoodRelations can be shared with relevant experts with ease
- Cross-references to external resources related to an element (e.g. a link to Wikipedia pages when a property value is from a standard code)
- Examples in Turtle, RDF/XML, RDFa, and SPARQL for each element (this is currently work in progress)
- New screen-design and Wiki

The Service Update 2011-04-01 also brings a few modifications to the vocabulary. They are implemented in a backwards-compatible fashion and approved by Yahoo and Google, so their parsers will tolerate the old and the new versions.

gr:ActualProductOrServiceInstance             --> gr:Individual
gr:ProductOrServicesSomeInstancesPlaceholder  --> gr:SomeItems
gr:LocationOfSalesOrServiceProvisioning       --> gr:Location

For new data and applications, please use the new, shorter elements. Old data does not have to be updated, as long as the consuming client  or triplestore can handle owl:equivalentClass. If you touch your modeling patterns or queries, it would be better to move to the new identifiers now.

Also, we added a few new elements:

* Additional payment options: gr:JCB, gr:PaySwarm, and gr:GoogleCheckout
* gr:GTIN-8 property for GTIN-8 (EAN/UCC-8) codes
* gr:displayPosition (owl:AnnotationProperty) so that a preferred display position for elements and data can be represented
* gr:Brand class and gr:hasBrand property for relating gr:ProductOrService and gr:BusinessEntity nodes to a brand name or brand identity

For the full Changelog, see 


A huge thanks to my team members Andreas Radinger, Alex Stolz, Uwe Stoll, and László Török for their hard work on this!

Best wishes

Martin Hepp

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen shot 2011-06-09 at 12.30.30 AM.png
Type: image/png
Size: 117336 bytes
Desc: not available
URL: <http://ebusiness-unibw.org/pipermail/goodrelations/attachments/20110609/2c4f33cb/attachment.png>
-------------- next part --------------

More information about the goodrelations mailing list