https://github.com/finos/secref-data

Security Reference Data project
https://github.com/finos/secref-data

Last synced: 6 months ago
JSON representation

Security Reference Data project

• Host: GitHub
• URL: https://github.com/finos/secref-data
• Owner: finos
• License: apache-2.0
• Created: 2020-04-29T08:05:44.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2022-01-12T23:13:26.000Z (almost 4 years ago)
• Last Synced: 2024-04-12T08:19:56.580Z (almost 2 years ago)
• Language: JavaScript
• Size: 2.84 MB
• Stars: 24
• Watchers: 13
• Forks: 7
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: .github/CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
Badges go here (see [shields.io](https://shields.io/), for examples).

[![FINOS - Incubating](https://cdn.jsdelivr.net/gh/finos/contrib-toolbox@master/images/badge-incubating.svg)](https://finosfoundation.atlassian.net/wiki/display/FINOS/Incubating)



# Securities Reference Data Project 

Welcome to the Securities Reference Data project, hosted and led by [FINOS, The Fintech Open Source Foundation](https://www.finos.org). The Securities Reference Data project was launched in 2018 by FINOS member Nomura. 

The project currently has two work streams: **Securities Reference Data** and **Currency Reference Data**.

## Securities Reference Data

### Roadmap

The Securities Reference Data project aims to develop an [open source cloud-based solution to map securities and issuer IDs](https://github.com/finos/secref-data/blob/master/SecRef_%20Securities%20%26%20Issuer%20ID%20mapping_%20.pdf). Doing this once collaboratively has the potential to significantly reduce the costs and effort of maintaining this individually.

For more information see the [Securities Reference Data Roadmap](https://github.com/finos/secref-data/issues/25) .

#### Background

There are a range of trade identifiers used across financial services (ISIN, CUSIP, SEDOL, LEI, FIGI, RIC, BBID and many more) that serve a number of purposes, from validating the integrity of a security to providing common identifiers used during trading and settlement. The majority are either fully or partially “closed" codes, although there are some initiatives that are partially or fully open, like FIGI and OpenCorporates.

However, no single code covers all securities, while individual securities may be represented by multiple identifiers and the granularity of coverage at entity vs. corporate level also varies. This often necessitates costly and error prone mapping across identifiers. The extent of the problem is greater in some asset classes than others and certainly more prominent within the OTC market.

Additionaly, the existence of regionally focused bodies/companies responsible for issuing the identifiers and, in come cases, requiring licenses to access them contributes to the problem, as they minimize the possibility of consolidation onto one identifier, causing delays and reducing transparency. All of these factors impact market efficiency and contribute to trade breaks and errors.

### Get Involved: Contribute to SecRef Data

There are several ways to get involved in SecRef Data:

* **Contribute code** or contribute to **building the mapping table**: reach out to data-tech-sec-ref@finos.org expressing your interest in contributing or [raise an issue](https://github.com/finos/secref-data/issues/new/choose)

* **Contribute use cases** at https://github.com/finos/secref-data/issues/33 

* **Join the mailing list**

Communications for the Securities Reference Data project are conducted through the data-tech-sec-ref@finos.org mailing list. Please email [data-tech-sec-ref+subscribe@finos.org](mailto:data-tech-sec-ref+subscribe@finos.org) to join the mailing list.

All Securities Reference Data project collaboration activities, including [meeting minutes](https://github.com/finos/secref-data/issues?q=label%3Ameeting+),are hosted on this SecRef Data GitHub repo. Activities prior to July 2020 can be found in the Securities Reference Data project [archive](https://finosfoundation.atlassian.net/wiki/spaces/DT/pages/656834673/Security+Reference+Data+Project).  For more information about FINOS project materials and communication, please review the [FINOS Governance](https://github.com/finos/community/blob/master/governance/Collaborative-Principles.md).

## Currency Reference Data 

The Security Reference Data project hosted a work stream on Currency Reference Data until January 2022. Currency Reference Data was [proposed and set up](https://github.com/finos/community/issues/136) as a separate FINOS project. See https://github.com/finos/curref-data for Currency Reference Data information, resources and collaboration materials.

## Contributing

1. Fork it ()

2. Create your feature branch (`git checkout -b feature/fooBar`)

3. Read our [contribution guidelines](.github/CONTRIBUTING.md) and [Community Code of Conduct](https://www.finos.org/code-of-conduct)

4. Commit your changes (`git commit -am 'Add some fooBar'`)

5. Push to the branch (`git push origin feature/fooBar`)

6. 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. 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 [help@finos.org](mailto:help@finos.org)*

## License

Copyright 2020 {name of copyright owner}

Distributed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0).

SPDX-License-Identifier: [Apache-2.0](https://spdx.org/licenses/Apache-2.0)