The Beneficial Ownership Data Standard (BODS) is an open standard providing a specification for modelling and publishing information on the beneficial ownership and control of corporate vehicles.
You can find the latest version of the schema and documentation at https://standard.openownership.org
BODS has been created by Open Ownership in partnership with Open Data Services, and is provided under an open license for re-use.
An open data standard working group of data experts, beneficial ownership specialists and other interested parties also provides advice and helps guide the development of BODS.
The working group is co-chaired by Open Ownership and Open Data Services - and anyone can apply to join the group by filling out this form. Virtual group meetings are held quarterly and communication is coordinated through a Google group.
All changes to the BODS schema and documentation take place this GitHub repo. A feature tracker is available which documents all new BODS features being researched, proposed or implemented.
Features currently on the tracker are those adopted for development by the Open Ownership and Open Data Services teams following work with implementers of beneficial ownership reforms and in consultation with the Data Standard Working Group.
However, anyone can submit a feature request ticket, contribute to a feature development ticket, or make an implementation proposal. The data standard support team at Open Ownership will consider and reply to any submitted feature requests within a month from submission.
See the project issue tracker for a list of feature requests and issues.
Please direct any correspondence to [email protected]
First, clone this repository so that you can work locally on your machine.
The frontend uses docson JavaScript library to visualise the JSON schema. BODS uses a specific patched fork of docson (which is different from the patched fork used by other standards). This is included in the data-standard repo rather than as part of the Sphinx theme because it is necessary regardless of which theme is used to build the docs. See data-standard-sphinx-theme#36 for the particulars of the patches. The situation with the various branches and patches of docson is in need of serious improvement.
Meanwhile, to include the appropriate version of docson JS after you clone this repo, you need to change directory into the cloned repository and run:
git submodule init
git submodule update
Create a Python Virtual Environment. It should be python3.9 to match our build server.
python3 -m virtualenv -p python3.9 .ve
(If you don't have python3.9 installed see here.)
Activate the virtual environment:
source .ve/bin/activate
Install Python libraries:
pip install -r requirements_test.txt
(Note if you need to change the theme you must instead use https://github.com/openownership/data-standard-sphinx-theme . If you only need to change the content, read on).
Once you have followed the installation and setup instructions above, you just need to change directory to that of your local repository and activate the virtual environement:
source .ve/bin/activate
To actually build the docs:
sphinx-build docs/ _build
To see the docs, open a new terminal window and run a development webserver:
cd _build
python3 -m http.server
Leave this command running, and you can now go to http://127.0.0.1:8000/ to see the docs.
Edit source files as needed. Return to your original window and rerun the build command above. Reload in web browser. Repeat!
To build another language, instead use this build command:
sphinx-build -D language=ru docs/ _build
Once you have followed the installation and setup instructions above, you just need to change directory to that of your local repository and activate the virtual environement:
source .ve/bin/activate
To run the tests:
pytest tests
Translation consists of generating strings to be translated from the English docs, pushing them to Transifex, fetching translations back from Transifex, and then you can build the docs in the other languages you need. There are full instructions for the translation workflow in the bods-dev-handbook.