RESTTful API description - JyriKa/PWP-Disc-Golf-Statistics GitHub Wiki
📑 Chapter summary
This chapter must provide a good overview of the Web API that your group is going to develop during the course. You should not focus in implementation aspects such as database structure, interfaces or the request/responses formats. We recommend that you look into existing APIs (see Related work below) before writing the description for your own API.In this Chapter you must describe JUST the RESTful API, NOT THE CLIENT. Remember that client and Web API should be totally decoupled.
- Understand what is an API
- Describe the project topic API
- Describe how the API will be used in the project
✔️ Chapter evaluation (max 8 points)
You can get a maximum of 8 points after completing this Chapter. More detailed evaluation is provided after each heading.📑 Content that must be included in the section
Describe the Web API briefly and comment which is the main functionality that it exposes to clients. Focus in the Web API not in the application which is using this API. Take into account that in the end, a WEB API is an encapsualted functionality as well as the interface to access that functionality. This section CANNOT include a description of an application or client that uses the API.
Justify also why you want to implement this API. Comment why a developer would like to integrate this API into their application. Try to "sell" the API to your potential customers.
A really short version of an overview for the RESTful Web API could be:
“The discussion forum Web API offers different functionalities to structure non-real-time conversations among the people of a group about topics they are interested in certain topic. Messages are grouped in Threads, that at the same time are grouped in Topics. The messages are accessible to anyone, but posts can only be created by providing credentials of a registered user [...] Clients using this service may implement applications similar to [...]“
Remember: The general description IS NOT just a description of the functionality. Try to market your API to potential customers.
✔️ Evaluation criteria(max 2.0 points)
You can get a maximum of 2 points in this section- The description is clearly written and explains what the API is for: 0.5
- The description includes a clear justification of why this project is useful. Why do you want to build this API: 0.5
- The description describes an API - not an application or client: 1.0
- This means that the description is written in terms of the functionality it makes available for clients, and internal working of the API
- tip: don't think about human users when writing the description - think about machines
✏️ Disc-Golf-Statistics API offers functions to store disc golf results. The results are saved as throws of hole. Holes are saved to a specific course. This structure is simple which makes saving and viewing results easy. The API makes following result easier than before and compared to traditional paper scorecards it is a much more efficient way. Clients using this API can collect data of throws for many kind of comparisons like what is the best and the worst result from one track. This kind of comparison makes it possible for instance to build a client which helps the user to get better on disc golf.
📑 Content that must be included in the section
Define the main concepts and describe the relations among them textually. Roughly, a concept is a real-world entity that is expected to be of interest to users. This section will be used in Deadline 3 to generate the list of resources. Students should remember that some of the concepts might not be a resource by themselves, but just a part of it (resource property). In this section, students should not describe the RESTful resources, but identify which are the main ideas of the API. Do not forget to include the relations among the concepts.A description of the main concepts for the Forum API could be:
"The API permits users send messages. The forum contains a list of categories and a list of users. Each category specifies a name, a description and a thread. A thread is [...]The forum may contain 0 or more categories… Each category may have 0 or more threads… Users can write and read messages to a forum thread. A user has a profile, basic information, activity information (stores, for instance, all the messages sent by a user, the messages marked as favorites). [...]The user history contains information of the last 30 messages sent by the user.[…]"
Include a diagram which shows easily the relations among concepts.
This section is important because it outlines the concepts that you will later implement. In particular, the diagram defined here will follow you throughout the project report and you will be adding more details to it.
✔️ Evaluation criteria(max 1.5 points)
In this section you can get a maximum of 1.5 points:- Concepts are named and described: 0.5
- Relations among concepts is clear: 0.5
- A diagram that shows relations between concepts is provided: 0.5
✏️ The course information contains a number of holes, the location (country, city and address) and the name of a course. The hole information contains a possibly added length of hole, the name of the course and the sequence number of holes. The user information consists of a username, a password and an e-mail. 
📑 Content that must be included in the section
Describe at least two clients that could use your Web API. You must explain here which is the functionality provided by the client, and how use the Web API to implement this functionality.✔️ Evaluation criteria(max 2.0 points)
In this section you can get a maximum of 2 points- The client descriptions are written clearly and explain what they are for: 0.5
- Descriptions outline what parts of the API each client uses, and how: 1.0
- At least two more examples of clients are provided (1-2 sentences per client):0.5
✏️ The API is used on the background of the client that user can save the throws and build up the course from throws. User can view results from tracks and holes later. For example average throws of a specific hole or a specific course can be viewed.
The API is used for the client which helps users to get better at disc golf. The API can recommend the best throw count for the hole. Throw count is chosen to fit for user's skill level. Client recommends where user should specially try to get a lower throw count than before. If user have thrown much over par at some hole many times, the client recommends to play safely.
The API can be used for client that saves the throw count automatically. Client can recognize a throw movement by phone's sensors. When client detects a taught movement it starts to count the hole's throw count. All throws from hole are saved to point until user set the hole to be ended. User can also teach client to detect when he takes disc from basket and it ends the counting from the hole.
Client saves how much user uses time averaging for throw and measures by it how much time user have spent at different courses. Measuring is done by data collected using API. Client recommends user to go to disc golf when it fits on calendar.
📑 Content that must be included in the section
Find at least one API that resembles the functionality provided by yours. Explain in detail the functionality provided by the API. Classify the API according to its type (RPC, CRUD REST, pure REST, hypermedia driven ...) justifying your selection. Provide at least one example client that uses this API.The purpose of this task is to get more familiar with what an API is. This will be helpful in describing your own API. Therefore, it is recommended to do this section after you have decided the topic of your project but before writing your API description.
✔️ Evaluation criteria(max 2.5 points)
You can get a maximum of 2.5 points in this secton:- The selected API is similar or related to the project topic: 0.5
- The API classified correctly, and is described in terms of offered functionality: 1.0
- An example of a client that uses this API is provided, explaining briefly what it does: 0.5
- An additional API is provided 0.5
✏️ DGCourseReview API (https://www.dgcoursereview.com/api.php) offers an opportunity to store disc golf statistics precisely. Statistics can be hole's throw count, time and even picture in the pro version. In API:s free version there is a request limit, but in the pro version it is possible to order a suitable request limit. The API has many interesting methods like tournament and shop methods. The API is a hypermedia driven because it uses hypertext. https://www.dgcoursereview.com/ uses this API. This client views for instance upcoming tournaments and course updates. Client also has a forum for disc golf discussions.
| Task | Student | Estimated time |
|---|---|---|
| DL1 | Jyri | 6h |
| additions | Jyri | 1h |