Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent use of underscore and capitalisation in names #10

Closed
Stephen-Gates opened this issue Dec 31, 2021 · 3 comments
Closed

Inconsistent use of underscore and capitalisation in names #10

Stephen-Gates opened this issue Dec 31, 2021 · 3 comments

Comments

@Stephen-Gates
Copy link
Collaborator

Stephen-Gates commented Dec 31, 2021

The use of an underscore and capitalisation appears to be inconsistent in names. For example:

Is there undocumented logic for the current names? If not, perhaps a naming style should be documented and consistently applied.

@rwarren2
Copy link
Contributor

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.

@Stephen-Gates
Copy link
Collaborator Author

Thanks for the reply and that makes sense. I assume there is no concept of an Alias that would enable old and updated names to be used?

This issue can be closed.

@rwarren2
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants