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.

Sign up for GitHub

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

Jump to bottom

Clarify meaning of number #50

Open
Almad opened this issue Feb 11, 2016 · 2 comments
Open

Clarify meaning of number #50

Almad opened this issue Feb 11, 2016 · 2 comments
Labels
t3: discussion

Comments

@Almad
Copy link

Almad commented Feb 11, 2016

For number primitive type, specification says:

Specifies any number.

I think it should be specified what any means. Integers only? Signed? Unsigned? Decimal points—fixed or floats?

If "any" truly means "all of the above", I think it would be useful to explicitly mention it in spec.
@honzajavorek
Copy link
Contributor

Good point. Is -1.7E+3 valid MSON number? This is how JSON Schema does it: http://spacetelescope.github.io/understanding-json-schema/reference/numeric.html

@zdne
Copy link
Contributor

zdne commented Feb 23, 2016

Related apiaryio/api-blueprint#297

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
t3: discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Almad @honzajavorek @zdne