Property talk:P1454

From Wikidata
Jump to navigation Jump to search

Documentation

Descriptionlegal form on an organization within the legal framework of its seat country (Inc., LLC, etc.)
Representslegal form (Q10541491)
Data typeItem
Template parameterHier den Infobox-Parameter einfügen, falls es einen gibt. Beispiel: "Rechtsform" (legal form) in de:Vorlage:Infobox Verband, de:Vorlage:Infobox Unternehmen
Domain
According to statements in the property:
organization (Q43229), human (Q5), fictional organization (Q14623646), juridical person (Q155076) or periodical (Q1002697)
When possible, data should only be stored as statements
Allowed valuesGesellschaft mit beschränkter Haftung (Q460178), foundation (Q157031), public establishment of an administrative nature (Q3244038), Gesellschaft mit beschränkter Haftung (Q460178) and many more (note: this should be moved to the property statements)
ExampleHaribo (Q169552)GmbH & Co. KG (Q897103)
Wikimedia Netherlands (Q2406378)vereniging (Q64686674)
Federation of Migros Cooperatives (Q680727)cooperative (Q53828709)
Academy of Motion Picture Arts and Sciences (Q212329)corporation (Q57655560)
Suntory (Q1345267)kabushiki gaisha (Q1480166)
Tracking: usageCategory:Pages using Wikidata property P1454 (Q20990032)
Tracking: local yes, WD noCategory:P1454 absent from Wikidata (Q101364401)
Lists
Proposal discussionProposal discussion
Current uses
Total455,502
Main statement455,430>99.9% of uses
Qualifier58<0.1% of uses
Reference14<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “legal form (Q10541491): This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value legal form (Q10541491) (or a subclass thereof). (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/P1454#Value type Q10541491, SPARQL
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/P1454#Single value, 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/P1454#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/P1454#Scope, SPARQL
None of company (Q783794), foundation (Q157031): value must not be any of the specified items.
Replacement property:
Replacement values: (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/P1454#none of, SPARQL
Item “country (P17): Items with this property should also have “country (P17)”. (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/P1454#Item P17, search, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Constraint

[edit]

I propose the Wikidata item of this property (P1629) to be juridical person (Q155076) not type of business entity (Q1269299)--Asqueladd (talk) 11:48, 21 June 2017 (UTC)[reply]

I agree. I have changed the constraint accordingly. --UV (talk) 20:44, 21 June 2017 (UTC)[reply]
See considerations on value type below. 2001:7D0:81F7:B580:7844:13A:83F9:BF67 10:32, 25 November 2019 (UTC)[reply]

extended to Q5

[edit]

d1g (talk) 04:21, 14 August 2017 (UTC)[reply]

Proper class instead of Q5 and Q43229 would be agent (Q24229398). d1g (talk) 04:23, 14 August 2017 (UTC)[reply]

I believe that values of this properties should be subclass of (P279) juridical person (Q155076), not instance of (P31) juridical person (Q155076).

I propose to change the constraint accordingly. If you want to stick to instance of (P31), then we should use another item for that. − Pintoch (talk) 10:32, 15 September 2017 (UTC)[reply]

This seems to be an obvious mistake. I've made the change. 90.191.81.65 07:22, 14 June 2018 (UTC)[reply]

Then again, juridical person (Q155076), or more widely legal person (Q3778211), may not do well enough as value type because there are kinds of unincorporated entities and similar which do have a legal form, but which strictly speaking are not legal persons (legal entities). As argued e.g. here lately. Alternatively, it may be more sufficient to set it so that values are instances of legal form (Q12047392) (including instances of its subclasses like Q19588327). 2001:7D0:81F7:B580:7844:13A:83F9:BF67 10:32, 25 November 2019 (UTC)[reply]

So, I'm going to try "legal form" with "instance of" relation as value type instead. At first this will produce some new constraint violations, and it will fix some existing ones as well. Either ways currently there are lots legal form values of bad types as recently someone has falsely copied 1000s of generic types like company (Q783794) or voluntary association (Q48204) from P31 to P1454, while these generic types are not actual legal forms within any particuar legal sytem (compared to Q1518608, Q11513034 etc.) and for some cases denote entities that actually don't even have legal form. 2001:7D0:81F7:B580:E13C:34E5:F2D9:36DA 09:34, 12 December 2019 (UTC)[reply]