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

Add missing comma. #75

Merged
merged 1 commit into from
May 24, 2017
Merged

Add missing comma. #75

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/docs/guides/ai-using.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ When looking at what different companies/groups provide we will see there’s a

As a starting point, then, we can think of an API is a set of definitions, protocols, functions and capabilities, which are then implemented in one or more libraries which can then be released as part of an SDK.

The caveat is that this is a good starting point to think about these terms, but not an absolute. In particular "API" has become a somewhat overloaded term. For example, a company may provide a "Speech API" _via a web service_ and then supply additional libraries, bindings or SDKs that can be used with different environments and languages. What makes the "Speech API" in this case different than the more abstract version we discussed above is that it can be used directly without any intermediate libraries by making specially formatted HTTP requests; similar to the requests used by web browsers to obtain the data they use to render web pages.
The caveat is that this is a good starting point to think about these terms, but not an absolute. In particular, "API" has become a somewhat overloaded term. For example, a company may provide a "Speech API" _via a web service_ and then supply additional libraries, bindings or SDKs that can be used with different environments and languages. What makes the "Speech API" in this case different than the more abstract version we discussed above is that it can be used directly without any intermediate libraries by making specially formatted HTTP requests; similar to the requests used by web browsers to obtain the data they use to render web pages.

Most of these APIs use [JSON](http://www.json.org/) (a few use XML) as a standard to transfer data back and forth. This makes it easy to use (and, if necessary, create) wrappers in different languages.

Expand Down