Property talk:P8424

Documentation

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

OpenHistoricalMap relation ID
identifier of a relation in OpenHistoricalMap, preferably a chronology relation; see also P402, the corresponding property for OpenStreetMap relations

Represents	chronology relation (Q114912920)
Applicable "stated in" value	OpenHistoricalMap (Q25384440)
Data type	External identifier
Allowed values	[1-9][0-9]{0,9}
Example	San Jose (Q16553) → 2705014 (RDF) territorial evolution of San Jose (Q114348668) → 2704719 (RDF) Baden (Q6877935) → 2735469 (RDF) Grand Duchy of Baden (Q186320) → 2660798 (RDF) Kingdom of Württemberg (Q159631) → 2661269 (RDF)
Source	https://www.openhistoricalmap.org/
Formatter URL	https://www.openhistoricalmap.org/relation/$1
See also	OpenStreetMap relation ID (P402)
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 Items with no other external identifier 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/P8424 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 4,608 Main statement 4,602 99.9% of uses Qualifier 5 0.1% of uses Reference 1 <0.1% of uses
Search for values

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

Format “\d+”: value must be formatted using this pattern (PCRE syntax). (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/P8424#Format, 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/P8424#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/P8424#Single value, SPARQL

Conflicts with “instance of (P31): human (Q5), Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836), Wikimedia project page (Q14204246), Wikimedia list article (Q13406463), Wikimedia template (Q11266439)”: 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/P8424#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/P8424#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): 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/P8424#Scope, SPARQL

single values constraint

should probably be relaxed until the superrelation structure is worked out so the individual subrelations can be listed instead. Arlo Barnes (talk) 17:52, 14 July 2020 (UTC)

@Arlo Barnes: I've proposed and started using a new chronology relation type on OpenHistoricalMap. Chronology relations address the horror Wikidatans felt at seeing 1,172 OpenHistoricalMap relation ID (P8424) statements dominate San Jose (Q16553) (whose boundary, to be fair, has had a horrifying history). Now it should be possible to satisfy the single value constraint for just about any whole, semantically consistent feature mapped in OHM. Minh Nguyễn ^💬 01:59, 2 October 2022 (UTC)