-
Notifications
You must be signed in to change notification settings - Fork 144
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
Universal variables? #106
Comments
I think it's a good idea. It makes things easier across the board. For systems/parsers that use the current variables there could be a translation file in the root. |
Agreed - we've had to adjust on the fly to compare across countries, and making the variable names consistent across the board would help with holistic views of the information. |
👍 on that one, it'd save a lot of munging! |
yep yep |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How do you feel about changing the variable names to be consistent across countries? Right now it is a mix of the variables as described in the sitreps (which include whitespace and punctuation), and more machine-friendly shortened variable names. The change would cover both old and new files. cc @pallih
The text was updated successfully, but these errors were encountered: