Property talk:P474
Jump to navigation
Jump to search
Documentation
country calling code
identifier for a country - dialed on phone after the international dialing prefix (precede value by +)
identifier for a country - dialed on phone after the international dialing prefix (precede value by +)
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “country (Q6256), sovereign state (Q3624078), disputed territory (Q15239622), occupied territory (Q2577883)”: item must contain property “instance of (P31)” with classes “country (Q6256), sovereign state (Q3624078), disputed territory (Q15239622), occupied territory (Q2577883)” 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). Known exceptions: Antarctica (Q51)List of violations of this constraint: Database reports/Constraint violations/P474#Type Q6256, Q3624078, Q15239622, Q2577883, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P474#Format, 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). Known exceptions: Western Sahara (Q6250)List of violations of this constraint: Database reports/Constraint violations/P474#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/P474#Single value, 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/P474#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/P474#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.) |
Only countries?[edit]
Shouldn't there be a constraint that only countries should have this property? Currently, also some towns (Magenta (Q42595), Gorgonzola (Q43055), Ferentino (Q50197), Cagnò (Q256842), Houston (Q16555), Copenhagen (Q1748), ...), are using it, plus Caribbean Netherlands (Q27561), of which I can't even tell whether it is something like a country. --YMS (talk) 16:10, 20 August 2013 (UTC)
- You might want to add it and check what the report shows. -- Docu at 10:03, 24 August 2013 (UTC)
- I do agree that the first constraint is wrong and should be removed : trunk prefixes are not allocated only to countries/sovereign states. They are also allocated to group of countries (notably +1 and +7), or to dependencies. Most reported violations of this constraint are for them. (so they violate "only countries", but they also violate "distant values" when several countries share the same trunk prefix (e.g. Italy, Vatican and San Marino; and previously France and Monaco, even if Monaco is also part of the French numbering system and does not require an international call between the two countries).
- Additionally some countries (or parts of countries) may have two trunk simultaneous trunk prefixes (notably in dependencies that have their own trunk prefix but are also frequently within the numering system used by their parent country: an example with French overseas collectivites or overseas regions, you can use either a "short" phone number with the prefix for that dependency followed by the local number, or use the "long" form with the trunk prefix for the parent country, some digits for the area selection, and then the local phone number): if a country/territory has a trunk prefix, this does not mean that you MUST use them for calling them, and in fact it is NOT used as an international call number when calling them from anywhere of the same country, you just use the national unified numbering system, which is also used now locally, both for land lines or for mobile phones (that cannot be called using the trunk prefix assigned to the dependency, notably in overseas departments, where as you still must use an international call for calls between an overseas collectivity and the rest of France including other overseas collectivities; the old trunk prefixes for overseas are still usable for international calls from elsewhere, they have not been abandoned even after the national unification) ! Verdy p (talk) 22:17, 20 November 2016 (UTC)
- For this reason, the constraints are only there to check cases where those violations are known (but these violations are not errors).
- I think there should be another kind of description for such "weak constraints" that are only there to generate some reports about special cases that are less common, or there should be a list maintained where those less common violations are in fact perfectly correct and not errors to be corrected. But for pure data modelisation, these should not be "constraints". Verdy p (talk) 22:24, 20 November 2016 (UTC)