Via Tender: API v3 formal specification
Reported by Travis Bell | February 1st, 2012 @ 08:42 AM | in Moon (closed)
Assigned to Tender discussion #207. As reported in Tender:
Is it possible to create a formal specification for version 3 of the API?
I am in the process of building a Java wrapper library (as I did for v2) and this time I would like the ability to have a reference to a formal spec so that I don't have to do guesswork when it comes to various aspects of it.
For example in v2 I treated the movie revenue field as an int causing the revenue of the movie Avatar to overflow since it was that big (should have been a long).
Also it would help to figure out which fields are expected to always be there and what fields may have no values.
I know that version 3 is a work in progress, which makes a formal specification even more important in my view, since we can always refer to it and make sure we follow the latest requirements.
Comments and changes to this ticket
-
Travis Bell July 23rd, 2012 @ 12:19 PM
- no changes were found...
-
Travis Bell May 15th, 2013 @ 10:12 AM
- State changed from “new” to “invalid”
- Milestone changed from “Icebox” to “Moon”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Travis Bell