Property talk:P10083

Latest comment: 3 years ago by Germartin1 in topic Why not persons?

Documentation

Offshore Leaks Database ID
identifier in the International Consortium of Investigative Journalists' Offshore Leaks Database
Associated itemOffshore Leaks Database (Q108935620)
Applicable "stated in" valueOffshore Leaks Database (Q108935620)
Has qualitynumeric identifier (Q93868746)
Data typeExternal identifier
Domainorganization (Q43229) or human (Q5)
Allowed values[1-9]\d*
ExampleStLaurent Holdco (Q94640530)55057488
Prague Property Holding (BVI) (Q104223936)82009630
Andrej Džupina (Q10819957)56077992
56101888
Sourcehttps://offshoreleaks.icij.org
Formatter URLhttps://offshoreleaks.icij.org/nodes/$1
Lists
Proposal discussionProposal discussion
Current uses
Total343
Main statement33998.8% of uses
Qualifier41.2% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “organization (Q43229), human (Q5): item must contain property “instance of (P31)” with classes “organization (Q43229), human (Q5)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10083#Type Q43229, Q5, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10083#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10083#Single value, SPARQL
Format “[1-9]\d*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10083#Format, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10083#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10083#Entity types

Why not persons?

edit

  Notified participants of WikiProject Companies

@So9q, Jklamo, RShigapov, Skim:

Why do you think it's a problem if the same formatter is used for entities, intermediaries, officers? I actually think that's nice, and it's used in some other databases, eg VIAF and GND have a single namespace for all kinds of things.

  • I added an example for a person. Problems:
    • Officers are less deduplicated, so persons will often have several IDs. So I think we should remove the "single value constraint"
    • I failed to find a couple from https://www.icij.org/investigations/pandora-papers/power-players/ (Ali Bongo, Andrej Babiš) and Bulgaria's magnitsky-sanctioned mogul (Peevski i.e. Пеевски). I wonder if ICIJ has exported Pandora's papers data in full???
  • Extended the scope of this prop to cover both persons and organizations.
  • In my work with company data I often hit a case where I need such abstract "Agent" class: eg founder, investor, owner can be persons and organizations alike.
  • If the WD community thinks that's wrong, I'll remove those additions.

Cheers! --Vladimir Alexiev (talk) 13:25, 23 November 2021 (UTC)Reply

@Vladimir Alexiev: As this property is already created it would make more sense to discuss changes on the talk page than here. --SilentSpike (talk) 15:05, 23 November 2021 (UTC)Reply
Vladimir, at first I thought that having separate formatters URL for persons and organizations would allow to create better constraints at Wikidata and consequently to have better data quality. But I am not sure anymore: I look now again at the original OpenCorporates dataset with separate identifiers for officers (https://opencorporates.com/officers/$1) and companies (https://opencorporates.com/companies/$1), and see that their officers are sometimes organizations. Hm... RShigapov (talk) 18:10, 23 November 2021 (UTC)Reply
I think one person can have multiple nodes, see example here https://www.wikidata.org/wiki/Q5346832#P10083 Germartin1 (talk) 15:51, 9 December 2021 (UTC)Reply
Why is there no opencorporates officer ID property? Germartin1 (talk) 15:53, 9 December 2021 (UTC)Reply
Return to "P10083" page.