Property talk:P535

Latest comment: 6 months ago by ShiehJ in topic Make "place of burial" non-obligatory?

Documentation

Find a Grave memorial ID
identifier of an individual's burial place in the Find a Grave database
Associated itemFind a Grave (Q63056)
Applicable "stated in" valueFind a Grave (Q63056)
Data typeExternal identifier
Corresponding templateTemplate:Find a Grave (Q6203793)
Template parameterTemplate:Find a Grave (Q6203793)
Domain
According to this template: persons, animals - mainly dead people
According to statements in the property:
person (Q215627), conjoined twins (Q216866), horse (Q726), animal (Q729), pig (Q787), orca (Q26843), Gorilla (Q36611), horned lizard (Q288720), chimpanzee (Q4126704), group of humans (Q16334295), cenotaph (Q321053), fictional human (Q15632617), memorial (Q5003624), monument (Q4989906) or human (Q5)
When possible, data should only be stored as statements
Allowed values[1-9]\d*
ExampleSon House (Q352999)7951199
Charlemagne (Q3044)6623
Cleveland Abbe (Q505270)1
Sourcehttps://www.findagrave.com/
Formatter URLhttps://www.findagrave.com/memorial/$1
https://it.findagrave.com/memorial/$1
https://nl.findagrave.com/memorial/$1
https://pt.findagrave.com/memorial/$1
https://fr-ca.findagrave.com/memorial/$1
https://es.findagrave.com/memorial/$1
https://fr.findagrave.com/memorial/$1
https://de.findagrave.com/memorial/$1
https://sv.findagrave.com/memorial/$1
Tracking: sameCategory:Find a Grave template with ID same as Wikidata (Q28653681)
Tracking: differencesCategory:Find a Grave template with ID different from Wikidata (Q24690623)
Tracking: usageCategory:Find a Grave template using Wikidata (Q30797911)
Tracking: local yes, WD noCategory:Find a Grave template with ID not in Wikidata (Q24690618)
See alsoFind a Grave cemetery ID (P2025), Online Begraafplaatsen person ID (P9890), BillionGraves cemetery ID (P4352), Cimiterium ID (P9472), CWGC burial ground ID (P1920), Geneanet cemetery ID (P9189), Cemeteries of France ID (P8337), Online Begraafplaatsen cemetery ID (P9884), Veterans Legacy Memorial ID (P12389)
Lists
Proposal discussionProposal discussion
Current uses
Total203,739
Main statement143,962 out of 210,000,000 (0% complete)70.7% of uses
Qualifier4<0.1% of uses
Reference59,77329.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “[1-9]\d*: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P535#Format, hourly updated report, 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/P535#Unique value, hourly updated report, 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/P535#Single value, SPARQL
Item “date of death (P570): Items with this property should also have “date of death (P570)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Lion Monument Lucerne (Q688214)
List of violations of this constraint: Database reports/Constraint violations/P535#Item P570, SPARQL
Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Lion Monument Lucerne (Q688214)
List of violations of this constraint: Database reports/Constraint violations/P535#Item P21, search, SPARQL
Item “date of birth (P569): Items with this property should also have “date of birth (P569)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Lion Monument Lucerne (Q688214)
List of violations of this constraint: Database reports/Constraint violations/P535#Item P569, SPARQL
Item “place of burial (P119): Items with this property should also have “place of burial (P119)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Lion Monument Lucerne (Q688214)
List of violations of this constraint: Database reports/Constraint violations/P535#Item P119, search, 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/P535#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/P535#Scope, SPARQL
  Pattern ^0+([1-9]\d*)$ will be automatically replaced to \1.
Testing: TODO list

Should the death date be obligatory? edit

Perhaps we should add the following restriction? GranD (talk) 16:08, 6 August 2013 (UTC)Reply

Normally, a death date can be found for most of the items with this property. Thus you might want to add such a constraint. --  Docu  at 20:44, 8 August 2013 (UTC)Reply
If there are no comments against this, I think I'll add it in a few days. GranD (talk) 14:45, 9 August 2013 (UTC)Reply
Give it a try. You can easily remove it the next day depending on the result. I added a few other ones for testing as well. BTW the person template didn't work, so I restored the original templates. --  Docu  at 17:33, 9 August 2013 (UTC)Reply
The person template is being discussed with KrBot owner, and as far as I understand there is no problem supporting the template. So I'd rather restore it. (However I won't unless the bot supports it.) GranD (talk) 10:09, 10 August 2013 (UTC)Reply

Instance of animal edit

I've added taxon (Q16521) to the allowed types, since this is used for animals too and even the original proposal mentions animals. Taxon is broader than animal, but it seems that most animals are not instances of or subclasses of anything other than taxon, so that was the only option I could find that wouldn't mean listing every animal separately. If anyone can find a better option, please change it! :) - Nikki (talk) 17:54, 22 July 2015 (UTC)Reply

I've removed it again since that didn't even work... :/ - Nikki (talk) 08:31, 11 August 2015 (UTC)Reply

Label edit

@ChristianKl: I've undone your change to the English label here because "grave people" doesn't make sense, nor is this property limited to people. I'm not sure what the problem with the original label is... if you think there is one, could you explain what it is? :) - Nikki (talk) 20:05, 30 October 2016 (UTC)Reply

@Nikki:The property is added to people and not to graves. I don't think there's a grave in every case. When I look at the semantics of the websites maybe it should be named "memorial ID"? ChristianKl (talk) 21:34, 30 October 2016 (UTC)Reply
The property needs to have "Find a Grave" and "ID" in the label somewhere as the value of the property is an ID used on the "Find a Grave" website, and it is an identifier for a grave (or other memorial) not for a person. While there is usually a 1:1 correspondence between a grave and a notable person that is not always the case. Thryduulf (talk) 21:50, 30 October 2016 (UTC)Reply

New string format edit

As of yesterday, the site has changed its string format and will be retiring the old format. I changed the property accordingly. Hazmat2 (talk) 19:04, 8 November 2017 (UTC)Reply

Dakar Memorial edit

Please see the various issues that appeared with the Find A Grave memorial ID here: INS Dakar Memorial (Q12404080) .

thank you, שילוני (talk) 05:58, 12 March 2019 (UTC)Reply

Make "place of burial" non-obligatory? edit

Considering that Find A Grave hosts memorials for people who were not buried (e.g. cremated, donated to science) or of unknown disposition, it seems to me that, while a logical constraint at first glance, "place of burial" ultimately isn't a given and shouldn't be treated as such. Is there a more general property like "disposition of remains" that could be used as an alternative? LadiesMakingComics (talk) 03:50, 28 March 2019 (UTC)Reply

    • Like the proposal making this non-obligatory. As I have found many entities in Find a grave ID were cremated. Hence, the alert to add <place of burial> irrelevant and rather impossible! jshieh (talk) 12:27, 23 October 2023 (UTC)Reply
Return to "P535" page.