<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<style type="text/css">.style1 {font-family: "Times New Roman";}</style></head><body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Hi all, I’m hoping that you all don’t think Yodlee is one of the two. If so, I’d like to learn more about this. I’d also like to see if we can help shine more
light on this with the ACCC, perhaps via FDATA AU/NZ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Kind Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Brian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Openid-specs-fapi <openid-specs-fapi-bounces@lists.openid.net>
<b>On Behalf Of </b>Nicholas Irving via Openid-specs-fapi<br>
<b>Sent:</b> Monday, April 20, 2020 7:13 PM<br>
<b>To:</b> Financial API Working Group List <openid-specs-fapi@lists.openid.net><br>
<b>Cc:</b> Nicholas Irving <nirving@darkedges.com><br>
<b>Subject:</b> Re: [Openid-specs-fapi] Australian CDR Concurrent Consent<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:red">External email, verify before opening attachments or links.<br>
<br>
</span><o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">You have hit the nail on the head with your last comment, as that is something I have felt from the beginning. I would prefer standards over commercial but it seems they are being lead by people concerned with selling their products and
it shone through in a number of meetings. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Also the architects solve problems by making it the implementors problem, without thinking about the impact to existing systems.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Nicholas<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, 21 Apr 2020, 11:32 Stuart Low via Openid-specs-fapi, <<a href="mailto:openid-specs-fapi@lists.openid.net">openid-specs-fapi@lists.openid.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Hi there,<br>
<br>
The Australian Data Standards Body has released an updated concurrent<br>
consent proposal here:<br>
<a href="https://github.com/ConsumerDataStandardsAustralia/standards/files/4490840/Decision.99.-.Concurrent.Consent.pdf" target="_blank">https://github.com/ConsumerDataStandardsAustralia/standards/files/4490840/Decision.99.-.Concurrent.Consent.pdf</a><br>
<br>
Despite submissions from numerous participants including the FAPI WG the<br>
DSB seems to be determined to adopt their own untested approach to<br>
consent management while acknowledging it will be unsuitable for known<br>
future requirements. The proposals put forward by the FAPI WG have been<br>
"considered" but not adopted for either unspecified reasons or due to<br>
their "draft" status which is ironic since the proposal from the DSB<br>
appears to be not only draft in nature but by and large not yet<br>
implemented by participants.<br>
<br>
The vendor landscape within Australia is quite limited but the two<br>
primary parties involved are both OIDF members. It remains to be seen as<br>
to whether they will prioritise commercial benefit over international<br>
standards alignment.<br>
<br>
Stuart<br>
<br>
<br>
_______________________________________________<br>
Openid-specs-fapi mailing list<br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
<br><br></body></html>