RE: action-16 IG deliverable and timeline

David and team
 I agree, so while I have been a bit quiet on this forum, that is due to
high travel at my end. Hope that comes to a halt.
But I agree, as I suggested on the call, I will actively participate,  and
as we define the work products I think we ought to spend time in including
things like:

1. Foundational technologies -- this includes payment tokenization (This is
true for ApplePay and HCE) and other use cases that go with it
2. Mobile Payment engagement
3. Mobile Payment Security -- this includes transaction, engagement and
interaction security.
 as we define use cases, I think this we ought to start populating the
glossary as we produce these work products.

Just my initial thoughts!


N

:)
Nitin Gaur
CTO, IBM Mobile Payments
512-789-5300




From:	David Ezell <David_E3@VERIFONE.com>
To:	"public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>
Cc:	Erik Anderson <eanders@pobox.com>, "Stephane Boyera
            (boyera@w3.org)" <boyera@w3.org>
Date:	11/19/2014 09:55 AM
Subject:	RE: action-16 IG deliverable and timeline



Hi Folks:

We agree with Stephane that the roadmap is a >very< important first work
product for the Web Payments IG.

Please read this message with the expectation that you will volunteer in
some way to help us get the proposed work done.

If the roadmap document is done well and in the near term, it should have
the following effects on people:

1) It will please them that we got our first draft out so soon.
2) It will give them confidence that we know at least one (if not every)
path through this very dense topic.
3) It will motivate them to come forward and indicate what they don't like
and emphasize other paths that may be beneficial.
4) It will help define scope for future discussions.

In other words, the roadmap doesn't have to be perfect, nor is it expected
to be the "last word" in web payments - it should be a thoughtful straw
model.

Stephane listed what is required for a roadmap document at this point:
*an individual or a set of editors for the document [1]
*content

The charter[2] lays out possible ways to approach the roadmap.  Here's a
sample outline for a roadmap document, based on my interpretation of the
charter:

a) Target scenarios - the [use_case] task force will provide content.
b) Relevant existing standards - at our f2f we identified several.
c) Potential sample architectures - the [payment_agent] task force will
provide content.  This section can
    address both near term and far-fetched possibilities, relevant actors,
etc.
d) Projections - taking a, b, and c together, provide some idea of expected
progress in the industry.
e) Glossary - the Glossary Task Force will provide content.

Using this outline, I think we can cover most of the "Web Payments Roadmap"
items indicated in the charter.  But it's only my idea - tear it up and
come up with something else if you like.

We are looking for editors to help us move this activity forward.  Joerg
Heuer has graciously volunteered for some of the work.

Let's try to get this effort underway.  We are looking for volunteers to be
editors for this roadmap document.

Best regards,
David Ezell

[1] for those of you familiar with W3C work, you'll recognize that being an
editor is one of the
     >few< ways you can be recognized in any meaningful way.  Chairs are in
many ways subordinate to editors,
     but don't tell them that.
[2]
http://www.w3.org/2014/04/payments/webpayments_charter.html#deliverables


-----Original Message-----
From: Stephane Boyera [mailto:boyera@w3.org]
Sent: Sunday, November 16, 2014 2:08 PM
To: public-webpayments-ig@w3.org
Subject: action-16 IG deliverable and timeline

Dear colleagues,

As discussed during the call last friday, I'm launching the discussion
related to IG deliverables and timeline.
First of all, in order to attract attention, it is esential that the group
publish regularly deliverables that summarize its work.

The charter contains a series a deliverables. see
http://www.w3.org/2014/04/payments/webpayments_charter.html#deliverables

This list points as the first deliverable a "Web Payments Roadmap"
I think it is the most important one that will highlight the gaps in the
technology stack, as well as clearly identify the areas where the group is
planning to make a significant contribution.
I believe that if we want to use the current momentum, and use the activity
in the domain to be visible, we should aim at publishing a first version of
this deliverable sometime in Q1 2015. I suggest we put a data, like 1st
March and do our best to deliver at this date.

What we need for a deliverable is 2 things:
*an individual or a set of editors for the document *content

What is imho more important for now is the second part, the content.
My feeling was that the 2 task forces we have on use-cases and
payment-agent are working on two sides of the problem: the bottom-up
approach defining a set of scenario we want to cover, and a top-down
approach defining a framework with various modules.
My view after the face-to-face was that the roadmap deliverable will be the
results of the encounter of the work of the two task forces: an overall
architecture with relatively high level modules that are addressing a
series of use-cases. A first draft could stay at a high-level identifying
the modules, and perhaps the set of actors that are essential for their
implementation as well as the other standards that are in the scope of the
module. Such a deliverable should allow us to identify working groups
(existing or new ones) to handle some of the modules.

Therefore, per my action, I wanted to write down my view on this, and see
what people think about this approach, the proposed timeline etc.

cheers
steph
--
Stephane Boyera        stephane@w3.org
W3C                +33 (0) 6 73 84 87 27
BP 93
F-06902 Sophia Antipolis Cedex,
France




This electronic message, including attachments, is intended only for the
use of the individual or company named above or to which it is addressed.
The information contained in this message shall be considered confidential
and proprietary, and may include confidential work product. If you are not
the intended recipient, please be aware that any unauthorized use,
dissemination, distribution or copying of this message is strictly
prohibited. If you have received this email in error, please notify the
sender by replying to this message and deleting this email immediately.