|GoodRelations is a standardized vocabulary for product, price, and company data that can be embedded into existing static and dynamic Web pages.|
This page is a stub and will be completed shortly.
You can use dbPedia/Wikipedia URIs for describing what you offer. This is promising, because it allows very precise statements due to the more than 250k URIs of the English Wikipedia that represent typical goods and services like "Laser Printer" or "Motorcycle".
Find the most suitable English Wikipedia page that describes the object or objects to which your offer refers.
Imagine you want to sell a motorbike. Then,
is the best Wikipedia page. By the way, you can search in any language variant of Wikipedia and then traverse to the equivalent English page by clicking on the "English" link on the left-hand side.
Create the proper dbPedia URI by replacing
In our example, you will get
Make the instance of gr:ProductOrServicesSomeInstancesPlaceholder (or gr:ActualProductOrService) an instance of that resource, e.g.
<xml> ... <gr:typeOfGood>
<gr:ProductOrServicesSomeInstancesPlaceholder rdf:ID="ProductOrServicesSomeInstancesPlaceholder_1"> <rdf:type rdf:resource="http://dbpedia.org/resource/Motorcycle"/> <rdfs:comment xml:lang="en">Kawasaki Motorbike 1234</rdfs:comment> <foaf:page rdf:resource="http://www.heppnetz.de/goodrelations/"/> </gr:ProductOrServicesSomeInstancesPlaceholder>
It is important that you take the page name ("Motorcycle") and attach it to http://dbpedia.org/resource/; don't use the Wikipedia URI directly!
Pitfall: When issuing an http get to
you get redirected to
Don't use that URI - that is again a Web page, but we are looking for the non-information resource.
Note that using the dbPedia recipe turns the data into OWL FULL, but that does not hurt as long as you can live without full DL reasoning.
This is because the dbPedia URI denotes an instance of the dbPedia top-level classes, but we reuse it as a class. This is permitted, because referring to the class of objects vs. a single entity are just roles of a conceptual element. The clear distinction between classes and individuals in OWL is for keeping complete reasoning decidable. Don't let others irritate you that the same URI cannot represent a class and an individual.