<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">We’ve talked for a long time about providing some advice around FAPI, and it was something that came up again on the 3rd July call.<br class=""><br class=""></div><div class="">Given that more ecosystems are looking into FAPI, there is some urgency to ensure any lessons learned so far are easily found by others, and hence I’ve had a very quick go at starting such a document and covering a handful of the points we’ve previously discussed covering in such a document.<br class=""><br class=""></div><div class="">I’m happy for feedback in any form; I’ve arbitrarily made a range of decisions many of which may need to be revisited, but if I’m close enough to the mark I’d suggest adopting / merging this so it can be further refined and added to by the working group members.</div><div class=""><br class=""></div><div class="">The document can be viewed/commented on here:</div><div class=""><br class=""></div><div class=""><a href="https://bitbucket.org/openid/fapi/pull-requests/129/first-cut-of-an-advice-document/diff" class="">https://bitbucket.org/openid/fapi/pull-requests/129/first-cut-of-an-advice-document/diff</a></div><div class=""><br class=""></div><div class="">And there’s a more readable form viewable here:</div><div class=""><br class=""></div><div class=""><a href="https://bitbucket.org/josephheenan/fapi/src/edce6adee86b16f5fed2ef71ce8a86f4f01dc181/Financial_API_Deployment.md" class="">https://bitbucket.org/josephheenan/fapi/src/edce6adee86b16f5fed2ef71ce8a86f4f01dc181/Financial_API_Deployment.md</a></div><div class=""><br class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Joseph</div><div class=""><br class=""></div></body></html>