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] vso:feature, dpPedia and productontology

Martin Hepp martin.hepp at ebusiness-unibw.org
Mon Jan 28 10:07:20 CET 2013

Hi Francois-Paul:

On Jan 26, 2013, at 7:59 AM, François-Paul Servant wrote:

> In http://www.productontology.org/#faq
> I read:
> "DBpedia URIs cannot be used for modeling the type of real-world objects, in particular in the context of the GoodRelations ontology, because
> - they lack a suitable semantics for being used as classes, and
> - they are not valid OWL DL."
> In http://www.heppnetz.de/ontologies/vso/ns#feature
> the comment about vso:feature says:
> "Use DBPedia resources to indicate the features, if possible."
> I don't see what they should be a difference between a product and a feature of a product wrt their modeling
> If it is bad to say that foo:mySolderingIron rdf:type dbPedia:Soldering_iron
> it must also be bad to say that
> foo:myRegulatedAirConditioner rdf:type dbPedia:Air_conditioner

The answer is simply, yet it may not obvious, so thanks for the question:

You can (and should) use suitable DBPedia URIs for *instances* (individuals), but not for *classes* (types).

All examples in the Vehicle Sales Ontology (http://purl.org/vso/ns) and other GoodRelations extensions say that you should rather use DBPedia URIs for instances of predefined value *types*.


VSO defines


as the range for 


You can use


as a value for that property, in statements like

foo:myCar vso:bodyStyle <http://dbpedia.org/resource/Convertible> .

An OWL/RDF reasoner will infer then that

<http://dbpedia.org/resource/Convertible> rdf:type vso:BodyStyleValue

which is perfectly fine.

Hope that helps!


> Best,
> fps
> _______________________________________________
> goodrelations mailing list
> goodrelations at ebusiness-unibw.org
> http://ebusiness-unibw.org/cgi-bin/mailman/listinfo/goodrelations

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 Main Page: http://purl.org/goodrelations/

More information about the goodrelations mailing list