Property talk:P10464
Latest comment: 1 year ago by 89.204.137.138 in topic Change datatype to external-id
Documentation
KLADR ID
identifier for a place in the KLADR database
identifier for a place in the KLADR database
[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)
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/P10464#Single value, 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/P10464#Unique value, SPARQL (every item), SPARQL (by value)
Type “federal subject of Russia (Q43263), street (Q79007), human settlement (Q486972), square (Q174782), municipal district (Q2198484), settlement of Moscow (Q4373614)”: item must contain property “instance of (P31)” with classes “federal subject of Russia (Q43263), street (Q79007), human settlement (Q486972), square (Q174782), municipal district (Q2198484), settlement of Moscow (Q4373614)” 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/P10464#Type Q43263, Q79007, Q486972, Q174782, Q2198484, Q4373614, SPARQL
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/P10464#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P10464#Format, 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/P10464#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/P10464#Scope, SPARQL
Item “country (P17): Russia (Q159)”: Items with this property should also have “country (P17): Russia (Q159)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P10464#Item P17, hourly updated report, search, SPARQL
|
Change datatype to external-id
editProposal to change datatype to external-id. GeoGQL (talk) 23:11, 1 April 2023 (UTC)
- @MasterRus21thCentury, Сидик из ПТУ, Kirilloparma: why was this created with String datatype? This seems to have been discussed on the proposal page but I don't quite follow what happened. ArthurPSmith (talk) 16:50, 4 April 2023 (UTC)
- Kirilloparma said despite not having a possibility to URL-link one could still use external-id but also said that string would be possible. MasterRus21thCentury then said something that Google translate convertes into English as "Yes, I agree with the string data type in the card along with OKATO and OKTMO.". That is no reason against external-id presented. GeoGQL (talk) 17:13, 4 April 2023 (UTC)
- Support, has distinct value constraint. No logic in having this as string. 89.204.137.138 02:53, 21 April 2023 (UTC)