W3C home > Mailing lists > Public > public-digitaloffers@w3.org > February 2017

RE: [Digital Offers][Use Cases] thoughts 2017-02-27

From: David Ezell <David_E3@VERIFONE.com>
Date: Mon, 27 Feb 2017 17:15:12 +0000
To: "public-digitaloffers@w3.org" <public-digitaloffers@w3.org>
CC: 'Ian Jacobs' <ij@w3.org>, "Linda Toth (ltoth@conexxus.org)" <ltoth@conexxus.org>, Adam Lake <creatinglake@gmail.com>, "Manu Sporny (msporny@digitalbazaar.com)" <msporny@digitalbazaar.com>
Message-ID: <SN1PR0301MB16157F11BFA0AFA54808C430C8570@SN1PR0301MB1615.namprd03.prod.outlook.com>

From: David Ezell
Sent: Monday, February 27, 2017 10:42 AM
To: public-digitaloffers@w3.org
Subject: [Digital Offers][Use Cases] thoughts 2017-02-27

Hi All:
Here are a few thoughts in advance of our telcon today at noon eastern time (US).  Referring to our wiki document:

1)      There are a few of "click through" use cases.  These use cases are more like traditional web marketing, in that they provide an offer >in context< of visiting a web page, and not involving any portion of the payment cycle.  I think we should examine these carefully. (4.2.4, 4.2.5).

2)      A couple of use cases indicate program "sign-up" through SMS.  I think we need to extend these a bit so that they link in, and be careful where we put them (4.2.6, 4.2.7).

3)      "Age Restriction" (4.3.1) is not defined.

4)      4.3.2 and 4.3.3 deal with "copiable" and "non-copiable" offers.  We should probably spend some time to indicate how something might be made copiable, and also how something might be made "non-copiable".

5)      "Tracking coupons after offline acceptance" (4.6.6) should be fleshed out to indicate how it actually needs to link to any processing.

6)      4.6.7 and 4.6.8 are essentially ID check in a brick-and-mortar scenario.  Today we normally expect that store personnel check the ID (possibly with the aid of POS software).  We need to examine how these link to our problem space.  Specifically, how did the customer get the coupon in the first place, could it have been prevented, and what is the risk exposure for the merchant/offer provider?

HTH.  Looking forward to talking to all of you at noon.
Best regards,
Received on Monday, 27 February 2017 17:48:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 27 February 2017 17:48:54 UTC