Provide instructions on how hasLocation can support a cemetery's local grave addressing scheme

[Stephen-Gates]

Most cemeteries have a map and a unique scheme to specify a grave's location. Not all cemeteries have latitude longitude coordinates for each individual grave. This feature request is to provide instructions in the specification on how the ontology can be extended to support a local grave addressing scheme and enable queries using that scheme.

As an example:

• Toowong Cemetery has a map - https://www.fotc.au/#toowong-cemetery-map
• There is a online tool to find a grave and display it on an interactive map, but the lat,lon coordinates are not shown and the data is not shared - https://brisbane.discovereverafter.com/profile/31724098
• The online tool, in an attempt to standardise local addresses across its database, had made up an address format, e.g. Mon 18 - 2/#/14. This represents that the grave is in Portion 18, Section 2, Grave 14, which is how it is referred to in Toowong Cemetery.

Users of the Toowong Cemetery data may want to query the data using the Portion-Section-Grave scheme. For example:

• Who is buried in Portion 18, Section 2, Grave 14
• Find all the people buried in Portion 18 prior to 1880

This requirement is currently acknowledged as a limitation - https://rdf.muninn-project.org/ontologies/graves-en.html#objectives

Grave location represents a difficulty is that there is no unified standard for archaeological digs and cemetery plots. Assigning basic longitude and latitude is possible through the hasLocation sub properties but it may be desirable to record the native grid coordinates through the use of an hasLocation property with a string. An additional property hasMap exists to provide a reference to an image of the cemetery map or computer readable coordinate system class.

Emphasis added in the quote to the suggested solution that would partially address this requirement.

Instead of using a string, what if people could add their own properties (portion, section, grave)? What are the pros and cons of this and how is is best done?