Property talk:P1446

Latest comment: 9 years ago by Tobias1984 in topic Vermisst und Verschollen

Documentation

number of missing
number of people missing after an event - qualify with "point in time (P585)"
Descriptionnumber of people reported missing as a result of this event - qualify with point in time (P585). See also number of deaths (P1120) and number of injured (P1339).
Data typeQuantity
Domain
According to this template: earthquake (Q7944) and other disasters, wars, etc.
According to statements in the property:
occurrence (Q1190554)
When possible, data should only be stored as statements
Allowed values
According to this template: whole numbers
According to statements in the property:
0 ≤ 𝓧 ≤ 100,000,000
When possible, data should only be stored as statements
Allowed unitsnot applicable
Example2013 Lushan earthquake (Q11547847) → 23
2011 Tōhoku earthquake and tsunami (Q36204) → 2,523
Sourceexternal reference, articles, etc. (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usageCategory:Pages using Wikidata property P1446 (Q26250030)
Tracking: local yes, WD noCategory:P1446 absent on Wikidata (Q101363767)
See alsonumber of casualties (P1590), number of deaths (P1120), number of injured (P1339)
Lists
Proposal discussionProposal discussion
Current uses
Total259
Main statement25698.8% of uses
Qualifier31.2% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “occurrence (Q1190554): item must contain property “instance of (P31)” with classes “occurrence (Q1190554)” 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/P1446#Type Q1190554, SPARQL
Range from “0” to “100000000”: values should be in the range from “0” to “100000000”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1446#Range, hourly updated report
Units: “novalue”: value unit must be one of listed. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1446#Units, hourly updated report
Integer: values should be integers (ie. they shouldn't have a fractional part) (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/P1446#integer, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P1446#Scope, hourly updated report, SPARQL
Citation needed: the property must have at least one reference (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/P1446#citation needed
Item “number of deaths (P1120): Items with this property should also have “number of deaths (P1120)”. (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/P1446#Item P1120, SPARQL
Item “country (P17): Items with this property should also have “country (P17)”. (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/P1446#Item P17, SPARQL
Item “point in time (P585): Items with this property should also have “point in time (P585)”. (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/P1446#Item P585, SPARQL
Conflicts with “participant (P710): this property must not be used with the listed properties and values. (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/P1446#Conflicts with P710, SPARQL
Conflicts with “instance of (P31): human (Q5): this property must not be used with the listed properties and values. (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/P1446#Conflicts with P31, 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/P1446#Entity types
 
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Vermisst und Verschollen edit

Vermisst und Verschollen sind zwei nicht ganz überlappende Begriffe (de:Verschollenheit). Sollen wir dieser Eigenschaft beide als Alias hinzufügen? -Tobias1984 (talk) 12:55, 18 August 2014 (UTC)Reply

Return to "P1446" page.