Merge branch 'rosetta-models:master' into master

Author: minesh-s-patel

CDM Overview.pptx.pdf

@@ -1,13 +1,12 @@
-# _CDM Model - Modification to product condition_
+# _Infrastructure - Dependency Update_
 
 _What is being released?_
 
-Modified condition for `FpML_cd_30`
-- Addition of clause to allow `adjustedDate` check
+This release updates the `DSL` dependency.
 
-Modified condition for `Floating Rate` Option.
-- Addition of clause to allow posting of supplementary attribute `IndexReferenceInformation`
+Version updates include:
+- `DSL` 9.14.0: Support for accessing meta features after a deep feature call. For further details see DSL release notes: https://github.com/finos/rune-dsl/releases/tag/9.14.0
 
 _Review directions_
 
-The changes can be reviewed in PR: [#3035](https://github.com/finos/common-domain-model/pull/3035)
+The changes can be reviewed in PR: [#3064](https://github.com/finos/common-domain-model/pull/3064)

GOVERNANCE.md

@@ -3,3 +3,19 @@
 ![](.github/cdm-roadmap-2024-1.png)
 
 ![](.github/cdm-roadmap-2024-2.png)
+
+# 2024-5 Release schedule
+![CDM Release Guidelines Task Force Summary - July 2 2024](https://github.com/finos/common-domain-model/assets/7291088/9542593d-b63e-4447-8a21-cfec1df65221)
+
+Release States
+===============
+Release states are defined as follows:
+* Development – versions that include new designs from the “main” branch that are still under development.  All tests must pass but the model may continue to evolve before being released into production.
+* Production - the "latest and greatest" stable version that ideally everyone should upgrade to, and where enhancements compatible with the existing models will be included. We should aim for a release to be in Production for around a year if we can, to alleviate upgrade costs to consumers. 
+* Maintenance – when a new Production version is released then the current Production will go into Maintenance. Only critical bug fixes and changes related to critical regulatory requirements should be ported to Maintenance releases. Otherwise, functional changes would not be ported to maintenance releases.  The intention would be to have only 1 version at a time in maintenance, so each time a new Production version drops, the previous Maintenance release would go to Unsupported.
+* Unsupported/End of Life – There will be no bug fixes or other support for the version.  TBD: We may perform security scans on some more recent unsupported versions and report any identified vulnerabilities, but will not perform security remediations.
+
+  
+At any point we want a maximum of 1 centrally supported development version, 1 production version, and one maintenance version.
+
+

RELEASE.md

@@ -125,7 +125,7 @@ steps:
             python3 -m pip wheel --no-deps --only-binary :all: --wheel-dir ./rosetta-source/target/classes/cdm/python ./rosetta-source/target/classes/cdm/python
           - python3 -m pip install ./rosetta-source/target/classes/cdm/python/python_cdm-*-py3-none-any.whl
           - python3 -m pip install pytest
-          - pytest -p no:cacheprovider ./cdm-python/test/
+#          - pytest -p no:cacheprovider ./cdm-python/test/
 
   DeployDaml:
     stage: 'build'

ROADMAP.md

@@ -2,6 +2,10 @@
 title: CDM Collateral Working Group
 ---
 
+## Common Domain Model Collateral Start-Up Guide
+
+ISDA has also launched the Get Started with the CDM for Collateral Guide! You can now access a wealth of resources and tutorials on CDM for collateral management on the [CDM-Collateral Initiatives page](https://www.isda.org/2023/02/16/isda-collateral-initiatives/).
+
 ## Overview
 
 The Collateral Working Group plays a pivotal role in the CDM ecosystem by providing a robust framework for harmonizing data and processes related to collateral flows and documentation.

codefresh.yml

@@ -45,7 +45,9 @@ needs to be added to the project pom.xml:
 
 > _NOTE:_ All current CDM dependencies are available in Maven Central.
 > For CDM releases prior to version 4.0.0 the dependencies can be found in the ISDA repository: <artifactregistry://europe-west1-maven.pkg.dev/production-208613/isda-maven>
-> Add the following two snippets to the `<build>` and `<repositories>` sections of your project `pom.xml`:
+> Add the following two snippets to the `<build>` and `<repositories>` sections of your project `pom.xml`.
+> You can also use the `https` protocol instead of `artifactregistry`.
+> If you do this then the `<build>` extension is not necessary.
 >
 > ``` xml
 >

docs/CDM-Collateral-WG.md

@@ -0,0 +1,64 @@
+---
+title: Common Domain Model Materials
+---
+
+Explore More Resources and Videos on the Common Domain Model in the [FINOS Resource Center](https://resources.finos.org/category/projects-sigs/common-domain-model-cdm?projects-sigs=common-domain-model-cdm&c=cG9zdDo5OTEwNzc%3D)
+
+## COMMON DOMAIN MODEL IN THE NEWS 
+### [CDM: data standardisation across the trade lifecycle](https://www.securitiesfinancetimes.com/sltimes/SFT_issue_324.pdf)
+
+SFT examines what comes next on the Common Domain Model project agenda. Read more about the benefits of CDM adoption include reduced reconciliation burdens and lower risk of settlement failures. The CDM available in FINOS as open source, broadening the base of CDM contributors. Future work includes applying CDM to collateral management and further automating processes like collateral calculation and interest processing.
+
+### [Six major banks trial Fragmos Chain in OTC derivatives market](https://www.finextra.com/pressarticle/100503/six-major-banks-trial-fragmos-chain-in-otc-derivatives-market)
+
+Fragmos Chain successfully trialed its innovative post-trade processing platform for OTC derivatives with six major banks, achieving trade confirmations within an average of 6 minutes. The platform's use of R3 Corda's Distributed Ledger Technology and the Common Domain Model ensured seamless interoperability and efficiency, receiving high praise for handling complex trades. 
+
+### [Fintech Open-Source Foundation (FINOS) Chosen to Support Community Around Common Domain Model from ISLA, ISDA, ICMA](https://www.crowdfundinsider.com/2022/09/195862-fintech-open-source-foundation-finos-chosen-to-support-community-around-common-domain-model-from-isla-isda-icma/)
+
+In this article, Crowdfund Insider discussed the appointment of FINOS as the host of CDM. Viewed as a milestone in promoting open and common standards in financial markets and praised FINOS for its potential to accelerate the adoption of CDM and bring greater consistency across the industry.
+
+### [FINOS Launches Common Domain Model](https://www.accesswire.com/viewarticle.aspx?id=739516)
+
+In February 2023, FINOS announced the launch of the Common Domain Model, which aims to to become the industry standard for digital regulatory reporting. The CDM streamlines and automates various lifecycle events and processes related to open repos, evergreens, and floating rate repos - ultimately reducing costs and improving sustainability in regulatory compliance by mutualizing regulatory reporting. The journey towards implementing the CDM is a significant step towards real-world industry implementation of digital regulatory reporting and compliance. See the press coverage here securitiesfinancetimes and FINADIUM.
+
+
+## CDM RESOURCES
+### [A discussion of "The Future of the Securities Lending Market: An Agenda for Change"](https://www.finos.org/blog/the-future-of-securities-lending-market)
+
+ISLA published a paper entitled ‘The Future of the Securities Lending Market | An Agenda for Change’ in September 2019, looking at the conjunction of market complexity, technical architecture and regulatory impacts. The conclusion reached was that a transformation was overdue and the solution would be underpinned by common standards.
+
+### [CDM Now Available In Python](https://www.finos.org/blog/cdm-now-available-in-python)
+
+A recent contribution to the CDM project makes it available in the Python programming language for the first time, which will allow a new community of developers to use the CDM in their projects.
+
+### [Common Domain Model into Open Source at FINOS](https://www.finos.org/hubfs/Accepted%20FINOS%20Edits_%20Common%20Domain%20Model%20into%20Open%20Source%20at%20FINOS.docx.pdf)
+
+Read more about CDM's journey into open source, project contribution guidelines, principles, and frequently asked questions.
+
+### [Barclays demonstration of interest rate swap processing using the Common Domain Model (CDM)](https://www.youtube.com/watch?v=LTWn_AWC4F8)
+
+In this recording, Barclays introduces a prototype for processing interest rate swaps using the common domain model. Starting with how the post-trade industry in capital markets has evolved over time, resulting in procedural inefficiencies that are complex, duplicative, and costly to maintain. The common domain model covers processes, events, and data, and Barclays prototype aims to showcase the potential of this new standard in revolutionizing the post-trade industry. 
+
+### [ISLA, ICMA & ISDA Appoint FINOS for CDM Repository](https://www.islaemea.org/press-releases/isla-icma-isda-appoint-finos-for-cdm-repository/)
+
+On Thursday, September 8th, 2022, three leading organizations in the financial industry, International Securities Lending Association (ISLA), International Capital Market Association (ICMA), and International Swaps and Derivatives Association (ISDA), made a major announcement appointing FINOS to provide a repository for the Common Domain Model (CDM) with the aim of fostering growth in the open-source community.
+
+### [2022 Open Source in Finance Forum New York Keynote Panel: Common Domain Model (CDM)](https://resources.finos.org/content/keynote-panel-common-domain-model-cdm/?projects-sigs=common-domain-model-cdm)
+
+At the keynote session of the 2022 Open Source in Finance Forum New York, a panel of industry leaders including Adrian Dale of ISLA, Alan Milligan of ISDA, and Georgina Jarrett, joined moderator Ffion Acland of Goldman Sachs to delve into the exciting topic of trade association collaboration, open sourcing, and the creation of a common domain for the market, built by the market. 
+
+### [Looking Backwards & Forwards at CDM: History of the Common Domain Model…](https://resources.finos.org/content/looking-backwards-forwards-at-cdm-history-of-the-common-domain-model/?projects-sigs=common-domain-model-cdm)
+
+The first portion of the one-hour CDM presentation at the 2022 NYC Open Source in Finance Forum featured a panel of distinguished industry leaders, including Ian Sloyan of ISDA, David Shone of ISLA, Gabriel Callsen of ICMA, and Amy Caruso of ISDA. The panel came together to provide a comprehensive overview of the history of Common Domain Model (CDM) and its evolution. The experts shared their insights on where CDM has come from and where it's headed in the future, offering valuable perspectives on the role of CDM in shaping the future of finance.
+
+### [Implementing CDM: How is it Done, Why is it Beneficial to Financial Markets Infrastructure?](https://resources.finos.org/content/implementing-cdm-how-is-it-done-why-is-it-beneficial-to-financial-markets-infrastructure/?projects-sigs=common-domain-model-cdm)
+
+The second half of the one-hour CDM presentation at the Open Source in Finance Forum (OSFF) in New York was dedicated to exploring the potential of Common Domain Model (CDM) in market infrastructure. A panel of experts, including Jon Nance of Axoni, Dianne Boyle of Symbiont, Sunil Challa of Credit Suisse, and Eleonora Acuna of ISDA, came together to delve into the possibilities of CDM in the real world. They discussed the practical applications and potential of CDM, offering valuable insights into the future of this exciting technology.
+
+### [FINOS on what’s next for CDM and open source trends](https://finadium.com/sfm-interview-finos-on-whats-next-for-cdm-and-open-source-trends/)
+
+On January 11th, 2023, FINADIUM sat down with Gabriele Columbro, the Executive Director at FINOS and General Manager of the Linux Foundation Europe, to discuss the exciting world of open source trends in financial services. During the conversation, Gabriele shared his insights on what to expect in the coming months and years and provided a broad overview of the overarching open source trends in the financial services industry.
+
+### [ISDA Digital Reporting](https://resources.finos.org/content/isda-digital-reporting/?projects-sigs=common-domain-model-cdm) 
+
+ISDA's Digital Regulatory Reporting provides a comprehensive solution for translating amended rules into machine-executable open-source code. This allows financial firms to access a standardized interpretation of the requirements and integrate them directly into their systems, streamlining their regulatory reporting processes and reducing the risk of compliance errors. With ISDA's Digital Regulatory Reporting, financial institutions can stay ahead of the regulatory curve and easily implement the latest industry standards and requirements.

docs/cdm-guidelines.md

@@ -15,7 +15,13 @@ and machine-executable blueprint for how financial products are traded
 and managed across the transaction lifecycle. It is represented as a
 [domain model](https://olegchursin.medium.com/a-brief-introduction-to-domain-modeling-862a30b38353) and distributed in open source.
 
-For an overview of the Common Domain Model, a comparative analysis with FpML, an exploration of the CDM's historical development and events, as well as insights into its further applications, including its role in the ecosystem and support for smart contract technology, we recommend reviewing the [CDM Overview deck](/pdfs/CDM-Overview.pdf).
+For an overview of the Common Domain Model, a comparative analysis with FpML, an exploration of the CDM's historical development and events, as well as insights into its further applications, including its role in the ecosystem and support for smart contract technology, we recommend reviewing the [CDM Overview deck](/pdfs/CDM-Overview.pdf). 
+
+ISDA’s Digital Regulatory Reporting (DRR) solution leverages the open-source Common Domain Model (CDM) to convert industry-agreed interpretations of new or amended regulatory reporting rules into clear, machine-executable code. This approach enhances implementation efficiency and reduces costs. Institutions contributing to the development of the ISDA DRR include (but are not limited to) those listed on [ISDA’s Digital Regulatory Reporting Page](https://www.isda.org/isda-digital-regulatory-reporting/).
+
+ISDA has also launched the Get Started with the CDM for Collateral Guide! You can now access a wealth of resources and tutorials on CDM for collateral management on the [CDM-Collateral Initiatives page](https://www.isda.org/2023/02/16/isda-collateral-initiatives/).
+
+If you’re interested in the Common Domain Model (CDM), please complete the [CDM Interest Form](https://www.finos.org/common-domain-model) to join our mailing list. By signing up, you’ll receive updates on CDM initiatives, meeting agendas, and other working group activities.
 
 ## Purpose
 
@@ -186,3 +192,4 @@ file in the CDM jar.
 
 For more details, please follow the
 [CDM Java Distribution Guidelines](/docs/cdm-guidelines).
+

docs/cdm-materials.md

@@ -18,6 +18,6 @@ In each section, selected examples of model definitions are used as
 illustrations to help explain each dimension and include, where
 applicable, data samples to help demonstrate the structure.
 
-The CDM is expressed in a language called the Rosetta DSL. All the
+The CDM is expressed in a language called the Rune DSL. All the
 language components used by the CDM including types, functions and
-annotations are described in the [Rosetta DSL Documentation](https://docs.rosetta-technology.io/rosetta/rosetta-dsl/rosetta-modelling-component).
+annotations are described in the [Rune DSL Documentation](https://docs.rosetta-technology.io/rosetta/rosetta-dsl/rune-modelling-component).

docs/cdm-overview.md

@@ -35,7 +35,9 @@ the following dependency needs to be added to the project pom.xml:
 
 > _NOTE:_ All current CDM dependencies are available in Maven Central.
 > For CDM releases prior to version 4.0.0 the dependencies can be found in the ISDA repository: <artifactregistry://europe-west1-maven.pkg.dev/production-208613/isda-maven>
-> Add the following two snippets to the `<build>` and `<repositories>` sections of your project `pom.xml`:
+> Add the following two snippets to the `<build>` and `<repositories>` sections of your project `pom.xml`.
+> You can also use the `https` protocol instead of `artifactregistry`.
+> If you do this then the `<build>` extension is not necessary.
 >
 > ``` xml
 >

docs/common-domain-model.md

@@ -285,12 +285,20 @@ type Transfer extends TransferBase:
 
 ``` Haskell
 type TransferBase:
-  identifier Identifier (0..*)
-    [metadata scheme]
-  quantity NonNegativeQuantity (1..1)
-  observable Observable (0..1)
-  payerReceiver PartyReferencePayerReceiver (1..1)
-  settlementDate AdjustableOrAdjustedOrRelativeDate (1..1)
+    identifier Identifier (0..*)
+        [metadata scheme]
+    quantity NonNegativeQuantity (1..1)
+    asset Asset (1..1)
+    payerReceiver PartyReferencePayerReceiver (1..1)
+    settlementDate AdjustableOrAdjustedOrRelativeDate (1..1)
+
+    condition QuantityUnitExists:
+        if asset -> Cash exists
+        then quantity -> unit -> currency exists
+        else if asset -> Commodity exists
+        then quantity -> unit -> capacityUnit exists
+        else if asset -> Instrument exists
+        then quantity -> unit -> financialUnit exists
 ```
 
 ## Primitive Operator {#primitive-event}

docs/download.md

@@ -21,6 +21,7 @@ Welcome to CDM documentation !
     - [Pre-trade Processing](/docs/pre-trade-processing)
 * [CDM Java Distribution Guidelines](/docs/cdm-guidelines)
 * [Development Guidelines](/docs/contribution)
+* [CDM Materials](/docs/cdm-materials)
 * [Get Involved](/docs/get-involved)
     - [Join the Contribution Review Working Group](/docs/CDM-Contribution-Review-WG)
     - [Join the Collateral Working Group](/docs/CDM-Collateral-WG)

docs/event-model.md

@@ -755,29 +755,30 @@ func ResolvePerformanceObservationIdentifiers:
         identifiers ObservationIdentifier (1..1)
 
     alias adjustedFinalValuationDate:
-        ResolveAdjustableDate( payout -> valuationDates -> finalValuationDate -> valuationDate)
+        ResolveAdjustableDate( payout -> valuationDates -> finalValuationDate -> valuationDate )
 
-    alias valuationDates:
-        if adjustedDate < adjustedFinalValuationDate then
-            payout -> valuationDates -> interimValuationDate
-        else
-            payout -> valuationDates -> finalValuationDate
+    alias valuationDates: 
+        if adjustedDate < adjustedFinalValuationDate
+        then payout -> valuationDates -> interimValuationDate
+        else payout -> valuationDates -> finalValuationDate
 
-    add identifiers -> observable -> productIdentifier:
-        payout -> underlier -> security -> productIdentifier
+    add identifiers -> observable -> asset -> Instrument -> Security -> identifier: 
+        payout -> underlier -> security -> identifier 
 
-    set identifiers -> observationDate:
-        AdjustedValuationDates( payout -> valuationDates )
+    set identifiers -> observationDate: 
+        AdjustedValuationDates(payout -> valuationDates)
             filter item <= adjustedDate
             then last
 
-    set identifiers -> observationTime:
-        ResolvePerformanceValuationTime(valuationDates -> valuationTime,
-            valuationDates -> valuationTimeType,
-            identifiers -> observable -> productIdentifier only-element,
-            valuationDates -> determinationMethod )
+    set identifiers -> observationTime: 
+        ResolvePerformanceValuationTime(
+                valuationDates -> valuationTime,
+                valuationDates -> valuationTimeType,
+                identifiers -> observable -> asset ->> identifier only-element,
+                valuationDates -> determinationMethod
+            )
 
-    set identifiers -> determinationMethodology -> determinationMethod:
+    set identifiers -> determinationMethodology -> determinationMethod: 
         valuationDates -> determinationMethod
 ```