Property talk:P10421

From Wikidata
Jump to navigation Jump to search

Documentation

ELF code
code for entity legal form (ELF), assigned by the Global Legal Entity Identifier Foundation (GLEIF) per ISO 20275
RepresentsISO 20275 (Q106152815)
Data typeExternal identifier
Domainlegal form (Q10541491) or type of business entity (Q1269299)organization (Q43229)
Allowed values[A-Z\d]{4}
ExampleGesellschaft mit beschränkter Haftung (Q460178)2HBR
société anonyme (Q18195767)QVPB
akciová společnost (Q3742494)6CQN
kabushiki gaisha (Q1480166)T417
Sourcehttps://www.gleif.org/en/about-lei/code-lists/iso-20275-entity-legal-forms-code-list
Formatter URLhttps://search.gleif.org/#/search/criteria%5B0%5D%5BrelId%5D=FILTER_LEIREC&criteria%5B0%5D%5BfieldId%5D=LEIREC_LEGAL_FORM&criteria%5B0%5D%5Bvalue%5D%5Bcode%5D=$1&criteria%5B0%5D%5Boperator%5D=MATCH&criteria%5B0%5D%5BdataType%5D=RESOURCE&expertMode=true#results-section
See alsoLegal Entity Identifier (P1278), GLEIF registration authority code (P9487)
Lists
Proposal discussionProposal discussion
Current uses
Total571
Main statement565 out of 3,296 (17% complete)98.9% of uses
Qualifier40.7% of uses
Reference20.4% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P10421#Single value, hourly updated report, 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/P10421#Unique value, SPARQL (every item), SPARQL (by value)
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/P10421#Entity types
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/P10421#Scope, SPARQL
Type “legal form (Q10541491), type of business entity (Q1269299): item must contain property “instance of (P31)” with classes “legal form (Q10541491), type of business entity (Q1269299)” 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/P10421#Type Q10541491, Q1269299, SPARQL
Format “[A-Z\d]{4}: 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/P10421#Format, SPARQL
Type “organization (Q43229): item must contain property “subclass of (P279)” with classes “organization (Q43229)” 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/P10421#Type Q43229, SPARQL
Item “main regulatory text (P92): Items with this property should also have “main regulatory text (P92)”. (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/P10421#Item P92, search, SPARQL
Item “applies to jurisdiction (P1001): Items with this property should also have “applies to jurisdiction (P1001)”. (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/P10421#Item P1001, search, SPARQL
Item “properties for this type (P1963): Items with this property should also have “properties for this type (P1963)”. (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/P10421#Item P1963, search, SPARQL
alias to include one with country name
TODO: add an alias including the name of the country or jurisdiction. Sample: for Q53361238 "association (Austria)" and/or "Verein (Austria)" (Help)
Violations query: SELECT ?item ?l { ?item wdt:P10421 []. ?item wdt:P1001 ?country. ?country rdfs:label ?l . FILTER( lang(?l) = "en" ) FILTER NOT EXISTS { ?item skos:altLabel ?alt. FILTER(lang(?alt) = "en" && CONTAINS(?alt, ?l) ) } }
List of this constraint violations: Database reports/Complex constraint violations/P10421#alias to include one with country name

Constraints[edit]

Hello @Jura1:, you added foundational text (P457) as a constraint. Wouldn't be main regulatory text (P92) be the more precise Property? At least the German legal types use these, but perhaps it's a problem with translation and/or legal systems. And I would propose to add applies to jurisdiction (P1001) as a suggestion constraint (Q62026391) since all ELF code (P10421) are specific to a country/region. Best Newt713 (talk) 16:57, 4 March 2022 (UTC)[reply]

Yes, P92 seems better. Q1480166#P92 already has it. I will fix it when/if I find it where I go the idea from.
I hesitated if it should be P1001, P17 or both. --- Jura 17:09, 4 March 2022 (UTC)[reply]
Thank you @Jura1:. I would prefer applies to jurisdiction (P1001), since sometimes there are legal forms for regions like Québec in Canada. Newt713 (talk) 17:35, 4 March 2022 (UTC)[reply]
Sounds good. Maybe even both. --- Jura 18:49, 4 March 2022 (UTC)[reply]
  • How could we define that the name of some forms needs to match a naming convention? I thought about
Sample would be for Q98887042. Maybe another property such as has part(s) (P527) is preferable? --- Jura 08:31, 5 March 2022 (UTC)[reply]
properties for this type (P1963) might do. This could also mention specific id properties to be added. --- Jura 09:22, 5 March 2022 (UTC)[reply]
  • @Jura1: type constraint "subclass of: organization" is too strict as some legal forms are also types of natural person (Q154954). 2001:7D0:81DA:F780:E9A1:45F7:5AB9:4A99 10:42, 5 March 2022 (UTC)[reply]
    • I'm aware, but I wasn't quite sure which other parent class to add. Maybe once the constraint report is updated, it's easier to pick. --- Jura 11:12, 5 March 2022 (UTC)[reply]
  • @Jura1: above you added a complex constraint on aliases that include country name. I doubt it's really wanted. My understanding is that aliases are alternative names that actually exist in common use outside Wikidata. Help:Aliases also seems to suggest that. Something like "registered association (Finland)" appears to be merely an ad hoc combination of related keywords, not a real alias. 2001:7D0:81DA:F780:6580:39AA:98F6:296D 13:13, 6 March 2022 (UTC)[reply]
    I think it's a useful way of referring to said concept in English. Maybe "registered association of Finland" is better, but I don't think it matters that much. Help:Aliases isn't of much help about this. --- Jura 13:17, 6 March 2022 (UTC)[reply]
    There may be some practicality behind this, but it doesn't seem like proper use of aliases. In real usage it probably isn't referred to as "registered association of Finland" either. Alias suggesting otherwise is sort of misleading. 2001:7D0:81DA:F780:6580:39AA:98F6:296D 13:39, 6 March 2022 (UTC)[reply]
    What solution do you suggest? --- Jura 13:50, 6 March 2022 (UTC)[reply]
    Just follow the Wikidata term design and rely on descriptions when it comes to disambiguation? 2001:7D0:81DA:F780:6580:39AA:98F6:296D 14:02, 6 March 2022 (UTC)[reply]
    It's likely that one wouldn't be able to find the proper item when adding statements and attempting to pick "association" for a given country.
    In any case, I'm not sure who would be misled. Nobody would end up with the wrong item.
    Some articles include a reference to the country directly in the label. It would be rather confusing if these could be found whereas others wouldn't be. --- Jura 14:05, 6 March 2022 (UTC)[reply]
    Well, but aliases aren't merely a search aid. These can be regarded and exported as the actual data about item subject.
    Search box suggestions have its limitations and sometimes its needed to use advanced search or more specific queries anyway to get the appropriate result. In case of "associaton" there are many other items, in addition of legal forms, that have the same label, too. Also, even if alias is there as a search aid, then users are not really expected to know that such ad hoc alias exists.
    Yes, in some cases country name has been added to label, but this is as questionable as it is for aliases. Help:Label specifically says that labels can be ambiguous. 2001:7D0:81DA:F780:D193:AF3F:184D:1989 12:36, 7 March 2022 (UTC)[reply]

Label[edit]

How about a less cryptic label (currently it's "GLEI ELF"), e.g. "GLEI entity legal form ID"? The other could still be an alias. --- Jura 08:34, 5 March 2022 (UTC)[reply]

Yes, I made that suggestion in property proposal, too. Current label is just inaccurate. Item using this property is for entity legal form (ELF), while the property is for its identifer. Also it should be "GLEIF", not "GLEI". In source dataset the respective column header is "ELF Code". So it could be either that, or more specifically something like "GLEIF ELF code" as well. 2001:7D0:81DA:F780:E9A1:45F7:5AB9:4A99 10:42, 5 March 2022 (UTC)[reply]
I also would prefer "GLEIF ELF Code" or just "ELF Code" since the "ELF Code" is issued by GLEIF (Global Legal Entity Identifier Foundation). The foundation itself uses Code not ID. Newt713 (talk) 11:28, 5 March 2022 (UTC)[reply]