Property talk:P2815
Latest comment: 1 year ago by SM5POR in topic Deprecating qualifier P642
Documentation
ESR station code
unique railway station/operation point code used in USSR and later in former USSR countries
unique railway station/operation point code used in USSR and later in former USSR countries
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P2815#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/P2815#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2815#Format, hourly updated report, SPARQL
Type “operation point (Q124817561)”: item must contain property “instance of (P31)” with classes “operation point (Q124817561)” 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/P2815#Type Q124817561, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
List of violations of this constraint: Database reports/Constraint violations/P2815#Entity types, hourly updated report
Scope is as main value (Q54828448), as reference (Q54828450): 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/P2815#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2815#Item P17, hourly updated report, search, SPARQL
Item “coordinate location (P625)”: Items with this property should also have “coordinate location (P625)”. (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/P2815#Item P625, SPARQL
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Deprecating qualifier P642
edit@Entbert, @Lockal: We are in the process of deprecating of (P642) due to ambiguous use. It's used on P2815#P1630 (P2815#P1630) in an unsupported fashion (it triggers a constraint violation). Are you aware of any practical need for it on this particular property? Can it simply be removed? --SM5POR (talk) 20:19, 15 January 2023 (UTC)
- @SM5POR, what do you mean by "this property"? It is not used right now. As for general usage, there is a User:Lucas Werkmeister/P642 considered harmful, which you might have already seen, I hope. There are a number of open question on discussion page there, but I hope they will be solved eventually. Lockal (talk) 03:16, 16 January 2023 (UTC)
- @Lockal: Sorry, I wasn't very clear above. By "this property" I'm referring to the Property:P2815 entity ESR station code (P2815) itself (rather than to its potential use in a claim made on any item), and in particular to its Property:P2815#P1630 property formatter URL (P1630) with three claims, two of them deprecated. Each of those three claims includes a qualifier of (P642) referring to operation point (Q1318558), railway company (Q249556) and railway stop (Q55678), respectively. While formatter URL (P1630) does not support the of (P642) qualifier, only the third claim is actually marked "(!)" as a constraint violation, since the first two claims are deprecated anyway.
- I'm aware of Lucas Werkmeister's article, and one year ago it had led to the creation of an effort to completely phase out of (P642) from WIkidata; see the project page Wikidata:WikiProject Data Quality/Issues/P642 for the current status of this effort (which I'm now taking part in). We have so far gone from over 10 million use cases to less than one million, but I believe most of the work is yet ahead of us. Yesterday I began looking into the Property namespace entities specifically, and that's how I found out about ESR station code (P2815).
- I assume the qualifier was added to the three formatter URLs in order to identify their functions or otherwise tell them apart, but if this identification is necessary you will have to find some other way of expressing it. I hope you can do this yourself, or you may be able to find someone else who can. Look at the allowed qualifiers constraint (Q21510851) claim of P1630#P2302 (P1630#P2302) for suggestions of which qualifiers can be used with formatter URL (P1630). --SM5POR (talk) 07:18, 16 January 2023 (UTC)
- Ah, you mean just 3 url formatters in Property:P2815#P1630... I converted them to Property:P518. And with that there are no more P642 for masks. Lockal (talk) 07:30, 16 January 2023 (UTC)
- @Lockal: That looks perfect, thank you! --SM5POR (talk) 05:43, 17 January 2023 (UTC)
- Ah, you mean just 3 url formatters in Property:P2815#P1630... I converted them to Property:P518. And with that there are no more P642 for masks. Lockal (talk) 07:30, 16 January 2023 (UTC)