Property talk:P9487

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

GLEIF registration authority code
National registration authority code in the GLEI RAL list

Applicable "stated in" value	GLEIF Registration Authorities List (Q106448148)
Data type	External identifier
Domain	registration authority (Q166140), Registration court (Q2138576), register data (Q12314395) or company register (Q1394657)
Allowed values	RA[0-9]{6}
Example	Firmenbuch (Q1419112) → RA000017 Register of Associations (Q106448105) → RA000710
Source	https://www.gleif.org/en/about-lei/code-lists/gleif-registration-authorities-list
Formatter URL	https://search.gleif.org/#/search/simpleSearch=$1
See also	org-id.guide ID (P4824)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P9487 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 663 Main statement 661 out of 738 (90% complete) 99.7% of uses Qualifier 2 0.3% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “registration authority (Q166140), Registration court (Q2138576), register data (Q12314395), company register (Q1394657)”: item must contain property “instance of (P31)” with classes “registration authority (Q166140), Registration court (Q2138576), register data (Q12314395), company register (Q1394657)” 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/P9487#Type Q166140, Q2138576, Q12314395, Q1394657, 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/P9487#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/P9487#Single value, SPARQL

Format “RA[0-9]{6}”: 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/P9487#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/P9487#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/P9487#Entity types

Qualifiers “applies to jurisdiction (P1001)”: this property should be used only with the listed qualifiers. (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/P9487#allowed qualifiers, SPARQL

Code for register or organization?

@Vladimir Alexiev: current usage of this property is quite confusing. In property proposal you have pointed out that "RAL makes a distinction between the Register and the Agency that keeps it", but on Wikidata this property is apparently used for both. As far as I can see the value of this property, i.e. registration authority code, is an identifier for an organization (authority), and not for the register that given organization is responsible for. As in RAL multiple entries are associated to the same country/jurisdition/register, then I figure that this code really can't be an identifier for any of these. For instance RAL entry RA000221 is disambiguated from other entries by an organisation that is Local Court Braunschweig. So it would seem correct to me if an item about Local Court Braunschweig is matched to code RA000221, instead of item about the register, German Trade Register (Q457703), currently matched to this value. --2001:7D0:81DA:F780:A0B2:E075:58D2:6E26 15:31, 4 November 2021 (UTC)

Hi anon! More examples:

• UK has a single register (Company House) but 3 jurisdictions with different RALs (UK+Wales, Scotland, Ireland)
• Germany has a single register and jurisdiction, but many regional courts with different RALs (the example you gave)
• Gibraltar is a single jurisdiction and register, but has 4 RALs split by company type
• The US is about 50 distinct jurisdictions with distinct registers
• Many countries (incl BG) are single jurisdictions, but have more than one register
• BG has two registers (traders in TR, non-traders in BULSTAT) but a single identifier (UIC=EIK)

What's really important is that whenever several RAL are unified in one register (eg UK), or the same identifier is used in several registers (eg BG), we have a single property and item for that register.

• So I was hesitant to create too many entries (per each RAL).
• Nobody cares what is the particular RAL of Local Court Braunschweig because that's not reflected in the German company identifiers
• To do company linking between WD and GLEI, you care which set of RALs corresponds to which WD property.
• If you dislike my modeling with qualifier "applies to jurisdiction", could you please propose a better alternative?

PS: Please don't make changes before this discussion is decided, as we use this structure in a production project.

Cheers! Vladimir Alexiev (talk) 09:40, 23 November 2021 (UTC)

These examples generally illustrate my previous observation that RAL entries are for organizations. In case of Gibraltar I'm not sure, in last version of authorities' list there's one entry for Gibraltar. Though, now that I look into it more, I see that these entries aren't always for unique authorities either. For instance, Slovakia has 9 RAL entries/registers per one authority.

If RAL entry is sometimes matched to a register and sometimes to an organization, then how can anyone rely on these links reliably if using Wikidata? My suggestion is to match RAL entries to organizations consistently, as RAL entries after all are from a list of authorites, not from a list of registers. If there are multiple entries per authority, such as in case of Slovakia, then I suppose an item can be matched to multiple RAL entries. As for Local Court Braunschweig and other authorites which, as you say, nobody cares about, I see why not create items for these as these are likely notable entities. As for those a few cases where name of the register is given, but name of the organization is not, I suppose name of the register can be used as name of the authority as well (so that separate items still can be created for both the register and authority where necessary).

So far I've fixed it only for two Estonian RAL entries, of which one was matched to a register and another was matched to an organization, whereas both could have been matched to existing items of organizations. 2001:7D0:81DA:F780:5EC:FF62:2B92:2312 20:50, 23 November 2021 (UTC)

Query to return all RAL

Use this query to see all RAL codes, with country and jurisdiction:

SELECT ?co ?jurLabel ?ral ?item ?itemLabel  WHERE {
  ?item p:P9487 ?stat.
  ?stat ps:P9487 ?ral
  optional {?item wdt:P17/wdt:P297 ?co}
  optional {?stat pq:P1001 ?jur1}
  optional {?item wdt:P1001 ?jur2}
  bind(coalesce(?jur1,?jur2) as ?jur)
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en,bg,no,nn,nb" } .
} order by ?co ?jurLabel

Try it!

TODO: this returns the German registries repeated many times because the two OPTIONAL "?jur1, ?jur2" cause a Cartesian Explosion. So I need to use UNION inside OPTIONAL. But I can't force it to first bind "?item, ?stat" even if I use a subquery:

SELECT ?co ?jurLabel ?ral ?item ?itemLabel  WHERE {
  {select * {?item p:P9487 ?stat. ?stat ps:P9487 ?ral} }
  optional {?item wdt:P17/wdt:P297 ?co}
  optional {
    {?stat pq:P1001 ?jur1} union {?item wdt:P1001 ?jur2}
    bind(coalesce(?jur1,?jur2) as ?jur)
  }
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en,bg,no,nn,nb" } .
} order by ?co ?jurLabel

Try it!

So I need to use a bd:Hint to tell it to execute the patterns in order, but too lazy to look it up just now --Vladimir Alexiev (talk) 10:22, 23 November 2021 (UTC)

DE RAL, jurisdictions and courts

Picking up from Wikidata:Property_proposal/XJustiz_registration_court_ID.

Hi @RShigapov: thanks for importing DE RAL codes and moving them to DE courts! But the query below shows some problems:

• The first 5 don't have "country: DE"
• The Jurisdiction of the rest is a mess: "Hesse" comes up too many times, and it's unset too many times.

SELECT ?co ?jurLabel ?ral ?item ?itemLabel  WHERE {
  ?item p:P9487 ?stat.
  ?stat ps:P9487 ?ral
  optional {?item wdt:P17/wdt:P297 ?co}
  filter(!bound(?co) || ?co="DE")
  optional {?stat pq:P1001 ?jur1}
  optional {?item wdt:P1001 ?jur2}
  bind(coalesce(?jur1,?jur2) as ?jur)
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en,de,bg,no,nn,nb" } .
} order by ?co ?ral ?jurLabel

Try it!

After you add applies to jurisdiction (P1001) values for the courts, could you also copy them as qualifiers to GLEIF registration authority code (P9487)? Cheers! --Vladimir Alexiev (talk) 12:06, 18 January 2022 (UTC)

I've started to look at jurisdictions using https://www.lto.de/gerichte/aktuelle-urteile-und-adresse/amtsgericht-jena and it seems already problematic. So it says: "Amtsgerichtsbezirk: Kreisfreie Stadt Jena; aus dem Saale-Holzland-Kreis die Gemeinden Camburg, Dornburg/Saale, Dorndorf-Steudnitz, Frauenprießnitz, Golmsdorf, Großlöbichau, Hainichen, Jenalöbnitz, Lehesten, Löberschütz, Neuengönna, Schkölen, Tautenburg, Thierschneck, Wichmar, Zimmern, Zöthen". I am not sure if we should add those lowest municipalities as jurisdictions. May be we could add just Kreisfreie Stadt Jena and Saale-Holzland-Kreis, but the latter seems to be only a partial jurisdiction, only some municipalities and cities from it are a part of jurisdiction of the court. How can we model that? Can we use applies to jurisdiction (P1001) somehow with applies to part (P518)?

Another example is https://www.lto.de/gerichte/aktuelle-urteile-und-adresse/amtsgericht-kempten-allgaeu. It says "Amtsgerichtsbezirk: Kreisfreie Stadt Kempten (Allgäu) und Teile des Landkreises Oberallgäu

Gemeinden:

Altusried, Betzigau, Buchenberg, Dietmannsried, Durach, Haldenwang, Kempten (Allgäu), Lauben, Oy-Mittelberg, Sulzberg, Waltenhofen, Weitnau, Wiggensbach, Wildpoldsried" Or should we just add all those municipalities? RShigapov (talk) 13:35, 18 January 2022 (UTC)

F missing in name

Shouldn't it be GLEIF RAL instead of GLEI RAL, its issued by the "Global Legal Entity Identifier Foundation" (GLEIF). Newt713 (talk) 11:28, 5 March 2022 (UTC)

Yes. Also current label doesn't quite say what is the property for. RAL (Registration Authorities List) is the source dataset, while the property is for "Registration Authority Code" from this dataset. So, accordingly the label could be something like "GLEIF registration authority code". 2001:7D0:81DA:F780:6580:39AA:98F6:296D 12:56, 6 March 2022 (UTC)