Property talk:P126
Add topicLatest comment: 3 years ago by ŠJů in topic Inverse property
Documentation
maintained by
person or organization in charge of keeping the subject (for instance an infrastructure) in functioning order
person or organization in charge of keeping the subject (for instance an infrastructure) in functioning order
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “organization (Q43229), fictional organization (Q14623646), human (Q5), position (Q4164871), facility (Q13226383), project (Q170584), government program (Q22222786)”: 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 organization (Q43229), fictional organization (Q14623646), human (Q5), position (Q4164871), facility (Q13226383), project (Q170584), government program (Q22222786) (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/P126#Value type Q43229, Q14623646, Q5, Q4164871, Q13226383, Q170584, Q22222786, SPARQL
None of WikiProject Mathematics (Q8487137): value must not be any of the specified items.
Replacement property: maintained by WikiProject (P6104) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Replacement property: maintained by WikiProject (P6104) (Help)
List of violations of this constraint: Database reports/Constraint violations/P126#none of, search, SPARQL
Allowed entity types are Wikibase property (Q29934218), 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/P126#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P126#Scope, SPARQL
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
Value WikiProject Mathematics (Q8487137) will be automatically replaced to value WikiProject Mathematics (Q8487137) and moved to maintained by WikiProject (P6104) property. Testing: TODO list |
generalize / généralisation
[edit]English: This property and P127 should be generalized: for example bridges have an owner and a maintainer as well (cf. en:Template:Infobox bridge).
Français : Le domaine d'application de cette propriété ainsi que celui de P127 devraient être étendus : par exemple les ponts ont aussi un propriétaire et un organisme assurant sa maintenance. (cf. en:Template:Infobox bridge)
--Gloumouth1 (talk) 14:47, 6 March 2013 (UTC)
- Unless there is opposition to it, I will rename this property to "maintainer". --Zolo (talk) 06:18, 4 April 2013 (UTC)
- Ok with that. But is it enough? Description in every language should be updated; therefore, maybe we should have an "official" page to diffuse this kind of information. --Gloumouth1 (talk) 07:46, 4 April 2013 (UTC)
- Yes, we should have a better way to diffuse information, both for discussion and for translation updates. In this case, the issue has been discussed for P165, so further discussion does not seem really needed, and I tried to update translation, but that's not really complete.--Zolo (talk) 10:33, 7 April 2013 (UTC)
- Actually, there seems to be P:P137, I am not sure whether they refer to the same thing. I think the difference is not always clear (and it seems to be worth in some translations), so that it would be better to merge both properties and use qualifiers. --Zolo (talk) 10:51, 7 April 2013 (UTC)
- If you agree with the generalization, why did you revert it? --Gloumouth1 (talk) 08:18, 8 April 2013 (UTC)
- Because I encountered a label conflict with P:P137 for lang:nds. I think we should decide whether we should merge the two properties. --Zolo (talk) 08:29, 8 April 2013 (UTC)
- I left a note at Property talk:P137. --Zolo (talk) 09:04, 8 April 2013 (UTC)
Done, after minor clarifications. --Zolo (talk) 15:23, 11 April 2013 (UTC)
- Cool. --Gloumouth1 (talk) 15:34, 11 April 2013 (UTC)
- If you agree with the generalization, why did you revert it? --Gloumouth1 (talk) 08:18, 8 April 2013 (UTC)
- Ok with that. But is it enough? Description in every language should be updated; therefore, maybe we should have an "official" page to diffuse this kind of information. --Gloumouth1 (talk) 07:46, 4 April 2013 (UTC)
Inverse property
[edit]Hi, what's inverse property for this? Do we want inverse property? I think yes. Skim (talk) 11:17, 23 September 2020 (UTC)
- Depending on context, you could try item operated (P121), or subject has role (P2868)X
P642Y , where X could be software maintainer (Q1420140), curator (Q674426), proprietor (Q16869121), manager (Q2462658), legal guardian (Q157509), operator (Q1970438), etc. Do you have examples of items where you think such a statement is needed? Swpb (talk) 15:56, 29 September 2020 (UTC)
- @Swpb, Skim: We simply need an universal inverse property for this property. Generally, an "operator" is not allways the same as a "maintainer". "Maintaner" can be also a synonyme for "administrator", in some contexts and languages and types of items. Generally, the property P126 is often used for a state or municipal property which is maintained by the state or municipal organization or by an authorized private organization. Private companies can also establish or hire another entity or establish their own organizational unit to manage their assets or their activities. Fundations, infrastructure managers, protected area manageres etc. can fall under this term. This subject usually exercises the rights and obligations of the owner in full or to a limited extent. In this way, a specific employee (person, function) who has been authorized as an administrator/keeper/curator/caretaker/custodian can also be the maintainer of any property or activity or right or obligation. E.g. in case of a railway line, the maintainer needs not to be identical with the operator. In case of a protected natural area or forests etc., the landscape is rather "maintained" than "operated". In case of buildings, structures and similar facilites, it is necessary to distinguish between the entity that rents and manages the device on behalf of the owner, and the entity that has it in use as an operator (as a tenant). (Unfortunately, there is a complication here that labels of Wikidata properties in different languages can have different breadth of the concept and different connotations.) --ŠJů (talk) 14:34, 8 February 2023 (UTC)