See also: IRC log
<Ian> scribe: pat
<Ian> Meeting: Web Payments Interest Group Teleconference
<Ian> agenda: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0153.html
<Ian> scribe: padler
<scribe> scribe: padler
Ian: is noting to Magda that we are on IRC..
dezell: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0153.html
will talk about Payment Architecture update and google doc later..
<Ian> https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015
dezell:
<dezell> https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015#Agenda_notes
<Ian> agenda draft -> https://www.w3.org/Payments/IG/wiki/Main_Page/FTF_June2015#Agenda_notes
dezell: first topic is face to face
Ian: wants to walk through draft
agenda structure
... Primary focus of face to face meeting is figuring out what
we will propose to W3C as standards work...
... After introductions, need to cover work efforts, schedule,
what is needed in terms of standardization... need to also
provide browser perspective..
... Ian will be working on draft charters
... Manu has been looking at use case priortization
... 3rd day will focus on "What's Next"..
... as well as "Hot Topics" - May need to switch around topics
if these are heavier...
... Looking for volunteers to help lead certain
discussions
... working with ISO standards groups to help bring that
perspective to the Face to Face meeting
... Adrian asked for 90 mIn at Face to Face meeting
... will be sharing agenda and inviting people to the Face to
Face at upcoming AC meeting next week
dezell: Need to hear from new members and the group about what is important
<Ian> padler: Let's welcome new participant!
dezell: will be getting good insight/input from Mark Tiggas (sp?) on his experience with ISO
<Ian> magda: My name is MagdaS...representing Apple here today...
<dezell> pat: should we ask people to introduce themselves?
Magda: Introduces herself from Apple...
<Ian> Magda: I've been in mobile and payments throughout my career
adrian: expecting time slots to flush out over the next week.
<dezell> adrian: 90 minutes may be too long for Value Web TF.
<Ian> padler: I think the architecture and prioritization discussions are helping to shape the time and topics of the FTF
<Ian> ..the goal this week is to get as much as possible in the document so we know where holes/gaps are
<Ian> ...certain things are non-controversial. Some things will require us to dive deep to understand what we need for interop
<Ian> ...we will be spending a lot of time this week
padler: perhaps we can use the document as a way to focus some of the time for the agenda
Ian: would like to ensure that
each topic has owners and that owners all have plans for what
they would like to cover and for how they are planning to
use/structure time..
... working with browser vendors in the background, but need to
have owners on topics
<Ian> +1
Laurent_: Need to cover Security and Web Crypto topics
Ian: do we need someone from Web App Sec?
Laurent_: Yes, need to have them present..
<dezell> ACTION: dezell to ask Erik about phone connectivity for the June meeting. [recorded in http://www.w3.org/2015/04/27-wpay-minutes.html#action01]
<trackbot> Created ACTION-96 - Ask erik about phone connectivity for the june meeting. [on David Ezell - due 2015-05-04].
Ian: Need to consider which other Security/Crypto guests/representatives we need to have present at the meeting..
dezell: Need to consider that
this should not be a 90 min slideshow..
... this needs to be more about engagement and action..
... goal is to make sure that we get everyone's thoughts on the
table so that we can move towards action/consensus
<dezell> pat: group met Friday. Discussion on the state of the document.
<dezell> pat: github/respec is taking too much time.
<dezell> pat: this URL gives view access.
<dezell> pat: we would like comments on the document.
<dezell> ...: if you'd like edit access I will give it if asked.
<dezell> ian: I am often reluctant to put things in GoogleDocs. I'm more comfortable to using the Wikis.
<dezell> ...: is there a strong rationale?
<dezell> pat: GD gives better speed of editing, to be moved to GitHub later.
<dezell> ian: if there is a plan to port it back to the Wiki then that is OK for me.
<dezell> Erik: I can't go to Google Docs at Bloomberg.
<scribe> ACTION: Pat to add link to the Google Doc in the Wiki [recorded in http://www.w3.org/2015/04/27-wpay-minutes.html#action02]
<trackbot> Error finding 'Pat'. You can review and register nicknames at <http://www.w3.org/Payments/IG/track/users>.
<scribe> ACTION: padler to add link to the Google Doc in the Wiki [recorded in http://www.w3.org/2015/04/27-wpay-minutes.html#action03]
<trackbot> Created ACTION-97 - Add link to the google doc in the wiki [on Patrick Adler - due 2015-05-04].
<dezell> pat: it's hard for me too - I have to go to a different network to get there.
<dezell> ian: I'm happy to help start a new page - we'll talk.
<Magda> When should be we have some feedback for additional discussion submitted to you by and in what format?
<dezell> Magda: when should we have feedback for additional points in the document, and what format?
<dezell> Pat: we have a fair amount of prior work, where we are fleshing out how things work.
<dezell> Pat: we're looking for people to put strong thoughts or opinions about key concepts in the next few days.
<dezell> Pat: we want to be close to an FPWD for the F2F in June.
<dezell> Erik: I have a lot of documentation on the requirements for "future payments".
<dezell> ...: we should go over those and make sure we haven't missed anything.
<dezell> Erik: I think we have adequate documents for the payment agent.
<dezell> Pat: so key management and encryption are first?
<dezell> Erik: higher level summary first.
Erik: Will be focused on pulling summary level requirements into the document..
<dezell> ian: I will summarize what I understand what I think we're working on...
Ian: Use cases are scoping device...
<dezell> ...: use cases are our scoping device and will be the ultimate source of requirements, but including some NFRs.
Ian: Architecture Vision document should answer the question of "this is what we want payments on the web to look like"
<dezell> ...: it won't be quite an elevator pitch, but the vision document will be a short/sweet description.
Ian: This vision has certain requirements to achieve...
Once we capture the requirements, this would be good input into the work group charters..
Ian: Manu is working on prioritized feature sets / phases to help focus early work on Working Groups..
<Zakim> dezell, you wanted to ask Ian for the last bullet
<dezell> Ian: here's my list.
<dezell> Use Cases
<dezell> Architecture Vision
<dezell> Analysis of use cases / presentation of requirements.
<dezell> Charter development.
<dezell> Prioritization of Use Cases - lead up to the prioritization at f2f.
Ian: goal is to help focus work efforts so as not to "boil the ocean"..
dezell: any new news on use cases?
Ian: have a related topic to
cover reaching out to groups to review use cases..
... dependencies to other groups not in our charter... Ian will
be reaching out to these other groups to explicitly ask for
feedback on our use cases..
... Draft email has been created.
<dezell> Laurent: is it too late to send comments?
<dezell> Ian: it's never too late?
Laurent_: Where are we on the Editor's Draft? Who should we send comments to?
<Zakim> dezell, you wanted to talk about review by X9
Ian: If just for editors, use Github, if for the broader group for discussion, please use the Mailing LIst.
dezell: X9 has a task force to
review our use cases...
... Article has been posted to the NACS Daily news feed..
dezell: Claudia is out for next 2
weeks
... Discussing how best to use liaison status - working with
Pat/Katie J to get more details
... Documents will be available to IG members but not shareable
outside of IG..
... Everyone should read the ISO 12812 standard as it is
available
Erik: 12812 is very focused on Mobile devices and not so much on Browsers..
dezell: Long discussions at recent conference on 12812, ISO team is supportive of what we are trying to accomplish...
Erik: Need to get the standard out to the IG group so that we can provide good input to the standard development...
<dezell> ACTION: dezell to find out the access rules for ISO12812 DIS review. [recorded in http://www.w3.org/2015/04/27-wpay-minutes.html#action04]
<trackbot> Created ACTION-98 - Find out the access rules for iso12812 dis review. [on David Ezell - due 2015-05-04].
Ian: Point of clarification: sounds like ONLY liaison has access to the standard document... dezell will work to clairfy.
Erik: Concerned if only 1 person has access to the standard... hope was to have anyone on the IG have access..
<manu> Manu (or David) can ask Alan Thiemann about ISO12812 access at the conference.
dezell: Excited about meeting at
Bloomberg.. focusing on putting materials together for next
week at AC meeting
... PLEASE REGISTER for F2F if you have not done so
already..
... Thanks everyone! That's a wrap..
<manu> My understanding is that anyone in the group can access the documents, will clarify via Alan.
<dezell> s///s
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) WARNING: Bad s/// command: s/Payment Agent//s Succeeded: s/:)// Succeeded: s/Payment Agent// Found Scribe: pat Found Scribe: padler Inferring ScribeNick: padler Found Scribe: padler Inferring ScribeNick: padler Scribes: pat, padler Default Present: padler, dezell, Istvan, +33.1.55.01.aaaa, Laurent_, Ian, AdrianHB_web, Erik, Joerg, +1.703.926.aabb, Magda Present: padler dezell Istvan Laurent_ Ian AdrianHB_web Erik Joerg Magda Agenda: https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0153.html Got date from IRC log name: 27 Apr 2015 Guessing minutes URL: http://www.w3.org/2015/04/27-wpay-minutes.html People with action items: dezell padler pat WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]