See also: IRC log
<scribe> Scribe: Ian
Kris: In ISO20022 there are two groups looking at APIs
1) JSON for serialization
2) Leveraging ISO 20022 to model REST-ful APIs
scribe: our initial (ambitious)
deadline is early 2017
... the JSON group is looking at how to go from
XML->JSON->XML
... the reason to be able to round-trip is not (IMHO) clear to
me
<jheuer> *can't seem to connect to the voice call... still trying
scribe: the modeling guidelines group, on the other hand, is meeting weekly since it's more complex how to model a REST API in an ISO 20022 environment
<manu> https://www.w3.org/TR/webpayments-http-api/
<manu> https://www.w3.org/TR/webpayments-http-messages/
scribe: ISO 20022 does not define notions of resource and representation, so there would need to be some alignment there.
Manu: Some questions asked about the utility of the HTTP API ...
<Zakim> manu, you wanted to ask how this overlaps with HTTP API in Web Payments and if there is a desire to collaborate on that?
Manu: it sounds like your work
overlaps with HTTP API
... would it make sense to collaborate on this?
Kris: I think HTTP API may be
close to what is going on in ISO 20022
... I can include you in the documents that we are working on
(on how to design ISO 20022 APIs)
... what is key to us is that the resources we define are
understandable to others
... I would imagine it would be interesting to see whether w3c
could use ISO 20022 components to define a resource, and to see
whether W3C wants to create new components or provide mappings
to existing components
<jheuer> *finally! Now I can hear you.
<Zakim> manu, you wanted to ask about Open Banking API and PSD2 and ISO 20022 RESTful APIs
manu: What is relationship of ISO
work to Open Banking API and PSD2?
... it sounds to me like there is overlap
Kris: As far as what ISO 20022
covers, W3C web payments is "on the edge."
... this is really between consumer and merchant
... what is between merchant and bank is not really part of ISO
20022
... between corporates and banks, yes, and real time
payments
... but the edge of ISO 20022 is moving
... ultimately, however, even if not "really" part of ISO
20022, most of what's happening in W3C will at some point end
up in ISO 20022
... even if not the messages, then interop between the
components would be useful
<dezell> Two topics: 1) JSON in place of XML could be either simple mapping, or schema-to-schema mapping. 2) use of API design in ISO 20022. This is a more interesting area for HTTP APIs.
Kris: if the components defined
in web payments are close to what ISO 20022 has defined, then
mapping will be easier
... if you have an account, for example, then the properties of
an account should be found similarly in any context
... for PSD2 there are new players...they also will require new
flows, and those flows will be ISO 20022 flows
... For, PSD2 it is very political as well
... and so it may be more difficult to achieve interop
... Open Banking is claiming to be PSD2 compliant
<jyrossi> +1 to what Kris explains, for both practical reasons and regulatory considerations as far as the EU is concerned
Kris: and some EBA initiatives
similarly are making that claim.
... they are all linked regarding business semantics
... whether they will use identical Apis in all circumstances
-- I don't think so
<Zakim> dezell, you wanted to mention "secured data" in ATICA
dezell: There are two other
things I wanted to mention
... recent meeting in Tampa - new group for semantic cataloging
of elements
... this is something that we (in the IG) have discussed - the
potential usefulness of a semantic map on the ISO 20022
elements
... another point: ATICA
... they are talking about secured data
... frequently personally identifying information
kris: What needs to be done is
(1) W3C could define components used in web payments, and
push/align upstream to ISO 20022
... it's easy to submit new components
... for existing components we can list synonyms
<ShaneM> +1 to synonyms
Kris: to get components added to the registry, it's a matter of weeks
<manu> https://www.w3.org/community/digitaloffers/
ltoth: We've had 1 meeting since
WPIG last met
... we are reviewing the charter and problem statements
... GS1 did a project review on their 8112 (database
project)
... we are looking at what's out there, and engaging with new
participants.
... and exciting story to help motivate people to get
involved
<Zakim> dezell, you wanted to talk a little about 8112.
<ShaneM> Noon eastern
ltoth: next digital offers meeting at noon ET today
https://www.w3.org/Payments/IG/wiki/Vision2017
<manu> ian: A quick note - At our f2f meeting in Lisbon, Ian volunteered to start a task force and work on refreshing our IG vision.
<manu> ian: I've been thinking on this document, listing goals for the IG and a timeline, some notes on deliverables, first thing is to convene people in January to develop a proposal, a few components, revising vision, work priorities for 2017
<manu> Ian: it would be good to project manage the IG a bit more so we feel a bit more focused and like we're accomplishing things in a timeframe that all of us understand. It helps drive things.
<manu> Ian: Just a heads up that I'll be doing some scheduling for January calls.
<manu> Ian: Further announcements will go out via the mailing list.
Manu: The Director put a draft WG charter to the W3C Membership
<manu> https://www.w3.org/2002/09/wbs/33280/VCWG/
draft charter -> https://www.w3.org/2017/vc/charter
scribe: in review until 15
January 2017
... a fair amount of discussion is happening within the w3c
membership (on their mailing list)
dezell: I ask people to weigh in there, especially if there is confusion about process
dezell: In Lisbon I took an action to write up a communications piece / design document
IJ: Let's drop your action item
<manu> Ian: Can we work on Comms in the Vision Task Force?
dezell: Ok, I will bring ideas to
that task force
... JYR and I will talk about mapping document / regulatory
landscape soon
9 January
<manu> Happy Holidays and New Year to all! :)
<Zakim> Ian, you wanted to ask question about that
Cheers all!