From 6c60f58a56de9f148eea5c5573eff433ac90488a Mon Sep 17 00:00:00 2001 From: Tom Christie Date: Thu, 9 Jun 2016 21:51:22 +0100 Subject: [PATCH] Docs update --- docs/tutorial/7-schemas-and-client-libraries.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/tutorial/7-schemas-and-client-libraries.md b/docs/tutorial/7-schemas-and-client-libraries.md index 7900d03f2..7a2ad61c3 100644 --- a/docs/tutorial/7-schemas-and-client-libraries.md +++ b/docs/tutorial/7-schemas-and-client-libraries.md @@ -58,12 +58,17 @@ content type in the `Accept` header. "_type": "document", ... +The default output style is to use the [Core JSON][corejson] encoding. + +Other schema formats, such as [Open API][openapi] (formerly Swagger) are +also supported. + ## Using a command line client Now that our API is exposing a schema endpoint, we can use a dynamic client library to interact with the API. To demonstrate this, let's use the Core API command line client. We've already installed the `coreapi` package -using `pip`, so the client tool should already be available. Check that it +using `pip`, so the client tool should already be installed. Check that it is available on the command line... $ coreapi @@ -125,3 +130,5 @@ TODO - authentication *TODO - document writing an explict schema view.* [coreapi]: http://www.coreapi.org +[corejson]: http://www.coreapi.org/specification/encoding/#core-json-encoding +[openapi]: https://openapis.org/