- From: Jean-Yves Rossi <jean-yves.rossi@cantonconsulting.fr>
- Date: Tue, 20 Jun 2017 22:16:14 +0200
- To: David Ezell <David_E3@verifone.com>
- Cc: Joseph Potvin <jpotvin@opman.ca>, KETELS Kris <Kris.KETELS@swift.com>, Katie Haritos-Shea <ryladog@gmail.com>, Kenneth Mealey <Kenneth.Mealey@aexp.com>, Web Payments IG <public-webpayments-ig@w3.org>, "Dapeng Liu (Max) (max.ldp@alibaba-inc.com)" <max.ldp@alibaba-inc.com>, "Ian Jacobs (ij@w3.org)" <ij@w3.org>
- Message-ID: <CAC9FLtgXjc6v5dFPm4ynk+AwjK3o9OeVWmoQt=1Rgv6261OWGw@mail.gmail.com>
> I’m not sure anything is improved by being more explicit in the charter. +1 ! @Ian, I agree with the wording you propose Thanks Kind regards JY Jean-Yves ROSSI +336 51 24 77 94 jean-yves.rossi@cantonconsulting.fr [image: logo_CANTON-Consulting] CANTON <http://goog_1803985827/> - Consulting <http://cantonconsulting.eu/> *Découvrez NDP, le meilleur outil de veille <http://cantonconsulting.eu/edition/abonnement/abonnement-decouverte-formule-d-essai-incluant-4-numeros> sur les ruptures du monde du paiement !* 2017-06-20 16:27 GMT+02:00 David Ezell <David_E3@verifone.com>: > I agree with the relevance in terms of work. > > > > But I’m not sure anything is improved by being more explicit in the > charter. Actual targets for investigation should (IMO) be decided by the > group. Putting more stuff in the charter for review doesn’t really add > much clarity, and possibly adds additional work at the rechartering stage > that isn’t all that helpful. > > > > Best regards, > > David > > > > > > *From:* Joseph Potvin [mailto:jpotvin@opman.ca] > *Sent:* Tuesday, June 20, 2017 10:18 AM > *To:* David Ezell > *Cc:* KETELS Kris; Jean-Yves Rossi; Katie Haritos-Shea; Kenneth Mealey; > Web Payments IG; Dapeng Liu (Max) (max.ldp@alibaba-inc.com); Ian Jacobs ( > ij@w3.org) > > *Subject:* Re: FW: Call for Consensus to Request Member Review of > Commerce IG Charter - Please Respond by 19 June > > > > There was quite a comprehensive list of other standards put together early > in the W3C Web Payments work, and probably most of it is relevant here. > > For a "Commerce IG" it seems to me that ISO 20022 for financial messaging > is adjacent, not directly involved. If the the charter should mention just > an example or two, ISO 19845 is more directly in the commerce sphere. > (I'm not playing 'favourites' -- in own work those two are equally > important.) > > > Joseph Potvin > Executive Director, Xalgorithms Foundation > Mobile: 819-593-5983 > jpotvin@xalgorithms.org > https://www.xalgorithms.org > > > > > > > On Tue, Jun 20, 2017 at 10:01 AM, David Ezell <David_E3@verifone.com> > wrote: > > I would caution that since the line say’s “e.g.” it’s very open to all the > standards mentioned below, as well as others that may be as important, but > we don’t have them on the list. The more standards mentioned in the list, > the more precise it seems, and that’s not accurate. > > > > *From:* KETELS Kris [mailto:Kris.KETELS@swift.com] > *Sent:* Tuesday, June 20, 2017 9:11 AM > *To:* Joseph Potvin; Jean-Yves Rossi > *Cc:* Katie Haritos-Shea; Kenneth Mealey; David Ezell; Web Payments IG; > Dapeng Liu (Max) (max.ldp@alibaba-inc.com); Ian Jacobs (ij@w3.org) > *Subject:* RE: FW: Call for Consensus to Request Member Review of > Commerce IG Charter - Please Respond by 19 June > > > > Hi, > > > > There are quite a few financial (and other) standards around. Will you be > the liaison for the standards you mention? > > > > Kind regards > > Kris > > > > *From:* Joseph Potvin [mailto:jpotvin@opman.ca <jpotvin@opman.ca>] > *Sent:* Monday, June 19, 2017 11:06 AM > *To:* Jean-Yves Rossi > *Cc:* Katie Haritos-Shea; Kenneth Mealey; David Ezell; Web Payments IG; > Dapeng Liu (Max) (max.ldp@alibaba-inc.com); Ian Jacobs (ij@w3.org) > *Subject:* Re: FW: Call for Consensus to Request Member Review of > Commerce IG Charter - Please Respond by 19 June > > > > RE: Harmonization with other standards (e.g., ISO 20022) > > > > I suggest: > > > Harmonization with other standards (e.g., ISO 19845, ISO 20022, UNICITRAL > WG IV) > > > Joseph Potvin > Executive Director, Xalgorithms Foundation > Mobile: 819-593-5983 > jpotvin@xalgorithms.org > https://www.xalgorithms.org > > > > > > > -----Original Message----- > From: Ian Jacobs [mailto:ij@w3.org] > Sent: Monday, June 12, 2017 10:08 AM > To: Web Payments IG <public-webpayments-ig@w3.org> > Subject: Call for Consensus to Request Member Review of Commerce IG > Charter - Please Respond by 19 June > > Dear Web Payments Interest Group Participants, > > The charter of the Web Payments Interest Group [1] expires 30 September > 2017. > Since the March face-to-face meeting [2], we have been developing a new > charter with an expanded scope. > > This is a Call for Consensus to determine whether the Interest Group > supports the W3C Director requesting Membership review [3] of: > > Commerce Interest Group Charter > https://www.w3.org/2017/03/commerce-charter.html > > PLEASE RESPOND to the proposal by 9am ET on 19 June. > > For the co-Chairs, > Ian Jacobs > > [1] https://www.w3.org/2014/04/payments/webpayments_charter.html > [2] https://www.w3.org/2017/03/22-wpay-minutes#item08 > [3] https://www.w3.org/2017/Process-20170301/#CharterReview > > ========= > PROPOSAL: That the Web Payments Interest Group request that the W3C > Director > propose the above charter to the W3C Membership. > > Please indicate one of the following in your response: > > 1. Support the proposal. > > 2. Request some changes, but support the proposal even > if suggested changes are not taken into account. > > 3. Request some changes, and do not support the proposal > unless the changes are taken into account. > > 4. Do not support the proposal (please provide rationale). > > 5. Support the consensus of the Web Payments Interest Group. > > 6. Abstain. > > We invite you to include rationale in your response. > > If there is strong consensus by 19 June (9am ET) for the proposal, it will > carry. > > If there are objections or proposals for substantive changes we will try > to resolve them and start a new Call for Consensus. > > ==================== > Regarding Formal Objections > > * If you do not support the charter and you wish your lack of support to > be communicated to the W3C Director and reviewed, please include the > phrase "FORMAL OBJECTION” [4] in your response. Be sure to include > substantive arguments or rationale. > > * Silence will be taken to mean there is no Formal Objection [4]. > > * If there are Formal Objections, the Chairs plan to contact the > individual(s) who made them to see whether there are changes that would > address the concern and increase consensus to advance the charter. > > [4] https://www.w3.org/2017/Process-20170301/#Consensus > > ============================ > Next steps if the Proposal carries > > If the proposal carries, the W3C Management Team will review and complete > the draft charter (e.g., by adding information about chairs and team > contacts and charter end date). > > If the W3C Management Team approves the charter, they will initiate a > 4-week review by the W3C Membership. > > Our goal is to launch the Commerce IG by mid-September and to hold a > Face-to-Face meeting during TPAC 2017. (This would take the place of the > Web Payments IG Face-to-Face meeting.) > > For more about chartering operations, see: > https://www.w3.org/Guide/Charter.html > > -- > Ian Jacobs <ij@w3.org> > https://www.w3.org/People/Jacobs/ > Tel: +1 718 260 9447 > > > > > > > > American Express made the following annotations > ************************************************************ > ****************** > "This message and any attachments are solely for the intended recipient > and may contain confidential or privileged information. If you are not the > intended recipient, any disclosure, copying, use, or distribution of the > information included in this message and any attachments is prohibited. If > you have received this communication in error, please notify us by reply > e-mail and immediately and permanently delete this message and any > attachments. Thank you." > > American Express a ajouté le commentaire suivant le Ce courrier et toute > pièce jointe qu'il contient sont réservés au seul destinataire indiqué et > peuvent renfermer des > renseignements confidentiels et privilégiés. Si vous n'êtes pas le > destinataire prévu, toute divulgation, duplication, utilisation ou > distribution du courrier ou de toute pièce jointe est interdite. Si vous > avez reçu cette communication par erreur, veuillez nous en aviser par > courrier et détruire immédiatement le courrier et les pièces jointes. Merci. > > ************************************************************ > ****************** > > > > > > ********************************************************* > This electronic message and any attachments are intended only for the use > of the addressee. The information in this electronic message is > confidential and proprietary, and may include privileged information. If > you are not the intended recipient, please delete this electronic message > and any attachments and notify the sender of the error. Please be aware > that any unauthorized use, dissemination, distribution or copying of this > message or any attachments is strictly prohibited. > > > ********************************************************* > This electronic message and any attachments are intended only for the use > of the addressee. The information in this electronic message is > confidential and proprietary, and may include privileged information. If > you are not the intended recipient, please delete this electronic message > and any attachments and notify the sender of the error. Please be aware > that any unauthorized use, dissemination, distribution or copying of this > message or any attachments is strictly prohibited. >
Attachments
- image/gif attachment: image003.gif
Received on Tuesday, 20 June 2017 20:17:08 UTC