Property talk:P137
Latest comment: 5 years ago by Syced in topic This property is used to document the operator of an embassy (as opposed to the country the embassy is in)
Documentation
operator
person, profession, or organization that operates the equipment, facility, or service
person, profession, or organization that operates the equipment, facility, or service
[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), group of humans (Q16334295), fictional character (Q95074), occupation (Q12737077), project (Q170584), person (Q215627), administrative territorial entity (Q56061), association (Q15911314), public transport network (Q18325841), control room (Q390516), cemetery (Q39614), enterprise (Q6881511), airport (Q1248784), juridical person (Q155076), établissement public (Q15343039), industry (Q268592), business (Q4830453), website (Q35127)”: 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), group of humans (Q16334295), fictional character (Q95074), occupation (Q12737077), project (Q170584), person (Q215627), administrative territorial entity (Q56061), association (Q15911314), public transport network (Q18325841), control room (Q390516), cemetery (Q39614), enterprise (Q6881511), airport (Q1248784), juridical person (Q155076), établissement public (Q15343039), industry (Q268592), business (Q4830453), website (Q35127) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Wikidata External ID redirector (Q108047563)List of violations of this constraint: Database reports/Constraint violations/P137#Value type Q43229, Q14623646, Q5, Q16334295, Q95074, Q12737077, Q170584, Q215627, Q56061, Q15911314, Q18325841, Q390516, Q39614, Q6881511, Q1248784, Q155076, Q15343039, Q268592, Q4830453, Q35127, SPARQL
Contemporaries:
if [item A] has this property (operator (P137)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (operator (P137)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P137#Contemporary, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase property (Q29934218), Wikibase MediaInfo (Q59712033): 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/P137#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P137#Scope, hourly updated report, SPARQL
Jail operator
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P137#Jail operator
(Help)
Violations query:
SELECT ?item ?operator { ?item wdt:P31/wdt:P279* wd:Q40357. ?item wdt:P137 ?operator. FILTER (?operator NOT IN (wd:Q7553258, wd:Q1400015, wd:Q8772743, wd:Q5513196, wd:Q1135278, wd:Q8022, wd:Q2018436, wd:Q7834044, wd:Q11220, wd:Q1547708, wd:Q17015228, wd:Q55867952, wd:Q57165085, wd:Q499104, wd:Q55315781, wd:Q4966552, wd:Q23074194, wd:Q1065, wd:Q6071108, wd:Q2821147)) FILTER NOT EXISTS { ?operator wdt:P31 wd:Q7188 } FILTER NOT EXISTS { ?operator wdt:P31/wdt:P279* wd:Q327333 } FILTER NOT EXISTS { ?operator wdt:P1128 [] } FILTER NOT EXISTS { ?operator wdt:P31/wdt:P279* wd:Q8473 } FILTER NOT EXISTS { ?operator wdt:P31 wd:Q2659904 } FILTER NOT EXISTS { ?operator wdt:P31 wd:Q1802419 } FILTER NOT EXISTS { ?operator wdt:P1056 wd:Q386432 } FILTER NOT EXISTS { ?item wdt:P31 wd:Q152081 } FILTER NOT EXISTS { ?operator wdt:P17 wd:Q77 } FILTER NOT EXISTS { ?operator wdt:P31/wdt:P279* wd:Q7275 } FILTER NOT EXISTS { ?operator p:P576 ?d } FILTER NOT EXISTS { ?item p:P3999 ?old } FILTER (?item NOT IN (wd:Q594994)) FILTER NOT EXISTS { ?operator wdt:P17 wd:Q414 } FILTER NOT EXISTS { ?item wdt:P31 wd:Q683992 } FILTER NOT EXISTS { ?item wdt:P31 wd:Q1498196 } FILTER NOT EXISTS { ?item p:P8047 [] } }List of this constraint violations: Database reports/Complex constraint violations/P137#Jail operator
Operate a railway line
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P137#Operate a railway line
(Help)
Violations query:
SELECT ?item ?operator { ?item wdt:P31 wd:Q728937. ?item wdt:P137 ?operator. FILTER NOT EXISTS { ?operator p:P31 [] } }List of this constraint violations: Database reports/Complex constraint violations/P137#Operate a railway line
Operate a railway line, complex query
Work in progress query (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P137#Operate a railway line, complex query
Work in progress query (Help)
Violations query:
SELECT ?item ?operator { ?item wdt:P31 wd:Q728937. ?item wdt:P137 ?operator. ?operator p:P31 []. # avoid 5 results FILTER NOT EXISTS { ?operator wdt:P31 wd:Q17377208 } FILTER NOT EXISTS { ?operator wdt:P31 wd:Q249556 } FILTER NOT EXISTS { ?operator wdt:P31 wd:Q740752 } # popular but can use the next line FILTER NOT EXISTS { ?operator wdt:P452 wd:Q3565868 } FILTER NOT EXISTS { ?operator wdt:P452 wd:Q249556 } FILTER NOT EXISTS { ?operator wdt:P452 wd:Q178512 } FILTER NOT EXISTS { ?operator wdt:P452 wd:Q7590 } FILTER NOT EXISTS { ?operator wdt:P31 wd:Q521458 } FILTER NOT EXISTS { ?operator wdt:P31/wdt:P279* wd:Q249556 } FILTER NOT EXISTS { ?operator p:P1471 ?reportingMark } FILTER NOT EXISTS { ?operator wdt:P31 wd:Q7835189 } FILTER NOT EXISTS { ?operator wdt:P463 wd:Q388314 } # avoid ... Q1677108 FILTER NOT EXISTS { ?operator wdt:P101 wd:Q3565868 } # domain FILTER NOT EXISTS { ?operator wdt:P452 wd:Q22667 } FILTER NOT EXISTS { ?operator wdt:P749 ?mother. ?mother wdt:P31 wd:Q249556 } # to avoid Q5966130 FILTER NOT EXISTS { ?operator wdt:P749 ?mother. ?mother wdt:P31 wd:Q740752 } # to avoid Q1765011 FILTER NOT EXISTS { ?operator wdt:P749 wd:Q664399 } # mother: Keolis # FILTER NOT EXISTS { ?operator p:P2541 ?zone. ?operator wdt:P31 wd:Q327333 } # to avoid Q5034704 operator only FILTER NOT EXISTS { ?operator wdt:P31 wd:Q327333 } # avoid Q15908531 too FILTER NOT EXISTS { ?operator wdt:P31/wdt:P279* wd:Q327333 } # avoid Q2250917 FILTER NOT EXISTS { ?operator wdt:P17 wd:Q17 } # Japan FILTER NOT EXISTS { ?operator wdt:P17 wd:Q1206012 } FILTER NOT EXISTS { ?operator wdt:P17 wd:Q668 } # India FILTER NOT EXISTS { ?operator wdt:P1056 wd:Q3407658 } # to avoid Q369524 FILTER NOT EXISTS { ?operator wdt:P452 wd:Q862571 } # to avoid Q5153816 exception FILTER (?operator NOT IN (wd:Q497244, wd:Q3726202, wd:Q4974586, wd:Q2872768, wd:Q15138907, wd:Q1926929, wd:Q2215905, wd:Q1407994, wd:Q1616278, wd:Q28670302, wd:Q3855714, wd:Q13634023, wd:Q15615204, wd:Q538101, wd:Q20010045, wd:Q24813254, wd:Q21043221, wd:Q1663784, wd:Q28868775, wd:Q3963830, wd:Q3369995, wd:Q16607060, wd:Q16599279, wd:Q3060836, wd:Q3743281, wd:Q3998389, wd:Q7566134, wd:Q6840763, wd:Q17636721, wd:Q18325550, wd:Q3952222, wd:Q11111997, wd:Q11411921, wd:Q11414812, wd:Q11465832, wd:Q11666892, wd:Q3963332, wd:Q13563305)) # Q538101 : agence pub FILTER (?item NOT IN (wd:Q1327589)) }List of this constraint violations: Database reports/Complex constraint violations/P137#Operate a railway line, complex query
Operate an embassy
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P137#Operate an embassy
(Help)
Violations query:
SELECT ?item { ?item wdt:P137 ?value; wdt:P31 wd:Q3917681. MINUS { ?value wdt:P31 [] } }List of this constraint violations: Database reports/Complex constraint violations/P137#Operate an embassy
Operate an embassy, check value
(Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P137#Operate an embassy, check value
(Help)
Violations query:
SELECT ?item { ?item wdt:P137 ?value; wdt:P31 wd:Q3917681. MINUS { VALUES ?list { wd:Q6256 wd:Q7275 wd:Q103817 } ?value wdt:P31/wdt:P279* ?list } }List of this constraint violations: Database reports/Complex constraint violations/P137#Operate an embassy, check value
Operate an airport
Detect some mistakes (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P137#Operate an airport
Detect some mistakes (Help)
Violations query:
SELECT ?item { ?item wdt:P137 ?value; wdt:P31 wd:Q1248784. MINUS { ?value wdt:P17 [] } MINUS { ?value wdt:P31/wdt:P279* wd:Q43229 } }List of this constraint violations: Database reports/Complex constraint violations/P137#Operate an airport
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
As discussed in Property talk:P126, the difference between operator and maintainer may not always be clear in practice. Does it make sense to keep two separate properties ? Using qualifiers instead may provide something more flexible and simpler to use. --Zolo (talk) 09:03, 8 April 2013 (UTC)
- I discuss a case I know of, for a metro line or a railway you can have two distinct entities doing the maintenance and operating the line. In France maintenance of most of the railways are under the responsability of Q1071978 and lines operation under the responsability of Q13646. So it's not a good ideas to merge the two properties otherwise, we will not be able to fill all the data for those two examples and maybe some more. Greenski (talk) 13:57, 9 April 2013 (UTC)
- Ok, then I think we should have better documentation of what is an operator and what is a maintainer. From what I understand, an operator is someone who uses an infrastructure (a telecom network, a rail line) and a mainteiner takes care of the infrastructure. Bus it seems that the labels and descriptions are rather similar in some languages, so I think the difference should be made clearer in the documentation. --Zolo (talk) 09:56, 10 April 2013 (UTC)
- We definitively should make sure that the descriptions are clear in all languages in order to create a clear distinction between the two properties. Greenski (talk) 12:20, 10 April 2013 (UTC)
- In general this would apply to the business/executive type of operator, the highest level of the operations, the overall controller. So, I'd suspect that Réseau Ferré de France (Q1071978) is not an operator. Danrok (talk) 18:53, 22 May 2013 (UTC)
- On second thoughts Réseau Ferré de France (Q1071978) may be an operator of some items. Danrok (talk) 19:00, 22 May 2013 (UTC)
- In general this would apply to the business/executive type of operator, the highest level of the operations, the overall controller. So, I'd suspect that Réseau Ferré de France (Q1071978) is not an operator. Danrok (talk) 18:53, 22 May 2013 (UTC)
- We definitively should make sure that the descriptions are clear in all languages in order to create a clear distinction between the two properties. Greenski (talk) 12:20, 10 April 2013 (UTC)
- Ok, then I think we should have better documentation of what is an operator and what is a maintainer. From what I understand, an operator is someone who uses an infrastructure (a telecom network, a rail line) and a mainteiner takes care of the infrastructure. Bus it seems that the labels and descriptions are rather similar in some languages, so I think the difference should be made clearer in the documentation. --Zolo (talk) 09:56, 10 April 2013 (UTC)
Responsible edit
What property should I use for the entity which is ultimately responsible of the service? For instance, the entity which chose or funded the operator? Archive of Editorial Production of Lombardy (Q19662348) is a service, mandatory by law (so by Italy (Q38)), which the responsible entity Lombardy (Q1210) commissioned to Biblioteca Europea di Informazione e Cultura (Q3639582). The "maintainer" would be the technical company which takes care of the hosting (not relevant for Wikidata), but what about the responsible/overseeing entity? --Federico Leva (BEIC) (talk) 16:28, 23 March 2015 (UTC)
Country as an operator edit
It has been suggested in several discussions that this property be used for the country that an embassy represents (with country (P17) used for the host country) e.g.
⟨ Embassy of Georgia, London (Q16891022) 
⟩ country (P17) ⟨ United Kingdom (Q145) ⟩
operator (P137) ⟨ Georgia (Q230) ⟩
⟩ country (P17) ⟨ United Kingdom (Q145) ⟩operator (P137)
⟨ Georgia (Q230) ⟩however this is not permitted by the current constraints. Should the constraints here be changed? See also WD:PC#From an embassy's QID, get its represented country and previous discussions linked from there. Thryduulf (talk) 11:10, 5 July 2016 (UTC)
- How about using an instance of government (Q7188) (which is a subclass of organization (Q43229)) instead of directly a country ?--Melderick (talk) 12:57, 5 July 2016 (UTC)
- Not a bad suggestion. It would work for the obvious cases like UK, USA, Georgia, etc. Would it work where there are competing entities for the government (I don't know how the government items for those countries are structured)? Thryduulf (talk) 19:17, 5 July 2016 (UTC)
Expansion/clarification of scope edit
Per Wikidata:Property_proposal/Competent_authority I expanded/clarified the scope of the property in these diffs. /André Costa (WMSE) (talk) 12:11, 4 August 2016 (UTC)
- That doesn't strike me as a good idea. If terminology may be the same in some languages, these are generally two different concepts. Please revert.
--- Jura 12:21, 4 August 2016 (UTC)- Me neither but that seemed to be the outcome of the proposal discussion. I've re-opended that (unsure if it needs to be linked back in on any pages). Lets take the discussion there. /André Costa (WMSE) (talk) 15:17, 4 August 2016 (UTC)
- That discussion was now closed with the conclusion that the definition should be changed here so I'll re-add that changes. /André Costa (WMSE) (talk) 16:24, 25 August 2016 (UTC)
- I don't see a consensus for that. Who agreed to that? There is just no consensus for a new property.
--- Jura 17:22, 25 August 2016 (UTC)- Well it was explicitly closed by @Srittau: as "don't create a new property, amend the labels on P137 instead". /André Costa (WMSE) (talk) 08:02, 7 September 2016 (UTC)
- Can we see a reference for the 2nd definition? Other than P. who agree to it? --- Jura 06:26, 26 August 2016 (UTC)
- The second definition is explicitly not for the word/label "operator" but for the greater scope which it was suggested that this property should cover. Personally I don't think expanding P137 is the better solution but then that is what the Proposal ended up in. The current process (some people are involved in property proposals, another in patrolling existing properties) is problematic though since it means that issues such as these essentially end up being bounced back and forth in some kind of limbo. Do we need an RfC (yet another group of people who likely don't fully overlap with the other two) to resolve this? /André Costa (WMSE) (talk) 08:02, 7 September 2016 (UTC)
- Here is the one from Wiktionary: https://en.wiktionary.org/wiki/operator#Noun
--- Jura 07:27, 26 August 2016 (UTC)
- I don't see a consensus for that. Who agreed to that? There is just no consensus for a new property.
- That discussion was now closed with the conclusion that the definition should be changed here so I'll re-add that changes. /André Costa (WMSE) (talk) 16:24, 25 August 2016 (UTC)
- Me neither but that seemed to be the outcome of the proposal discussion. I've re-opended that (unsure if it needs to be linked back in on any pages). Lets take the discussion there. /André Costa (WMSE) (talk) 15:17, 4 August 2016 (UTC)
- P137 operator(child) → family, operator(people) → government, operator(world) → God and so on? --Fractaler (talk) 07:08, 26 August 2016 (UTC)
- @Jura1, Srittau, Pigsonthewing: So to follow up on this. Can we either agree to a re-labelling or would one of you mind raising an RfC about it since there is obviously a conflict between what was decided in the Property Proposal process and how it is being realised here. Personally I don't care which the outcome is but the current limbo prevents me from adding this type of data to Wikidata. /André Costa (WMSE) (talk) 07:42, 3 October 2016 (UTC)
- It might be worth formulating a proposal that better fits your immediate need. I think the term used might have been confusing due to some uses in the UK ("airport authority" and "London airport" changing roles).
--- Jura 07:51, 3 October 2016 (UTC)- Well the proposal was essentially to fill the spot currently taken by P137 in ⟨ Environmental Noise Directive (Q22908169)and ⟩ operator (P137) ⟨ Swedish Environmental Protection Agency (Q2976522) ⟩
country (P17) ⟨ Sweden (Q34) ⟩⟨ Bothnian Bay Water District (Q25346184). Not sure I could have made it any more narrow while still being useful. For now I'll just use P137 but leave the current labelling as is. It's not a ideal but it works for now. This is the second time I've encountered clashes between the Property Proposal process and implementation on existing properties and with no existing avenues for getting this sorted I just don't have the energy to put the proposal back in just to likely see it end up back here. /André Costa (WMSE) (talk) 12:09, 13 October 2016 (UTC) ⟩ operator (P137) ⟨ Kalmar County Administrative Board (Q25349864) ⟩
- Well the proposal was essentially to fill the spot currently taken by P137 in
- It might be worth formulating a proposal that better fits your immediate need. I think the term used might have been confusing due to some uses in the UK ("airport authority" and "London airport" changing roles).
- @Jura1, Srittau, Pigsonthewing: So to follow up on this. Can we either agree to a re-labelling or would one of you mind raising an RfC about it since there is obviously a conflict between what was decided in the Property Proposal process and how it is being realised here. Personally I don't care which the outcome is but the current limbo prevents me from adding this type of data to Wikidata. /André Costa (WMSE) (talk) 07:42, 3 October 2016 (UTC)
This property is used to document the operator of an embassy (as opposed to the country the embassy is in) edit
The documentation is outdated, does not reflect actual usage (there are 3140 embassies and consulates on Wikidata, 99.904% of them have an operator (P137)).
So please someone fix the documentation by removing this very wrong bit: "use country for diplomatic missions".
Thanks! Syced (talk) 11:23, 5 December 2018 (UTC)