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.
Martin Hepp
martin.hepp at ebusiness-unibw.org
Wed Jun 15 12:13:17 CEST 2011
Hi Michael, Thanks for your question. There are several ways of modeling coupon-information in GoodRelations: > > Hi all, > > I was curious to know if there are current activities or potential user scenarios that use GoodRelations in the context of coupons? Is there a coupon ontology extension or perhaps a way that GoodRelations can help to specify coupons? > 1. Gift Vouchers If the coupon has a money equivalent and is basically a method of payment, then your type of coupon is an instance of gr:PaymentMethod. Attach this type to the offers for which it can be turned in. foo:GiftVoucher a gr:PaymentMethod ; gr:name "ACME Gift Vouchers (gr:PaymentMethod)" . foo:Offer0001 a gr:Offering ; gr:acceptedPaymentMethods foo:GiftVoucher. You may then also want to model that one can buy gift vouchers, which would happen by creating a product class foo:ACMEGiftVouchers a owl:Class ; rdfs:subClassOf gr:ProductOrService ; gr:name "ACME Gift Vouchers" . and two properties foo:value a owl:DatatypeProperty ; rdfs:subPropertyOf gr:datatypeProductOrServiceProperty . foo:currency a owl:DatatypeProperty ; rdfs:subPropertyOf gr:datatypeProductOrServiceProperty . Then, you can offer individual gift vouchers for sale: foo:GiftVoucher20USD a foo:ACMEGiftVouchers, gr:SomeItems ; foo:value 20.00 ; foo:currency "USD"^^xsd:string . foo:Offer0002 a gr:Offering ; gr:includes foo:GiftVoucher20USD ; gr:hasPriceSpecification [a gr:UnitPriceSpecification ; gr:hasCurrency "USD"^^xsd:string ; gr:hasCurrencyValue 20.00 ; gr:validThrough "2011-31-12"^^xsd:datetime ] . 2. Coupons that entitle you to obtain a product or service at a reduced price (in the Groupon sense) In this case, you could model a special offer (gr:Offering) and constrain it's validity to a special audience via gr:eligibleCustomerTypes. foo:SummerSaleCoupon a gr:BusinessEntityType ; gr:name "Summer Sale Coupon must be presented" . foo:Offer0003 a gr:Offering ; gr:eligibleCustomerTypes foo:SummerSaleCoupon ; gr:hasPriceSpecification [a gr:UnitPriceSpecification ; gr:hasCurrency "USD"^^xsd:string ; gr:hasCurrencyValue 10.00 ; gr:validThrough "2011-31-12"^^xsd:datetime ] . I have been thinking about a special coupon extension for GoodRelations; this is on our radar. If there is significant interest, i.e. potential real-world adopters, we can make this a priority. Best wishes Martin Hepp On Jun 14, 2011, at 10:26 PM, Shepherd, Michael wrote: > Hi all, > > I was curious to know if there are current activities or potential user scenarios that use GoodRelations in the context of coupons? Is there a coupon ontology extension or perhaps a way that GoodRelations can help to specify coupons? > > Thanks! > Mike > > _______________________________________________ > goodrelations mailing list > goodrelations at ebusiness-unibw.org > http://ebusiness-unibw.org/cgi-bin/mailman/listinfo/goodrelations