Property talk:P3335

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

associated hazard
hazards implicit in the subject item: that a sign warns of; that one may encounter in this place, on this thoroughfare; that are inherent properties of (or threats to) the subject; etc.

Represents	hazard (Q1132455)
Data type	Item
Template parameter	|hazards= in en:Template:Infobox hiking trail, for instance
Domain	According to this template: Instances of a geographic location (Q2221906) or thoroughfare (Q83620) or instances of their subclasses According to statements in the property: When possible, data should only be stored as statements
Allowed values	Relevant hazards, first of all those signaled on site through signs (note: this should be moved to the property statements)
Example	Route du Littoral (Q3444090) → rockfall (Q5654036) Pointe du Diable (Q3393714) → shark attack (Q900214) motorcycle (Q34493) → motorcycle accident (Q48802726) conflict (Q180684) → conflict escalation (Q5160184)
Tracking: usage	Category:Pages using Wikidata property P3335 (Q27826775)
See also	activity policy in this place (P5023), Kemler code (P700), GHS hazard pictogram (P5040), GHS hazard statement (P5041), risk factor (P5642), immediately dangerous to life or health (P2129), handled, mitigated, or managed by (P11738)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P3335 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 122 Main statement 118 96.7% of uses Qualifier 4 3.3% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

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/P3335#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/P3335#citation needed

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/P3335#Entity types

Value type “hazard (Q1132455), risk source (Q86923152), vulnerability (Q1178984), damage (Q481609)”: This property should use items as value that contain property “subclass of (P279)”. On these, the value for subclass of (P279) should be an item that uses subclass of (P279) with value hazard (Q1132455), risk source (Q86923152), vulnerability (Q1178984), damage (Q481609) (or a subclass thereof). (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/P3335#Value type Q1132455, Q86923152, Q1178984, Q481609, SPARQL

Remove type constraint

There appear to be no general "hazard" property for hazards associated with activities, objects, processes, etc., and no reason this property needs to be limited to places. I propose removing the type constraint and changing the property name and description correspondingly, as suggested in the proposal discussion a year ago. Swpb (talk) 16:00, 4 December 2017 (UTC)

I edited the English and German labels and descriptions, other languages may still have the old phrasing. I deprecated the constraint, that will prevent it from causing error messages. I also added constraint clarifications to all the constraints, which IMO should be required for all properties... Arlo Barnes (talk) 00:22, 16 December 2020 (UTC)