Jack Lord
Jack Lord
It would be good to have a sweep through the standard and look for consistency in our use of titles and descriptions. e.g., we for URLs we have `Source URL`...
For entities where an interested party is expected to be absent (e.g. a nation state), we may want a `not-applicable` entry in the unspecifiedReason codelist. Alternatively, the current `no-beneficial-owners` entry...
We currently have five types of entity: `registeredEntity`, `legalEntity`, `arrangement`, `anonymousEntity`, `unknownEntity`. `registeredEntity` and `legalEntity` are a source of confusion due to conflicts with their common usage in other related...
This is required in [Paraguayan law ](https://www.bacn.gov.py/leyes-paraguayas/9116/ley-n-6446--crea-el-registro-administrativo-de-personas-y-estructuras-jurdicas-y-el-registro-administrativo-de-beneficiarios-finales-del-paraguay)(and a few others I think).
Proposed codelist for agreement types, once we have implemented #336: jointShareholding nomineeShareholding bearerShares contractOrContractualJointVenture informalAgreement unknownAgreement
We have a `reason` but might also want to allow publishers to use short codelists, as with Companies House enumerations.
Publishers need to locate and disambiguate identifiers for natural persons and legal entities. - Legal identifier _lists_ can be found on org-id.guide. This includes both single-jurisdiction, canonical lists, fall-back lists...
Example of current and former ownership and control relationships coexisting: https://register.openownership.org/entities/5b16a8b89dfc3fae18f62024/graph In my experience the default behaviour of showing all relationships regardless of whether they have ended: - is a...
There are multiple classification schemes for industry classification codes. OpenCorporates presents the original classification data and a mapping between the original and other schemes, e.g. https://opencorporates.com/statements/757088716 I think that the...