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 feedback

Martin Hepp (UniBW) martin.hepp at ebusiness-unibw.org
Thu Apr 9 08:20:10 CEST 2009

Hi Holger,
thanks for your feedback!

Holger Knublauch wrote:
> Martin,
> I am currently playing a bit with GoodRelations. I noticed a few details
> 1) You may want to define an explicit namespace prefix instead of the 
> default namespace (or at least in addition to it). This will make life 
> easier for ontologies that import your file.
Thanks - we will implement that in the next service update, top be 
expected after Easter.
> 2) I didn't see rdfs:labels, e.g. for the Days of the week. This would 
> also allow you to make international versions of that ontology.
Thanks - we will implement that in the next service update, top be 
expected after Easter.
> 3) There is a p1 namespace prefix defined (for the assert namespace), 
> and also the protege namespace does not seem to be used.
Will look into that and likely fix it in the next service release.
> 4) (A matter of taste) - some property names start with "has" but 
> others don't, e.g. acceptedPaymentMethods versus hasEligibleQuantity - 
> are those really different? I would just drop the "has" everywhere.
> 5) Likewise some property names end with 's' to indicate plural, but 
> for example includesObject can have multiple values.
As for 4) and 5), we cannot easily fix that without breaking existing 
data and applications, so I am hesitant to c


> Regards
> Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: martin_hepp.vcf
Type: text/x-vcard
Size: 308 bytes
Desc: not available
URL: <http://ebusiness-unibw.org/pipermail/goodrelations/attachments/20090409/b0a267d4/attachment.vcf>

More information about the goodrelations mailing list