Summary In this short course we explore how some programming languages, data formats, database API’s and web frameworks handle hierarchical classes. Content Object-oriented programming and techniques (OOP) such as using classes and inheritance are common in many application programming environments but alas don’t “travel well” outside computer memory. The potentially intricate relationships of objects (both the data they hold and the meaning and possible uses of the data) are not easy to transfer (except of-course by full replication of code and data).
The GSOC 2021 collaboration between Open Risk and the Hydra Ecosystem - Project Wrap-Up Google Summer of Code 2021 came and went amid the still ongoing worldwide pandemic experience. Open Risk was happy to join forces with the Hydra Ecosystem in exploring a proof-of-concept for next generation API’s using Hydra. The project aimed to guide students (here and here) to build a hypermedia enabled REST service that can serve standardized credit portfolio data.
A GSOC 2021 summer project collaboration between Open Risk and the Hydra Ecosystem Summer is underway and for the Google Summer of Code 2021 season Open Risk is happy to join forces with the Hydra Ecosystem. The project aims to guide students to build a hypermedia enabled REST service around standardized credit portfolio data. More specifically the project will build a REST service as backend for a hypothetical banking entity that collects and disseminates credit portfolio data conforming to an established public standard (the EBA NPL templates, see below).
Semantic Web Technologies integrate naturally with the worlds of open data science and open source machine learning, empowering better control and management of the risks and opportunities that come with increased digitization and model use The ongoing and accelerating digitisation of many aspects of social and economic life means the proliferation of data driven/data intermediated decisions and the reliance on quantitative models of various sorts (going under various hashtags such as machine learning, artificial intelligence, data science etc.
Course Content This CrashCourse is an introduction to semantic data using Python. It covers the following topics: We learn to work with RDF graphs using rdflib We explore the owlready package and OWL ontologies We look into json-ld serialization of RDF/OWL data We try data validation using pySHACL We use throughout a realistic data set based on the Credit Ratings Ontology Who Is This Course For The course is useful to:
The Non-Perfoming Loan Ontology The Non-Performing Loan Ontology is a framework that aims to represent and categorize knowledge about non-performing loans using semantic web information technologies. Codenamed NPLO, it codifies the relationship between the various components of a Non-Performing Loan portfolio dataset.(NB: Non-performing loans are bank loans that are 90 days or more past their repayment date or that are unlikely to be repaid, for example if the borrower is facing financial difficulties).
The Risk Function Ontology The Risk Function Ontology is a framework that aims to represent and categorize knowledge about risk management functions using semantic web information technologies. Codenamed RFO codifies the relationship between the various components of a risk management organization. Individuals, teams or even whole departments tasked with risk management exist in some shape or form in most organizations. The ontology allows the definition of risk management roles in more precise terms, which in turn can be used in a variety of contexts: towards better structured actual job descriptions, more accurate description of internal processes and easier inspection of alignement and consistency with risk taxonomies.
openNPL 0.2 release The open source openNPL platform supports the management of standardized credit portfolio data for non-performing loans. In this respect it implements the detailed European Banking Authority NPL loan templates. openNPL aims to be at the same time easy to integrate in human workflows (using a familiar web interface) and integrate into automated (computer driven) workflows. The latest (0.2) release exposes a REST API that offers machine oriented access using, what is by now, the most established mechanism for achieving flexible online data transfers.
Making Open Risk Data easier In an earlier blog post we discussed the promise of Open Risk Data and how the widespread availability of good information that is relevant for risk management can substantially help mitigate diverse risks. The list of Open Risk Data providers, particularly from public sector, keeps increasing and we are aiming to document all available datasets in the dedicated page of the Open Risk Manual. The trailblazing Wikidata project In this post we want to introduce another facility, an online database that allows the (relatively) easy publication of structured risk data.
Semantic Web Technologies The Risk Model Ontology is a framework that aims to represent and categorize knowledge about risk models using semantic web information technologies. In principle any semantic technology can be the starting point for a risk model ontology. The Open Risk Manual adopts the W3C’s Web Ontology Language (OWL). OWL is a Semantic Web language designed to represent rich and complex knowledge about things, groups of things, and relations between things.
Extending the Open Risk API to include the EBA Portfolio Data Templates The Open Risk API provides a mechanism to integrate arbitrary collections of risk data and risk modelling resources in the context of assessing and managing financial risk. It is based on two key technologies of the modern Web, RESTful architectures and Semantic Data. OpenNPL, the credit portfolio management platfrom we launched recently fully integrates the latest versions of the Open Risk API.
From Big Data, to Linked Data and Linked Models The big data problem: As certainly as the sun will set today, the big data explosion will lead to a big clean-up mess How do we know? It is simply a case of history repeating. We only have to study the still smouldering last chapter of banking industry history. Currently banks are portrayed as something akin to the village idiot as far as technology adoption is concerned (and there is certainly a nugget of truth to this).
Open Risk API If you work in financial risk management you will most likely recognize where the following sentence is coming from: One of the most significant lessons learned from the global financial crisis that began in 2007 was that banks information technology (IT) and data architectures were inadequate to support the broad management of financial risks. This had severe consequences to the banks themselves and to the stability of the financial system as a whole For those lucky few risk managers not being affected by inadequate IT systems, the excerpt is from the Basel Committee’s Principles for effective risk data aggregation and risk reporting (2013).