Property talk:P7883

From Wikidata
Jump to navigation Jump to search

Documentation

Historical Marker Database ID
database entries of historical markers
Applicable "stated in" valueHistorical Marker Database (Q21815238)
Data typeExternal identifier
Domaincommemorative plaque (Q721747)
Allowed values[0-9]+
ExampleStage House Tavern (Q67503613)94038
Blackwells Mills Canal House (Q4923612)94091
Millstone School House (Q75829450)37166
William L. Hutcheson Memorial Forest (Q14705640)99139
Bridgewater station (Q4966831)139393
Van Horne House (Q48895869)99260
Kingston Presbyterian Church (Q73331165)122266
Rockingham (Q7355375)33222
Kingston Presbyterian Church cemetery (Q73332954)33194
Opie - Vanderveer Cemetery (Q83196475)96151
Maybury Hill (Q6796997)64133
Landing Lane Bridge (Q6484602)109273
Kirkpatrick Chapel (Q15238589)10016
Old Queens (Q7084807)62695
Winants Hall (Q18159219)10018
Elizabeth Coleman White (Q1331174)34274
McDowell Cemetery (Q72877044)23777
Formatter URLhttps://www.hmdb.org/m.asp?m=$1
See alsoFlorida Historical Marker List ID (P6567), Indiana State Historical Marker Program ID (P9546), NC Highway Historical Marker Program ID (P9492), Nevada SHPO marker ID (P9515), Human Metabolome Database ID (P2057), Open Plaques plaque ID (P1893)
Lists
Proposal discussionProposal discussion
Current uses
Total313
Main statement258 out of 192,588 (0% complete)82.4% of uses
Qualifier196.1% of uses
Reference3611.5% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P7883#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P7883#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
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/P7883#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/P7883#Scope, SPARQL
Type “commemorative plaque (Q721747): item must contain property “instance of (P31), subclass of (P279)” with classes “commemorative plaque (Q721747)” 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/P7883#Type Q721747, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (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/P7883#Item P31, search, SPARQL
Item “main subject (P921): Items with this property should also have “main subject (P921)”. (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/P7883#Item P921, search, SPARQL
Format “[0-9]+: 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/P7883#Format, SPARQL

Adding constraints - type and main subject[edit]

I added type and main subject constraints to distinguish how and where the id is applied. The Historical Marker Database ID represents a commemorative plaque about a subject, but often is being applied to subjects directly. These constraints may affect the way Historical Marker Database IDs are applied, but splitting the commemorative plaque to its own Q enables distinguishing the subject of the plaque from the plaque object about the subject allowing for the plaque Q to be linked and managed separately from the subject while retaining the relationship. Also given the multiple IDs for historic markers it would allow a single Q to cross check and match against for the marker offering clearer and cleaner checks against external content.

Question regarding consideration for this property ids representing a group was mentioned on the WikiProject Cultural heritage talk page.
Seems a bad idea to me. All the examples when the property were created were actual places, and I can't see why we'd want WD to have entries for individual marker plaques in addition to them. Plaques are not statues. Vicarage (talk) 10:20, 4 March 2024 (UTC)[reply]