How to indicate a "Threatened" Headstone; Add #AtRisk term to ontology.

[Stephen-Gates]

In cemeteries, headstones can often be at threat of becoming Unserviceable. This is often due to trees growing in or near the grave and their roots or branches pushing over the headstone.

It is useful to indicate that a Headstone is "Threatened" so family, or others responsible for maintaining the grave site, can be contacted to take steps to avoid the headstone becoming Unserviceable.

Is a new status needed to indicate this status?

[rwarren2]

Unserviceable was originally meant for a thing that can no longer serve its purpose in terms of leaky roof, broken engine, etc...

What about #AtRisk as a term?

[Stephen-Gates]

I read Unservicable - The object is incapable of functioning but may be repairable, as applicable to a headstone. E.g. A headstone was toppled by a tree; has fallen and broken into pieces; is lying facedown so not readable; but is repairable.

State changes from Serviceable > AtRisk > Unservicable to potentially Ruins or, if repaired, Rebuilt (on a date), then Serviceable.

Is that the correct interpretation?

[rwarren2]

I think that makes sense. I really had machinery in mind for Unservicable, but it still works for things like tombstones that are expected to be read. Let's go with it.

[Stephen-Gates]

Sorry I should have made this a discussion item. I've added some #49 use cases for headstone states in the discussion forum. It raises some questions about when the status should change from/to Un/serviceable.