Update REST API schema to use open standards

[jathanism]

The release of Django REST Framework 3.5.x introduced support for multiple open API standards including OpenAPI/Swagger and CoreAPI.

See: http://www.django-rest-framework.org/api-guide/schemas/

Swagger, especially, facilitates the ability to do client code generation. This can lay the groundwork for simplifying the ability to create NSoT clients in other languages. At the very least, the new schema definitions are more robust and will provide a means for better programmatic enumeration of API endpoints for clients.

[jathanism]

It appears we may want to wait until DRF 3.6.4 which should be adding support for the generation of response schemas. See: encode/django-rest-framework#4502

[jathanism]

DRF 3.6.4 is out!

For additional context, one of the primary use-cases for a standardized schema is generating a Golang client using go-swagger.

I've started experimenting with using a project called drf_openapi which allows for explicitly setting request AND response serializers to define the schemas for each. This is necessary for any client code generation for strongly-typed languages (such as Go).

[tyler-8]

drf_openapi has been deprecated in favor of https://github.com/axnsan12/drf-yasg/

[jathanism]

Ah yes. I knew that just didn't update the ticket. Thank you!