Replies: 5 comments 10 replies
-
From my side: Business Problem that is trying to solve Expected features to demo at the end of the event Apps, systems, projects, technologies, libraries and datasets that could be used
Code and other existing resources that may be relevant |
Beta Was this translation helpful? Give feedback.
-
From Finsamble: Enhance Chat Integration with Contextual Transformation Success Criteria:
|
Beta Was this translation helpful? Give feedback.
-
For Open Reg Tech: We left part of the LCR unfinished to gain experience with open-source collaboration on a regulation. There are two main items to be finished:
Success Criteria |
Beta Was this translation helpful? Give feedback.
-
From algoritimca.ai : In the context of the new EU Securitisation Regulation, NON-EU originators and / or NON-EU specialist reporting providers now have to report loan-level data using ESMA templates if they want to sell securities to EU investors. See here more info. Some US GSE (agency) transactions are already being mapped to ESMA templates (see here). This is going to be even more relevant for non-agency transactions, which rely more on the EU investors base. The problem is that non-agency transactions come with custom loan-level data templates (i.e. every bank has its own loan-level data "standard"). Each of them will have to translate their custom templates to the ESMA one and apply rule checks to make sure that the "transformation" worked well (we can provide an example of rule checks that every US bank will have to implement eventually). The data has to be of high-quality because it is used by the investor for due diligence (before closing) and monitoring (after transaction closing). I simply suggest writing open source connectors and rule checks code: by being open source, the community could double check the mappings (from custom to standard), suggest reviews, as well as add new data quality rule checks (e.g. Interest rate > 0 but < 20). |
Beta Was this translation helpful? Give feedback.
-
a couple of ideas
|
Beta Was this translation helpful? Give feedback.
-
During today's TSC, we had an interesting conversation around sample use cases, to share ahead of time with registrants and give them a clearer idea of what could be built, or an inspiration to come up with their own use case to build.
I'm listing below the comments I grabbed from the meeting chat:
I'd kindly ask the TSC to add a bit more content (3-4 paragraphs) describing:
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions