Use Case TF -- 11 Dec 2014

<manu> rssagent, make log member

<manu> rssagent, make minutes

<steph> PCP?

scribename: David Ezell

<scribe> scribenick: dezell

CVS for work

manu: asking stephane for a CVS account and all potential editors, hooked to /docs URL.

<manu> https://www.w3.org/Payments/IG/docs/

<manu> https://www.w3.org/Payments/IG/docs/latest/ <--- latest editors drafts

<manu> https://www.w3.org/Payments/IG/docs/ED/ <--- time-stamped editors drafts

<manu> https://www.w3.org/Payments/IG/docs/WD/ <--- time-stamped working drafts

<steph> ACTION: steph to create a cvs area for editors Payments/IG/Docs and add editors (at least msporny to start with) [recorded in http://www.w3.org/2014/12/11-wpay-minutes.html#action01]

<trackbot> Created ACTION-32 - Create a cvs area for editors payments/ig/docs and add editors (at least msporny to start with) [on Stéphane Boyera - due 2014-12-18].

<manu> https://www.w3.org/Payments/IG/docs/latest/roadmap/ <--- latest Roadmap editors draft ... etc.

manu: reviewing the use case strategy...
... I've sent out some instructions on how to approach to problem.
... we'll walkthrough.

<manu> Minutes from previous call - any changes/additions? http://www.w3.org/2014/12/04-wpay-minutes.html

Previous minutes approval.

http://www.w3.org/2014/12/04-wpay-minutes.html

Action Item Review

RESOLUTION: minutes approved as posted.

<manu> http://www.w3.org/2014/12/04-wpay-minutes.html#ActionSummary

<manu> trackbot, issue-20?

<trackbot> Sorry, but issue-20 does not exist.

<manu> trackbot, action-20?

<trackbot> action-20 -- David Ezell to Set up doodle poll on times for telcons. -- due 2014-12-02 -- CLOSED

<trackbot> http://www.w3.org/Payments/IG/track/actions/20

<manu> http://www.w3.org/Payments/IG/track/actions/open

<manu> trackbot, action-21?

<trackbot> action-21 -- Claudia Swendseid to Ask tc68 how to get non-x9 members access to use cases documents. -- due 2014-12-02 -- OPEN

<trackbot> http://www.w3.org/Payments/IG/track/actions/21

<manu> manu: david, any updates on that?

<manu> dezell: She's giving us suggestions on how to liaise with X9... she has answered us.

<manu> trackbot, close action-21

<trackbot> Closed action-21.

close: action-21

<manu> manu: What's the next step?

<manu> dezell: It's not simple - instructions given were complex on who we should contact/talk to...

<manu> dezell: We need to get together and decide what direction we want to take.

<manu> dezell: Digesting her email was not easy, wasn't her fault, it's just a complex process.

<manu> steph: I think she sent an email about sharing the use cases document - I think she said we can use them.

<manu> steph: She said she can share the use case document with us.

<manu> steph: In summary, I'm working on the global liason sharing w/ ISO, X9, and W3C. That'll take a couple of weeks/months. The use case document from X9 should be resolved within next few hours.

<manu> trackbot, action-25?

<trackbot> action-25 -- Manu Sporny to Assign use cases (more or less at random) to people on the task force. -- due 2014-12-11 -- OPEN

<trackbot> http://www.w3.org/Payments/IG/track/actions/25

trackbot, close action-25

<trackbot> Closed action-25.

<manu> I did that here: http://lists.w3.org/Archives/Public/public-webpayments-ig/2014Dec/0025.html

Review Use Case Strategy

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force

manu: we expect to put the use cases from ISO20022, as well as other X9 use cases.
... goal is to have FPWD done by January.

<lcastillo> It's Laurent Castillo from Gemalto

manu: people should choose the use cases closest to being done.
... about 20 use cases have been assigned to the group.

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#Digital_Receipts

manu: the examples should be adequate to help people fill out the sections for each use case.
... so in January we will come back and see what's ready for inclusion.

<steph> is there one fully written to have a sense of the level expected?

manu: probably not all will make it in.
... purchase request is probably a good example.

<manu> Example of a fully done one: https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#Purchase_Request

steph: I'm not clear on "details"

manu: anything that can't be captured in the simple description at the top.
... it's a good place (e.g.) for things like regulatory issues. Also extended rationale for including the use case.
... "high priority" mainly means "we can make rapid progress".
... also, "push payments" could be high priority even though it might take more time (tech stack isn't quite ready).

<steph> makes sense to me

manu: so it's a case by case decision.

<manu> This is also a good example of a "close to complete" use case: http://opencreds.org/specs/source/use-cases/#verifiable-claims

manu: "Verifiable Claims" also has a lot of examples so it's a good example example.

<manu> dezell: Do you have any dates where you expect people to finish reviews?

manu: it also has some intrusion from "credentials" in this use case.
... I think having feed back in 1-2 weeks (25th December), and review done by January 9 is reasonable.
... that should give us time to bring things together.

laurent: I'm not clear on the process for the task force.
... where do we put the review and other edits?

manu: directly in the wiki.

laurent: and who does these reviews?

manu: the task force is actually assigned first, but we'd like everyone to do reviews.

<steph> very happy to trade some of mine for free

laurent: there are some specific use cases we're already interested in.

<steph> no payment required :)

manu: great! I had to give our current volunteers too many, actually, so having more folks will be good.

Review Use Case Assignments

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force

manu: all you have to do is search for your first name, and you'll find your assignments.

<manu> dezell: Quick question on use cases - Laurent, Pascal - are you going to tell Manu which use cases you're interested in?

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#Choice_of_Payment_Processor

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#In-App_Purchases

laurent: choice of payment processor and in-app purchases.
... we are interested in these already. And assign us others if you need to.

pascal: I'm not comfortable with picking yet.

manu: I'll assign things I think make sense for Gemalto.

pascal: use cases on "secure element" and things like that are definitely of interest.

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#Use_Cases_from_Web_Payments_IG

manu: you can look at some of the new items at the bottom of the list and start to fill those in, too. (URL above).

Do a Review Example

manu: picking one randomly.

<manu> https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#Subscriptions

manu: the terms in the description "buyer" and "payment processor" may need sharpening.

<steph> +1

<steph> (buyers usally does not have payment processor)

laurent: buyers normally don't designate a processor, so I'm a little uncomfortable with terminology here.

dezell: do we want to normalize the terminology as part of the excercise?

manu: I think that's very worthwhile.

<manu> dezell: We need to figure out the language that we should be using. I'm wondering if we shouldn't take a stab at the common names and put them at the top somewhere?

<scribe> ACTION: David Ezell to put a small terminology definition section at the top of the use cases Wiki page. [recorded in http://www.w3.org/2014/12/11-wpay-minutes.html#action02]

<trackbot> 'David' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., dezell2, djackso3, mcdermittd).

<manu> We have this glossary in the Web Payments CG document: https://web-payments.org/specs/source/use-cases/#glossary

<scribe> ACTION: dezell to put a small terminology definition section at the top of the use cases Wiki page. [recorded in http://www.w3.org/2014/12/11-wpay-minutes.html#action03]

<trackbot> Created ACTION-33 - Put a small terminology definition section at the top of the use cases wiki page. [on David Ezell - due 2014-12-18].

laurent: I just added a file to the wiki but I can't find where it is. It's a ppt file.

<manu> just updated this: https://www.w3.org/Payments/IG/wiki/Use_Cases_Task_Force#Subscriptions

<manu> https://web-payments.org/specs/source/use-cases/#glossary

dezell: Does the glossary TF know about this glossary?

<steph> https://www.w3.org/Payments/IG/wiki/Special:ListFiles

<steph> https://www.w3.org/Payments/IG/wiki/File:Payments_Actors.pptx

manu: my only concern is that the list is very "status quo" oriented.
... what is the proposal?
... I think for this most part we've identified these roles in the Web Payments CG as well as the glossary TF.
... "customer" may be at the wrong level of abstraction for some of the use cases.
... base terminology is "payer/payee".
... "customer/merchant" are a realization of the the more abstract terms.

<manu> dezell: How would you classify an acquirer?

<manu> manu: We haven't come to a decision on that.

laurent: there is fuzziness about where the actual end-points are.

manu: we tried to look at use cases and got sucked into terminology discussion.
... I think everyone will have a hard time doing their assignments without these clarifications.
... so DE must do these things soon, and make sure that the Glossary TF is in the loop.

AOB

manu: next call is January 8, 2015.
... I will send prodding emails out.

<steph> thanks

Adjournd.

<steph> happy holidays

- DRAFT -

Use Case TF
11 Dec 2014

Attendees

Contents

CVS for work

Previous minutes approval.

Action Item Review

Review Use Case Strategy

Review Use Case Assignments

Do a Review Example

AOB

Summary of Action Items

Scribe.perl diagnostic output

- DRAFT -

Use Case TF 11 Dec 2014

Attendees

Contents

CVS for work

Previous minutes approval.

Action Item Review

Review Use Case Strategy

Review Use Case Assignments

Do a Review Example

AOB

Summary of Action Items

Scribe.perl diagnostic output

Use Case TF
11 Dec 2014