Welcome to the Open Reg Tech implementation of the US Liquidity Coverage Ratio (LCR). The goal of the project is to establish the delivery and collaboration of regulations in code.
The Documentation Is a good place to read about the LCR regulation and how this project implements it.
In addition, FINOS runs a server with the Latest Interactive LCR to explore the implementation for non-technical users.
The LCR can be generated into any target language or platform supported by Morphir. See the Morphir Documentation on Generating for details on available generators.
As a convenience, this project includes configuration for generating into Scala with Maven. To use it, ensure that Maven is installed and run:
mvn buildto build a library .jar file that can be included in a Scala or Java project.
The current implementation is almost complete. We've left a small portion incomplete so that we can finish the remainder as a community. This will provide experience and insight on the experience of the community collaborating on regulations.
- Agree on the regulation (LCR)
- Contribute existing LCR implementation into a new project in FINOS (done)
- Implement the remainder of the LCR as a Open Reg Tech SIG team effort
- Decide on an execution environment (i.e., Spark)
- Enable procurement of the data with Legend
- Demonstrate the complete solution.
- Fork it (https://github.com/finos/open-reg-tech-us-lcr/fork)
- Create your feature branch (
git checkout -b feature/fooBar) - Read our contribution guidelines and Community Code of Conduct
- Commit your changes (
git commit -am 'Add some fooBar') - Push to the branch (
git push origin feature/fooBar) - Create a new Pull Request
NOTE: Commits and pull requests to FINOS repositories will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS. Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS Clabot tool (or EasyCLA). Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.
Need an ICLA? Unsure if you are covered under an existing CCLA? Email [email protected]
Copyright 2022 Fintech Open Source Foundation
Distributed under the Apache License, Version 2.0.
SPDX-License-Identifier: Apache-2.0