Property talk:P635

From Wikidata
Jump to navigation Jump to search

Documentation

[create Create a translatable help page (preferably in English) for this property to be included here]
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (Help)
List of violations of this constraint: Database reports/Constraint violations/P635#single best value, hourly updated report, 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/P635#Unique value, SPARQL (every item), SPARQL (by value)
Format “\d{2}|\d{3}|\d{6}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P635#Format, hourly updated report, 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/P635#Item P625, SPARQL
Item “country (P17): Italy (Q38): Items with this property should also have “country (P17): Italy (Q38)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P635#Item P17, hourly updated report, search, SPARQL
Item “shares border with (P47): Items with this property should also have “shares border with (P47)”. (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/P635#Item P47, search, 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/P635#Item P131, search, SPARQL
Item “postal code (P281): Items with this property should also have “postal code (P281)”. (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/P635#Item P281, search, SPARQL
Item “local dialing code (P473): Items with this property should also have “local dialing code (P473)”. (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/P635#Item P473, search, SPARQL
Item “located in time zone (P421): UTC+01:00 (Q6655): Items with this property should also have “located in time zone (P421): UTC+01:00 (Q6655)”. (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/P635#Item P421, search, SPARQL
Item “Italian cadastre code (municipality) (P806): Items with this property should also have “Italian cadastre code (municipality) (P806)”. (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/P635#Item P806, search, SPARQL
Item “locator map image (P242): Items with this property should also have “locator map image (P242)”. (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/P635#Item P242, SPARQL
Item “Commons category (P373): Items with this property should also have “Commons category (P373)”. (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/P635#Item P373, search, 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/P635#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/P635#Scope, SPARQL
Label required in languages: it: Entities using this property should have labels in one of the following languages: it (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/P635#Label in 'it' language, 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.)

Tabella di conversione con codice ISTAT, codice catastale, codice regione ed elemento Wikidata[edit]

Niente di che, ma magari può tornare utile ad altri: interrogazione SPARQL. Al momento dà 8264 risultati unici, non sono sicuro che sia corretto. --Nemo 10:30, 24 July 2018 (UTC)[reply]

Ah sí, c'erano alcune righe di troppo, come alcuni comuni siciliani che sono presenti sia con codice regione 19 (giusto) sia con 082 (sbagliato), a causa di [1] [2] [3]. --Nemo 11:50, 24 July 2018 (UTC)[reply]
Occhio che per i comuni devi considerare i comuni sparsi (Q954172) e togliere quelli cessati ?item p:P31 ?com. {?com ps:P31 wd:Q747074} UNION {?com ps:P31 wd:Q954172} . FILTER NOT EXISTS { ?com pq:P582 ?x } --Sabas88 (talk) 10:41, 8 August 2018 (UTC)[reply]
Dovrei però prima verificare se i miei dati di partenza contengano informazioni su quei luoghi. Se mi interessa la regione in cui si trova un posto, anche il codice del comune cessato va bene. --Nemo 10:11, 25 August 2018 (UTC)[reply]

property constraint da modificare[edit]

Al codice ISTAT sono associati le tre "property constraint" sottostanti.

I codici ISTAT ci sono anche per le regioni, quindi:

  • non sono sempre associabili a un prefisso telefonico (non in relazione 1:1, ma a famiglie di prefissi);
  • i CAP regionali non esistono in relazione 1:1, si sa soltanto che quelli di alcune regioni iniziano per 1..., ecc.;
  • il codice catastale è (credo) coincidente con quello ISTAT.

Le prime due le rimuoverei.

 – The preceding unsigned comment was added by Aborruso (talk • contribs).

Notified participants of WikiProject Italy
@Aborruso: Immagino che originariamente il codice fosse limitato solo ai comuni e per questo abbiamo deciso di imporre quei constraint - anche se non sono obbligatori, ma solo "consigliati". A questo punto, direi che possiamo chiamare il Wikiprogetto Italia e discuterne insieme agli altri. --Sannita - not just another it.wiki sysop 10:57, 10 August 2018 (UTC)[reply]
Io ho bisogno di capire cos'è un "property constraint". Poi qualcuno mi spiega a cosa serve l'immagine che è stata qui inserita? Qual è il suo utilizzo?--Sentruper (talk) 14:25, 10 August 2018 (UTC)[reply]
@Sentruper: Un "property constraint" è una regola che si applica a una proprietà. In questo senso, si dice che la proprietà ISTAT ID (P635) è da utilizzare assieme ad altre proprietà. L'immagine è stata fatta perché Andrea non sapeva come richiamare altrimenti le cose che diceva. Sannita - not just another it.wiki sysop 15:00, 10 August 2018 (UTC)[reply]
Rispondo sui primi due punti: 1. È vero: i prefissi telefonici sono tipicamente distrettuali (sub-provinciali); 2. È vero: i CAP non sono associati alle regioni. Sono d'accordo col rimuovere i primi due. --Sentruper (talk) 15:54, 10 August 2018 (UTC)[reply]
Non ho mai usato questa proprietà, ma documentandomi (prima di leggere gli ultimi commenti), sarei anche io giunto all'idea che vadano rimossi.--Alexmar983 (talk) 18:22, 10 August 2018 (UTC)[reply]
 Support. Va però spiegato in inglese così da avvisare chi ha messo i constraint perché li stiamo rimuovendo --★ → Airon 90 06:43, 11 August 2018 (UTC)[reply]