Web Payments Interest Group Teleconference -- 06 Jan 2015

<wseltzer> trackbot, prepare teleconf

<trackbot> Date: 06 January 2015

<scribe> Meeting: Web Payments IG group call

<scribe> Agenda: https://lists.w3.org/Archives/Member/member-webpayments-ig/2015Jan/0000.html

<jheuer> who calls me 'heurer'?

<dezell> https://lists.w3.org/Archives/Member/member-webpayments-ig/2015Jan/0000.html

<scribe> Scribe: steph

<dezell> scribenick: steph

review of the agenda

david: any other items?

Manu: cover f2f, registration, etc.

david: +1 will cover that in the agenda f2f point

review of previous minutes

<dezell> http://www.w3.org/2014/12/19-wpay-minutes.html

https://www.w3.org/2014/12/16-wpay-minutes.html

<dezell> Correct Minutes: https://www.w3.org/2014/12/16-wpay-minutes.html

david: comments on the minutes?

<manu> +1 to approve minutes.

<virginie> no comment

silence...

David: minutes of dec 16 Approved

Review of action items

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

<wseltzer> manu: CG has a process for signing the Final Specification Agreement, but the CG site tool is broken

<wseltzer> ... everyone in the CG who made a contribution is willing to sign

<wseltzer> ... we just need to get those sigs into the W3C db

<wseltzer> manu: I'll follow up

david: will finalize with Pat
... another item is mising that was on Nitin

<dezell> ACTION-36 - reassign to dezell

<manu> No other comments on actions.

stephane: done

Use-case update

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

manu: comments in the doc

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

david, laurent, steph and mine are in

Manu: some uc have been developed

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

like the URL above and belo

manu: deadline-end of week
... please do your job

let's try to have some amterial for thursday call

david: a few questions

at the top we have iso documents

to help structuring the use-cases

we need a victim to help us to be sure we cover all the pieces

we need tobe sure we cover ISO20022

Erik: some of the business processes are quite legacy. We will categorize, but will get through our uc with iso2002 edtior and see if he agrees

<manu> ACTION: Manu to summarize US Fed use cases document and create new use cases for the wiki. [recorded in http://www.w3.org/2015/01/06-wpay-minutes.html#action01]

<trackbot> Created ACTION-38 - Summarize us fed use cases document and create new use cases for the wiki. [on Manu Sporny - due 2015-01-13].

erik: business processes needs to be cross-referenced with the us fed document

<dezell> ACTION: Erik to review the ISO20022 processes for cross referencing and to provide feedback for the roadmap. [recorded in http://www.w3.org/2015/01/06-wpay-minutes.html#action02]

<trackbot> Created ACTION-39 - Review the iso20022 processes for cross referencing and to provide feedback for the roadmap. [on Erik Anderson - due 2015-01-13].

david: it would be great to have a iso20022 seciton in the roadmap and clarify what we believe is legacy and what we are following

erik: some of the business processes are outdated, some are missing. not one-to-one mapping we will

<dezell> dezell: the "use cases" section should be retitled, and we should figure out how to integrate the considerations.

manu: agreed, but we let it in the wiki and we decide later what we keep. We keep because it was discussed before

david: some of the poitns put here like online vs offline touch almost all use-cases

<Zakim> manu, you wanted to respond wrt. ISO20022 / X9 / US Fed. and to mention how to integrate glossary into documents. and to mention ISO20022, X9, US Fed documents, and mention how to

david: reworked some of the name to remove some ambiguity

manu: forgot to mention ISO20022, X9, US Fed documents

they need to be integrated in the UC doc

manu: about x9 not sure where we stand
... we need to boil x9 and us fed doc and extract use-case
... given deadline, i suggest we focus on what we already have (cg+workhsop) on FPWD

then on the next iteration we add us fed+X9 input

erik: us fed: uc sectin is small

it is more research behind uc

so shuold go more in requirements

erik: agreed on focusing on our uc and then extract from other doc
... cross referencing is essential

<dezell> steph: I agree with the Agile approach, but that begs the question about what is in the next revision.

<manu> +1, yes, good idea - mention what the next iteration will have in it (use cases)

manu: did a deep read in us fed

great research doc

great doc, but will take a while to process completly

erik: +1

katie: jumping out, but will keep pat updated

<jheuer> when will Pat be back?

david: all: please go review and add example

even if you didn't commit to this TF, we need your input

david: no limitation in sharing with other

erik: we can use content from us fed doc to put in our

doc

david: we can't put in the wiki but shuold be accessible to the grou

manu: no limitation on our uc, but the other docs are more problematic

david: how to od this?

wendy: we can create pages in our dated space, member restricted

and tell people abut the restriction

<manu> +1 to put it on date-space W3C for member-only access.

<scribe> ACTION: DAvid to work with wendy on publishing documents in W3C dated space with the right ACL [recorded in http://www.w3.org/2015/01/06-wpay-minutes.html#action03]

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

<scribe> ACTION: Dezell to work with wendy on publishing documents in W3C dated space with the right ACL [recorded in http://www.w3.org/2015/01/06-wpay-minutes.html#action04]

<trackbot> Created ACTION-40 - Work with wendy on publishing documents in w3c dated space with the right acl [on David Ezell - due 2015-01-13].

david: we can share p2p in case

Erik: +1

david: deadline?

manu: good to have feedback fro thursday meeting, deadline for friday, but not sure we can fit
... we shuold publish after the F2F

Payment Agent TF report

david: trajectory for SE tf ?

joerg: full report in the last 2 weeks: nothing done, till Pat is back. more things to come by friday (next call)

not sure about where pat is wrt updating his diag

<manu> I will also try to do my action wrt. Payment Agent TF - propose a layout for the document based on time-based approach.

nothing new in the wiki, new input+new discussion on friday meetings

david: meeting friday?

joerg: yes

https://www.w3.org/Payments/IG/wiki/Main_Page#IG_Meetings

virginie: dealing with SE@W3C: no progress

Secure Element and WebCrypto Update

<manu> I'm concerned that this group isn't spun up enough to make substantive comments on Secure Element and WebCrypto API.

access to SE is still non-official draft

web crypto decided not to deal with that

need to have a dedicated group for this topic, but no plan yet

david: SE is a key component of the payment agent

and having an API is a key part

on how things work, so we need to work together to be sure it goes out

let us know how it can help?

erik: trying to bring on board Boris who worked on google checout system

trying to have him onboard to join your TF

joerg: great

<jheuer> +1 to emphasis on SE for client-side/ user payment agent

<Zakim> manu, you wanted to ask about what this group might say about SE and WebCrypto.Next?

manu: timing is terrible, not really ready to make comments on SE, but it important we say something

it would be important to develop our PoV

manu: virginie, tell us what we should say
... not sure about web cypto next content

so perhaps an overivew on api will be helpful

manu: biggest issue is about what exist today and what is next in web crypto

<wseltzer> [to me, it would be most helpful for this group to say a) what it needs from SE and b) who's willing to work on it]

<jheuer> +1 on supporting WebCrypto and SE discussion

steph: to which activity such a new wg should belong to?

<Zakim> virginie, you wanted to comment on the webcrypto next and secure element plans

virginie: webcrypto.next: charter discussed on the web security ML

low activity

no recharter before march

virginie: topics: new crypto operation, mgt of certificate

browser makers agreed that adding SE to the next charter is not good, so it will not be part of it (at least for now)

virginie: about SE, different discussions on the services. different proposal in the last 6 months

discussion on APU, the programming language for SE

2nd optin: being at the service level

API level, please check pin, sign transaction etc

virginie: 3rd level: cryptigraphic service in the SE, might be part of webcrypto next

virgnie: suggested that a dedicated WG for SE API

gemalto is pushing for this

to get more resources form members

this is my own objective for Q1 to desing a draft charter asap

virginie: there is also some work at globalplatform this topic

liaison exists with globalplatform

<jheuer> offering help to Virginie in drafting the SE charter - also GSMA has over the last days expressed interest in Payment IG - let's gudie them to SE!

david: bloomberg & nacs will be happy to join gemalto on this item

<virginie> FYI : globalplatform http://www.globalplatform.org/

wendy: important part of this ig role is to tell what we need from the web, so critical to tell ig opinion on SE api

david: will start the agenda brainstorming by email
... AoB?
... next meeting same time next week

virginie: dates of f2f?

<wseltzer> please remember to register for the IG F2F, Feb 2-4, Utrecht, NL

https://www.w3.org/Payments/IG/wiki/2014-02-02_Meeting_Page

<wseltzer> ->meeting info: https://www.w3.org/Payments/IG/wiki/2014-02-02_Meeting_Page

<wseltzer> -> F2F Registration link https://www.w3.org/2002/09/wbs/73816/wpigf2f201401/

<wseltzer> trackbot, end teleconf

- DRAFT -

Web Payments Interest Group Teleconference
06 Jan 2015

Attendees

Contents

review of the agenda

review of previous minutes

Review of action items

Use-case update

Payment Agent TF report

Secure Element and WebCrypto Update

Summary of Action Items

Scribe.perl diagnostic output

- DRAFT -

Web Payments Interest Group Teleconference 06 Jan 2015

Attendees

Contents

review of the agenda

review of previous minutes

Review of action items

Use-case update

Payment Agent TF report

Secure Element and WebCrypto Update

Summary of Action Items

Scribe.perl diagnostic output

Web Payments Interest Group Teleconference
06 Jan 2015