Cookbook/Seeks

= Modeling Wish Lists, Demand, or Tendering Data =

Describing your interest in certain offers using GoodRelations

On this page, we explain how the GoodRelations vocabulary can be used to express your interest in certain offers, e.g. wish lists, requests for quotations, or tendering data.

Overview
GoodRelations can be used both for advertising a product or service, or for expressing your interest in buying / consuming a particular good or service.

This is straightforward using the property gr:seeks. You simply link the individual or business expressing the demand (the "agent") with an instance of gr:Offering that describes WHAT you are looking for. The type of business function, e.g. sales, lease, repair, etc. is attached to the offering using gr:hasBusinessFunction as usual.

Example
Assume we are interested in buying one TV set but I am not interested in offers more expensive than 200 euros.

RDFa
Simply paste the following content before the closing &lt;/body&gt; element in your page:







Example in RDF/XML
http://www.heppnetz.de/wishlist/wishlist.html

 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">   Example of A GoodRelations Wish-List  This page is a small example of how one can express interest in a particular product or service on the Web of Linked Data. Provided by the E-Business &amp; Web Science Research Group (Prof. Hepp) at Universitaet der Bundeswehr Muenchen, www.unibw.de/ebusiness/.

Hepp Space Ventures Inc. is a non-existent corporation made up for the purpose of this example. We are looking for: A TV set with at least 30 CMT screen-size Offers are to be sent to our main office: 1234 Hepp Road , 85577      Neubiberg , Bavaria , Germany. Phone:+49-89-6004-0 Web: www.heppnetz.de







Example in Turtle
@prefix foaf: . @prefix gr: . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>. @prefix vcard: <http://www.w3.org/2006/vcard/ns#>. @prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>. @prefix xml: <http://www.w3.org/XML/1998/namespace>. @prefix xsd: <http://www.w3.org/2001/XMLSchema#>.

<http://www.heppnetz.de/wishlist/wishlist.html#company> a gr:BusinessEntity ; rdfs:label "Hepp Space Ventures Inc."@en ; gr:legalName "Hepp Space Ventures Inc."@en ; gr:seeks <http://www.heppnetz.de/wishlist/wishlist.html#mydemand> ; foaf:page <http://www.heppnetz.de/>, <http://www.heppnetz.de/wishlist/wishlist.html> ; vcard:adr <http://www.heppnetz.de/wishlist/wishlist.html#address> ; vcard:fn "Hepp Space Ventures Inc."@en ; vcard:geo [ vcard:latitude "48.0802626"^^xsd:float ; vcard:longitude "11.6407428"^^xsd:float ] ; vcard:tel "+49-89-6004-0"^^xsd:string ; vcard:url <http://www.heppnetz.de/>.

<http://www.heppnetz.de/wishlist/wishlist.html#TypeAndQuantityNode> a gr:TypeAndQuantityNode ; gr:amountOfThisGood "1.0"^^xsd:float ; gr:hasUnitOfMeasurement "C62"^^xsd:string ; gr:typeOfGood [ a gr:SomeItems ; rdfs:label "A TV set with at least 30 CMT screen-size"@en ; rdfs:comment "A TV set with at least 30 CMT screen-size"@en ; foaf:page <http://www.heppnetz.de/wishlist/wishlist.html> ].

<http://www.heppnetz.de/wishlist/wishlist.html#UnitPriceSpecification> a gr:UnitPriceSpecification ; gr:hasCurrency "EUR"^^xsd:string ; gr:hasMaxCurrencyValue "200"^^xsd:float.

<http://www.heppnetz.de/wishlist/wishlist.html#address> a vcard:Address ; vcard:country-name "Germany"@en ; vcard:locality "Neubiberg"@en ; vcard:postal-code "85577"^^xsd:string ; vcard:region "Bavaria"@en ; vcard:street-address "1234 Hepp Road"@en.

<http://www.heppnetz.de/wishlist/wishlist.html#mydemand> a gr:Offering ; gr:hasBusinessFunction gr:Sell ; gr:hasPriceSpecification <http://www.heppnetz.de/wishlist/wishlist.html#UnitPriceSpecification> ; gr:includesObject <http://www.heppnetz.de/wishlist/wishlist.html#TypeAndQuantityNode> ; gr:validFrom "2009-07-20T00:00:00Z"^^xsd:dateTime ; gr:validThrough "2010-07-20T00:00:00Z"^^xsd:dateTime ; foaf:page <http://www.heppnetz.de/wishlist/wishlist.html>.

Additional Information

 * You can attach images to the product; this will make sense when the business function is different from gr:sell (e.g. repair) - "Who can fixed that broken wristwatch?"
 * You can attach EAN/UPC codes to the product if you are looking for a particular make and model.
 * You can be much more specific in describing what you want by using a domain ontology ike eclassOWL or freeClass; this will allow specifying quantitative or qualitative properties of the items you are looking for - "Concrete tubes with 30 centimeters inner diamater and a length of at least 2 meters".
 * You can specify acceptable payment and delivery options same.
 * There is a proposal for a similar type in schema.org: http://dl.dropbox.com/u/1523969/microdata/Demand.html

In a nutshell: Basically, you can use the very same GoodRelations vocabulary for the buy and the sell side of commerce.