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

more formal definitions #8

Open
kvlahromei opened this issue Mar 3, 2015 · 2 comments
Open

more formal definitions #8

kvlahromei opened this issue Mar 3, 2015 · 2 comments

Comments

@kvlahromei
Copy link
Contributor

If we want to get good formal definitions (see #7 ) we might also bring some more logic into datastructures, so validation might be easier. This includes esp.:

  • attribute.code
  • attribute.order
  • service.id
  • address
  • ...

This might also result in discussions (e.g. do we consider IDs always to be strings (e.g. hashes, hex numbers, ...) or just positive integers, ...)?

@philipashlock
Copy link
Member

It doesn't look like this is properly covered in the documentation, but I think everything (other than hashes/arrays) should be a string.

@kvlahromei
Copy link
Contributor Author

Ok a string. This excludes any special characters that might corrupt any marshelling/serializers or the use within URLs, right? So just an alphanum string?

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

No branches or pull requests

2 participants