data-standard icon indicating copy to clipboard operation
data-standard copied to clipboard

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

Results 82 data-standard issues
Sort by recently updated
recently updated
newest added

**Summary of the bug or issue** Some of the files in the examples folder (on [main](https://github.com/openownership/data-standard/tree/main/examples), but also for the 0.4 release) are incorrectly re-using recordId values for different entities....

bug

If #317 is accepted, then some of the justification for `isComponent` is removed. This issue suggests further revision of `isComponent` to remove it from `personStatement` and `entityStatement` and to consider...

schema properties
feature: change over time

Following discussion in https://github.com/openownership/lib-cove-bods/issues/123 Currently there's a normative requirement 'If an address in the addresses array is of type "alternative" then there is also another address in the array' There's...

codelist

Currently the description is "if interestedParty is a string, the interested party MAY be an entity or a person." The use of MAY here could be confusing. Clearer wording could...

schema descriptions

_[This ticket helps track progress towards developing a particular feature in BODS where changes or revisions to the standard may be required. It should be placed on the [BODS Feature...

feature: missing information

# Overview **What does this pull request do?** updates example data - componentRecords fields were listing statementIds, now they list recordIds **How can a reviewer test or examine your changes?**...

**Is your request related to a problem? Please describe.** Publishers of beneficial ownership information sometimes want to differentiate between beneficial owners themselves and professional intermediary actors (accountants, lawyers, etc...) acting...

documentation development
feature: interests

We need to adjust our ReadTheDocs configuration. Here is their announcement: >We are announcing the deprecation of Sphinx context injection at build time for all the projects. The deprecation date...

bug
documentation development
sphinx

For personType unknownPerson and entityType unknownEntity do we require an unspecifiedRecord reason? for the anonymous person/entity the codelist description includes "The reason for non-disclosure should be given in the accompanying...

feature: missing information

**Summary of the bug or issue** The description of `isComponent` is hard to follow, and I think it still contains some text/concepts from earlier version of BODS. > Whether this...

bug