# Normalising Common Components To achieve standardisation across products and asset classes, the CDM identifies logical components that fulfil the same function and normalises them, even when those components may be named and treated differently in the context of their respective markets. We followed the CDM design principle of normalising concepts such as quantity, price and party in the representation of financial transactions. The CDM identifies that, regardless of the asset class or product type, a financial transaction always involves two counterparties trading (ie buying or selling) a certain financial product in a specific quantity and at a specific price. This approach means that a single logical concept such as quantity can represent concepts that may be named and captured differently across markets: eg notional or principal amount etc. Following this approach, we took the modular components that exist in the CDM and reused concepts such as product, loan, price, collateral and party to reflect the mortgage attributes that characterised loan, borrower and collateral. We also extended the model to reflect attributes that were specific to the POC around collateral (eg property) or the credit profile of the borrower (eg credit details). ![JSON Representation of Retail Mortgage Model](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mi5wPkxf94vt5dSbr_p%2Fuploads%2FRpRNOZSRnlctcBkcT0FY%2Ffile.png?alt=media) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.bis.org/ellipse/proof-of-concept/normalising-common-components.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.