Property talk:P535
Documentation
identifier of an individual's burial place in the Find a Grave database
List of violations of this constraint: Database reports/Constraint violations/P535#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P535#Item P570, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P535#Item P21, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P535#Item P569, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P535#Item P119, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P535#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P535#Entity types
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 |
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
Should the death date be obligatory?
[edit]Perhaps we should add the following restriction? GranD (talk) 16:08, 6 August 2013 (UTC)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
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)
- I've removed it again since that didn't even work... :/ - Nikki (talk) 08:31, 11 August 2015 (UTC)
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)
- @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)
- 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)
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)
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)
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)
- As long as it's not mandatory, I don't think that matters that much. Still, somehow it seems odd that so many place of burial (P119) statements are missing. This probably makes P535 useful as an alternative. --- Jura 08:05, 6 April 2019 (UTC)
- 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)
- All Properties
- Properties with external-id-datatype
- Properties used on 100000+ items
- Properties with format constraints
- Properties with unique value constraints
- Properties with single value constraints
- Properties with constraints on items using them
- Properties with constraints on type
- Properties with qualifiers constraints
- Properties with entity type constraints
- Properties with scope constraints
- Cemetery properties