Skip to content

Commit

Permalink
More content fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
jharmn committed Jan 14, 2016
1 parent e622056 commit 5669bd4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions guidelines/REUSE.md
Expand Up @@ -15,13 +15,13 @@ The following types are reusable, as defined by the spec:

When authoring API design documents, common object definitions can be utilized to avoid duplication. For example, imagine multiple path definitions that each share a common path parameter, or a common response structure. The OpenAPI specification allows reuse of common object definitions through the use of "references".

A reference a construct in your API design document that indicates "the content for this portion of the document is defined elsewhere". To create a reference, at the location in your document where you want to reuse some other definition, create an object that has a `$ref` property whose value is a URI pointing to where the definition is (more on this in later sections).
A reference is a construct in your API design document that indicates "the content for this portion of the document is defined elsewhere". To create a reference, at the location in your document where you want to reuse some other definition, create an object that has a `$ref` property whose value is a URI pointing to where the definition is (more on this in later sections).

OpenAPI's provides reference capabilities using the [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03) specification.

### JSON Example

``` json
``` js
{
// ...
definitions: {
Expand Down

0 comments on commit 5669bd4

Please sign in to comment.