This is the archive of the goodrelations dicussion list

Hi Michael,

I think it really depends what aspect of coupons you want to model.

In the context of selling the coupons (a la Groupon), I think coupons are
just like any other product. So you could create a gr:Offering with a proper
price specification and the coupon as product attached to it. The product
details (e.g. how to redeem) can be attached as text (gr:Description).

Coupons are (usually) also a discount buy option that you can be exercised
later. What I mean by that is they seem to me as a materialization of a
 gr:Offering. I don't think you can currently say explicitly that an
instance of gr:Offering can be bought or sold.
Coupons can also be distinct. Although instances of gr:Offering are usually
modeled as blank nodes, as countability is not a concern. (You model it
implicitly through gr:hasInventoryLevel), however, if I'm interested in
identifying and track a coupon I'd give it URI.

All in all, GR can be used to model coupons as products to be sold. I'm not
sure about the second part of my thought exercise though.

Bests,

Laszlo


2011/6/14 Shepherd, Michael <Michael.Shepherd at xerox.com>

> 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
>
>


-- 
László Török

Skype: laczoka2000
Twitter: @laczoka
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ebusiness-unibw.org/pipermail/goodrelations/attachments/20110615/c908aa63/attachment.html>