You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue dates back to the initial release of graves using underscores and then new terms began using camelCase. Embarrassingly, the terms are ignored when spell-checking.
Given that the underscored terms are in active use from years ago, I'm uncomfortable changing them but the state instances must be fixed.
I can owl:sameAs the term or deprecate it, however most sparql implementations will not follow the logical relationship and it will break. There's no happy solution to this, but #11 needs to be fixed.
The use of an underscore and capitalisation appears to be inconsistent in names. For example:
Mass_grave
,EmptyGrave
,WarGrave
monument_title
,siteName
Servicable
,UnServicable
(I'll open a separate issue to correct the spelling of these properties Servicable and UnServicable properties names misspelt #11 )Is there undocumented logic for the current names? If not, perhaps a naming style should be documented and consistently applied.
The text was updated successfully, but these errors were encountered: