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

Consistency Things #144

Closed
JaredCubilla opened this issue Sep 16, 2014 · 2 comments
Closed

Consistency Things #144

JaredCubilla opened this issue Sep 16, 2014 · 2 comments
Labels
Milestone

Comments

@JaredCubilla
Copy link
Contributor

As stated in tons of previous issues (#125, #142, #69), we need a lot more standards for things. Different inputs end up with really weird things happening on themes.

@ocram
Copy link
Contributor

ocram commented Sep 17, 2014

If we want everything to be machine-readable and analyzable, yes.

But as it is now, the plain strings without any requirements allow tool/theme authors to print the phone numbers, dates, etc. just as they have been entered by the users.

And it allows users in Japan to enter their study type even if it doesn't match the titles from US/Australia/Canada/Europe that may have been defined in the specification at that point.

When adding the input, either the tools or the user has to transform a user-readable date (e.g. December 31, 2000) into a machine readable one. Same for all the other values, e.g. phone numbers.

@olivif
Copy link
Collaborator

olivif commented May 3, 2016

I think we have already covered the cases mentioned here in other issues, if there is anything specific that we haven't covered please re-open.

@olivif olivif closed this as completed May 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants