See also: IRC log
<manu> zaim, this will be wpay
<Ian> scribe: Isvan
<Ian> scribe: Istvan
<dezell> no changes requested
<dezell> https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Mar/0102.html
dezell: focus on ISO12812, which is basically web payments, and check if we can align with that
<manu> s/web payments and check/ISO12812, which is basically web payments, and check/
dezell: we need to also look at tokenization for X9 and make sure we can align with that
Erik: lets focus on 12812
lets focus on three standards X9-xxx
Manu: will the group focus on ISO12812 in the short term? In the long term follow through ISO12812 with larger organisations other than W3C
dezell: that's correct
... 20022 part is more focus in Europe and in India
Erik: 12812 call it as a guiding
doocument
... we should catch up on credentials
Manu: we need to make sure we assing someone to this piece of work to deliver it
dezell: Erik and David can get
access to these document (ISO12812 etc)
... Claudia X9 offered collaboration on security
Ian: summary for a blogpost for external groups for comms purposes, we can discuss internally then publish it
<manu> ACTION: DavidE to create a summary of the ISO12812/X9 analysis destined for a blog post for external groups for comms purposes. [recorded in http://www.w3.org/2015/03/23-wpay-minutes.html#action01]
<trackbot> Error finding 'DavidE'. You can review and register nicknames at <http://www.w3.org/Payments/IG/track/users>.
<manu> ACTION: dezell to create a summary of the ISO12812/X9 analysis destined for a blog post for external groups for comms purposes. [recorded in http://www.w3.org/2015/03/23-wpay-minutes.html#action02]
<trackbot> Created ACTION-80 - Create a summary of the iso12812/x9 analysis destined for a blog post for external groups for comms purposes. [on David Ezell - due 2015-03-30].
David: took this action as we need to sort out the internal comms, the dependency is to have 12812 vote first sorted
David proposed to draft by after the iso12812 has been released
Claudia: iso12812 goes out for vote on 9 April
Ian: we can speak about the spec in our blogpost in the meantime
<Erik> ISO and X9 specs to follow X9.119 part 2 = Tokenization ANSI X9.69 = Key Management ANSI X9.73 = Cryptographic Message Syntax — ASN.1 and XML X9 ISO 12812 = Mobile Payments
David: will develop the first draft of the blogpost by 30 March
<Erik> ISO and X9 specs to follow
<Erik> X9.119 part 2 = Tokenization
<Erik> ANSI X9.69 = Key Management
<manu> https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/use-cases/index.html#toc
<Erik> ANSI X9.73 = Cryptographic Message Syntax — ASN.1 and XML
<Erik> X9 ISO 12812 = Mobile Payments
Manu: making a good
progress
... in terms of the use cases are included in the FPRD, needs
final editorial
... finishing writing the user stories then once thats done,
review of FPWD then release it a week after
Manu target is to release the First Public Working Draft by middle of April
david: team to review the use cases document
Joerg: User Payment Agent work is progressing
<jheuer> https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/payment-agent/index.html
Joerg: need more alignment with
use cases
... next meeting is scheduled for coming Friday, 27th March
David: document has been improved and the architecture is more mature
Erik: we should look at new services regarding biometrics at the next call
Joerg: we have to mindful of one
standards requested in one standard is not automatically will
be required in another standard
... lets review it at the next user payment agent call
Dave: lets review alternative techniques for coupons and royalty cards at the next UPA call
<dezell> Dave Raggett's email: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Mar/0116.html
Joerg: lets include this topic on the agenda
Claudia: what is the difference
in between X9 and EMVCO
... EMVCo is a payment token
... X9 is a security token
... these are two different things, and we shouldn't thing
these are aligned with each other.It is more like a harmonised
approach
between the two
thanks manu :-)
<Ian> +1 to getting X9 review of our use cases!!
Claudia: groupd of X9 experts to
review any draft wpay is putting together, they can review it
based on iso12812
... this is an option we can pursue
<Ian> IJ: Yes, please let's get "official" review by the X9 folks
Ian: great possibility for a review and it can raise our work, concerns around our work maybe premature
David: maintain our dev facing focus, we have powerful role here so that X9 can review offer of our work is great
Claudia: this is document review from X9 team and we dont have vote, it is about building a relationship with X9
Ian: : W3C doesn't have any interest in voting in any context
David: ISO and X9 world is concerned about who votes on what...thats why we have to be clear about what we need from these groups
Erik: meeting next week with ISO about security
David: are there security standards discussed at X9?
Claudia: regarding security it is
in development regarding tokenization
... to email contacts from security at X9 to Erik
<Ian> https://www.w3.org/Payments/IG/wiki/External_Reviews_Task_Force
<Ian> http://www.w3.org/2014/04/payments/webpayments_charter.html#coordination
Ian: blogpost content could
detail about what standards we will convey, updates on use
cases, UPA etc
... review TF to flesh out some priority about priorities and
updates
David: action 79 on David which was not completed (was due today)
<Zakim> manu, you wanted to suggest as a minimal first step - notify all those groups when we do a publication.
David: will follow this action up ACTION-79
<Ian> IJ: Please list on the task force wiki which groups we are working with and where we think that there are dependencies (in more detail than the charter)
Manu: we can notify working
groups about document publication,and explain the rationale
about the content
... we can develop a spreadsheet for explaining why we would
target a specific working group and why
Ian: outreach for a partner to include in the IG, working on use cases and some slides this week
David: there is no AOB was discussed, thanked everybody's effort
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ttps/https/ FAILED: s/web payments and check/ISO12812, which is basically web payments, and check/ Succeeded: s/web payment and check/ISO12812, which is basically web payments, and check/ Succeeded: s/we need/dezell: we need/ Succeeded: s/Erik;/Erik:/ Succeeded: s/dezell 20022 part/dezell: 20022 part/ Succeeded: s/Manu : we need/Manu: we need/ Succeeded: s/Claudia X9/dezell: Claudia X9/ Succeeded: s/FPRD/FPWD/ Succeeded: s/thanks Manu// Succeeded: s/topic: user payment agent// Succeeded: s/EMVOC/EMVCo/ Succeeded: s/79/ACTION-79/ Succeeded: s/rssagent, draft minutes// Succeeded: s/agenda bashing// Found Scribe: Isvan Found Scribe: Istvan Inferring ScribeNick: Istvan Scribes: Isvan, Istvan Default Present: +1.612.655.aaaa, Davd_Ezell, dezell, claudia, Istvan, Ian, David_Jackson, Joerg, manu, slaory, Erik, Dsr, evert Present: Evert Manu Joerg Erik DavidE DavidJ Istvan Claudia DaveRaggett Ian Slaory Regrets: Pat Agenda: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Mar/0115.html Got date from IRC log name: 23 Mar 2015 Guessing minutes URL: http://www.w3.org/2015/03/23-wpay-minutes.html People with action items: davide dezell WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]