IBM
diff --git a/‎CONTRIBUTING.md
Lines changed: 9 additions & 27 deletions b/‎CONTRIBUTING.md
Lines changed: 9 additions & 27 deletions
diff --git a/‎README.md
Lines changed: 55 additions & 57 deletions b/‎README.md
Lines changed: 55 additions & 57 deletions
diff --git a/‎docs/tutorials/cli_loopback.md
Lines changed: 12 additions & 12 deletions b/‎docs/tutorials/cli_loopback.md
Lines changed: 12 additions & 12 deletions
@@ -1,38 +1,20 @@
-# Contributing to OASGraph
+# Contributing to OpenAPI-to-GraphQL
 
-This document lists the differences between the contribution guidelines for
-this repository and the general [**Contributing to LoopBack**](http://loopback.io/doc/en/contrib/index.html) guidelines.
+This document lists the differences between the contribution guidelines for this repository and the general [**Contributing to LoopBack**](http://loopback.io/doc/en/contrib/index.html) guidelines.
 
 ### Developer Certificate of Origin
 
-This repository uses a [Developer Certificate of Origin (DCO)](https://developercertificate.org/) instead of a
-[Contributor License Agreement](https://cla.strongloop.com/agreements/strongloop/loopback.io) like most other LoopBack repositories. DCO
-is an easier process to adhere to. [Full text of DCO](https://developercertificate.org/) can be found below, formatted
-for readability. 
+This repository uses a [Developer Certificate of Origin (DCO)](https://developercertificate.org/) instead of a [Contributor License Agreement](https://cla.strongloop.com/agreements/strongloop/loopback.io) like most other LoopBack repositories. DCO is an easier process to adhere to. [Full text of DCO](https://developercertificate.org/) can be found below, formatted for readability.
 
 > By making a contribution to this project, I certify that:
 >
-> (a) The contribution was created in whole or in part by me and I
-    have the right to submit it under the open source license
-    indicated in the file; or
+> (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
 >
-> (b) The contribution is based upon previous work that, to the best
-    of my knowledge, is covered under an appropriate open source
-    license and I have the right under that license to submit that
-    work with modifications, whether created in whole or in part
-    by me, under the same open source license (unless I am
-    permitted to submit under a different license), as indicated
-    in the file; or
+> (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
 >
-> (c) The contribution was provided directly to me by some other
-    person who certified (a), (b) or (c) and I have not modified
-    it.
+> (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
 >
-> (d) I understand and agree that this project and the contribution
-    are public and that a record of the contribution (including all
-    personal information I submit with it, including my sign-off) is
-    maintained indefinitely and may be redistributed consistent with
-    this project or the open source license(s) involved.
+> (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
 
 Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.
 
@@ -56,14 +38,14 @@ If you've pushed a commit and forgot to sign it, fear not, you can sign it as fo
 git commit --amend -s
 ```
 
-Modify the commit message (if desired) -- do not modify the `Signed-off-by` line. Exit edit mode (`esc` followed by `:x` and then `Enter`). 
+Modify the commit message (if desired) -- do not modify the `Signed-off-by` line. Exit edit mode (`esc` followed by `:x` and then `Enter`).
 
 Now force-push the changes by running:
+
 ```
 git push origin +[branch-name]
 ```
 
 Refer to the [official documentation](https://help.github.com/articles/changing-a-commit-message/#amending-older-or-multiple-commit-messages) for modifying multiple commits or an example with screenshots.
 
 If all else fails, ask the LoopBack team for help :)
-
@@ -2,104 +2,103 @@
 ![Travis (.org)](https://img.shields.io/travis/strongloop/oasgraph.svg?style=flat)
 [![Join the chat at https://gitter.im/oasgraph/Lobby](https://badges.gitter.im/oasgraph/Lobby.svg?style=flat)](https://gitter.im/oasgraph/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
+# OpenAPI-to-GraphQL
 
-# OASGraph
 Translate APIs described by [OpenAPI Specifications (OAS)](https://github.com/OAI/OpenAPI-Specification) into [GraphQL](https://graphql.org/).
 
-<img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/translation.png" alt="Overview of translation" width="600">
-
+<img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/translation.png" alt="Overview of translation" width="600">
 
 ## Getting started
-OASGraph can be used in two ways:
 
+OpenAPI-to-GraphQL can be used in two ways:
 
 ### CLI
-The Command Line Interface (CLI) provides a convenient way to start a GraphQL server wrapping an API for a given OpenAPI Specification:
 
-1. Install the OASGraph CLI using:
-    ```bash
-    npm i -g oasgraph-cli
-    ```
-2. Then, run the OASGraph command and point it to an OpenAPI Specification:
-    ```bash
-    oasgraph <OAS JSON file path or remote url> [options]
-    ```
+The Command Line Interface (CLI) provides a convenient way to start a GraphQL server wrapping an API for a given OpenAPI Specification:
 
-For further details, refer to the [`oasgraph-cli` documentation](./packages/oasgraph-cli).
+1. Install the OpenAPI-to-GraphQL CLI using:
+   ```bash
+   npm i -g openapi-to-graphql-cli
+   ```
+2. Then, run the OpenAPI-to-GraphQL command and point it to an OpenAPI Specification:
+   ```bash
+   openapi-to-graphql <OAS JSON file path or remote url> [options]
+   ```
 
+For further details, refer to the [`openapi-to-graphql-cli` documentation](./packages/openapi-to-graphql-cli).
 
 ### Library
-Use OASGraph as a library in your application to generate GraphQL schemas.
 
-1. Install OASGraph as a dependency:
-    ```bash
-    npm i -s oasgraph
-    ```
-2. Require OASGraph and use the `createGraphQlSchema` function:
-    ```javascript
-    const { createGraphQlSchema } = require('oasgraph')
-    // load or construct OAS (const oas = ...)
-    const { schema, report } = await createGraphQlSchema(oas)
-    ```
+Use OpenAPI-to-GraphQL as a library in your application to generate GraphQL schemas.
 
-For further details, refer to the [`oasgraph` documentation](./packages/oasgraph).
+1. Install OpenAPI-to-GraphQL as a dependency:
+   ```bash
+   npm i -s openapi-to-graphql
+   ```
+2. Require OpenAPI-to-GraphQL and use the `createGraphQlSchema` function:
+   ```javascript
+   const { createGraphQlSchema } = require("openapi-to-graphql");
+   // load or construct OAS (const oas = ...)
+   const { schema, report } = await createGraphQlSchema(oas);
+   ```
 
+For further details, refer to the [`openapi-to-graphql` documentation](./packages/openapi-to-graphql).
 
 ## Tutorials
-Here are some guides to further help you get started:
 
-* [CLI + Loopback tutorial](./docs/tutorials/cli_loopback.md): Learn how to quickly spin up GraphQL wrappers using the OASGraph CLI.
-* [Library tutorial](./docs/tutorials/watson.md): Learn how to use OASGraph as a library, and how to improve the resulting GraphQL wrappers using OAS `link` definitions.
-* [LoopBack tutorial](./docs/tutorials/loopback.md): Learn how to use OASGraph to create GraphQL wrappers for APIs created with LoopBack 4.
+Here are some guides to further help you get started:
 
+- [CLI + Loopback tutorial](./docs/tutorials/cli_loopback.md): Learn how to quickly spin up GraphQL wrappers using the OpenAPI-to-GraphQL CLI.
+- [Library tutorial](./docs/tutorials/watson.md): Learn how to use OpenAPI-to-GraphQL as a library, and how to improve the resulting GraphQL wrappers using OAS `link` definitions.
+- [LoopBack tutorial](./docs/tutorials/loopback.md): Learn how to use OpenAPI-to-GraphQL to create GraphQL wrappers for APIs created with LoopBack 4.
 
 ## Characteristics
 
-* **Data-centric**
+- **Data-centric**
   The GraphQL interface is created around the data definitions in the given OAS, not around the endpoints, leading to a natural use of GraphQL.
 
-  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/data-centric.png" alt="Example of data-centric design" width="600">
+  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/data-centric.png" alt="Example of data-centric design" width="600">
 
-* **Nested data**
-  [Links](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#linksObject) defined in the OAS are used to compose data definitions. Furthermore, hierarchical path structures can be used to nest data via the [`addSubOperations`](./packages/oasgraph/README.md#options-addsuboperations) option.
+- **Nested data**
+  [Links](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#linksObject) defined in the OAS are used to compose data definitions. Furthermore, hierarchical path structures can be used to nest data via the [`addSubOperations`](./packages/openapi-to-graphql/README.md#options-addsuboperations) option.
 
-  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/links.png" alt="Example of links resolution" width="600">
+  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/links.png" alt="Example of links resolution" width="600">
 
-* **Automatic query resolution**
+- **Automatic query resolution**
   Automatically generated resolvers translate (nested) GraphQL queries to API requests. Request results are translated back to GraphQL responses.
 
-  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/resolution.png" alt="Example of query resolution" width="600">
+  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/resolution.png" alt="Example of query resolution" width="600">
 
-* **Mutations**
+- **Mutations**
   Non-safe, non-idempotent API operations (e.g., `POST`, `PUT`, `DELETE`) are translated to GraphQL [mutations](http://graphql.org/learn/queries/#mutations). Input payload is type-checked.
 
-  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/mutations.png" alt="Example of mutation" width="600">
+  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/mutations.png" alt="Example of mutation" width="600">
 
-* **Authentication**
-  OASGraph currently supports authentication via API Key and basic auth. OASGraph wraps secured endpoints into a `viewer`, which takes the API key / credentials as input.
+- **Authentication**
+  OpenAPI-to-GraphQL currently supports authentication via API Key and basic auth. OpenAPI-to-GraphQL wraps secured endpoints into a `viewer`, which takes the API key / credentials as input.
 
-  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/auth.png" alt="Example of authentication" width="600">
+  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/auth.png" alt="Example of authentication" width="600">
 
-* **API Sanitation**
+- **API Sanitation**
   Parts of an API that not compatible with GraphQL are automatically sanitized. For example, API parameters and data definition names with unsupported characters (e.g., `-`, `.`, `,`, `:`, `;`...) are removed. GraphQL queries are desanitized to correctly invoke the REST API and the responses are resanitized to create GraphQL-compliant results.
 
-  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/master/docs/sanitization.png" alt="Example of sanitation" width="300">
+  <img src="https://raw.githubusercontent.com/strongloop/oasgraph/openapi-to-graphql/docs/sanitization.png" alt="Example of sanitation" width="300">
 
-* **Custom request options** Provide headers and query parameters to send with every API request. This allows, for example, to handle authentication or tag requests from GraphQL.
-
-* **Swagger and OpenAPI 3 support** OASGraph can handle both Swagger (OpenAPI specification 2.0) as well as OpenAPI specification 3.
+- **Custom request options** Provide headers and query parameters to send with every API request. This allows, for example, to handle authentication or tag requests from GraphQL.
 
+- **Swagger and OpenAPI 3 support** OpenAPI-to-GraphQL can handle both Swagger (OpenAPI specification 2.0) as well as OpenAPI specification 3.
 
 ## Development
-OASGraph uses the [Lerna](https://github.com/lerna/lerna) monorepo management system. After cloning the entire monorepo repository, you can install Lerna with the command `npm install` and then install the dependencies for all of the packages with `lerna bootstrap`.
 
-OASGraph is written in [TypeScript](http://www.typescriptlang.org/). Within each of OASGraph's packages, all source code is contained in the `src` folder. Use `npm run build` or `npm test` to transpile the source files into the final library in the `lib` folder. Entry-point for the library is `index.js` in `lib`.
+OpenAPI-to-GraphQL uses the [Lerna](https://github.com/lerna/lerna) monorepo management system. After cloning the entire monorepo repository, you can install Lerna with the command `npm install` and then install the dependencies for all of the packages with `lerna bootstrap`.
 
+OpenAPI-to-GraphQL is written in [TypeScript](http://www.typescriptlang.org/). Within each of OpenAPI-to-GraphQL's packages, all source code is contained in the `src` folder. Use `npm run build` or `npm test` to transpile the source files into the final library in the `lib` folder. Entry-point for the library is `index.js` in `lib`.
 
 ## Research
-Our research paper, "Generating GraphQL-Wrappers for REST(-like) APIs", can be found [here](https://arxiv.org/abs/1809.08319). The paper describes the challenges of building OASGraph and an experiment in which we evaluated OASGraph against 959 publicly available OAS, provided by [APIs.guru](https://apis.guru/), and successfully created GraphQL interfaces for 89.5% of them.
 
-To run the experiment, in the [`oasgraph` package](./packages/oasgraph), load APIs.guru specifications, found [here](https://github.com/APIs-guru/openapi-directory), into the `/tmp` folder:
+Our research paper, "Generating GraphQL-Wrappers for REST(-like) APIs", can be found [here](https://arxiv.org/abs/1809.08319). The paper describes the challenges of building OpenAPI-to-GraphQL and an experiment in which we evaluated OpenAPI-to-GraphQL against 959 publicly available OAS, provided by [APIs.guru](https://apis.guru/), and successfully created GraphQL interfaces for 89.5% of them.
+
+To run the experiment, in the [`openapi-to-graphql` package](./packages/openapi-to-graphql), load APIs.guru specifications, found [here](https://github.com/APIs-guru/openapi-directory), into the `/tmp` folder:
 
 ```bash
 npm run guru-load
@@ -111,15 +110,14 @@ Then, run tests:
 npm run guru-test <number of APIs to test at most>
 ```
 
-
 ## Similar projects
 
-* [swagger-to-graphql](https://github.com/yarax/swagger-to-graphql) turns a given Swagger (OpenAPI Specification 2.0) into a GraphQL interface, which resolves against the original API. GraphQL schema is based on endpoints, not on data definitions. No links are considered.
+- [swagger-to-graphql](https://github.com/yarax/swagger-to-graphql) turns a given Swagger (OpenAPI Specification 2.0) into a GraphQL interface, which resolves against the original API. GraphQL schema is based on endpoints, not on data definitions. No links are considered.
 
-* [json-to-graphql](https://github.com/aweary/json-to-graphql) turns given JSON objects / arrays into a GraphQL schema. `resolve` functions need to be provided by the user.
-
-* [StackOverflow discussion](https://stackoverflow.com/questions/38339442/json-schema-to-graphql-schema-converters) points to the above projects.
+- [json-to-graphql](https://github.com/aweary/json-to-graphql) turns given JSON objects / arrays into a GraphQL schema. `resolve` functions need to be provided by the user.
 
+- [StackOverflow discussion](https://stackoverflow.com/questions/38339442/json-schema-to-graphql-schema-converters) points to the above projects.
 
 ## License
-[MIT](./LICENSE.md)
+
+[MIT](./LICENSE.md)
@@ -1,34 +1,34 @@
-# OASGraph Quickstart tutorial
+# OpenAPI-to-GraphQL Quickstart tutorial
 
-The purpose of this tutorial is to show how easy it is to use OASGraph CLI in combination with LoopBack.
+The purpose of this tutorial is to show how easy it is to use OpenAPI-to-GraphQL CLI in combination with LoopBack.
 
-With just a single command line instruction, `oasgraph <OAS JSON file path or remote url>`, you can get a GraphQL server running.
+With just a single command line instruction, `openapi-to-graphql <OAS JSON file path or remote url>`, you can get a GraphQL server running.
 
-Please note that while the CLI tool will satisfy most needs, it does not offer the flexibility or functionality of OASGraph's intended usage, as an integrated library. See the [README.md](../../README.md) for more information.
+Please note that while the CLI tool will satisfy most needs, it does not offer the flexibility or functionality of OpenAPI-to-GraphQL's intended usage, as an integrated library. See the [README.md](../../README.md) for more information.
 
 ## Video demo
 
-[![OASGraph](../conveyor_belt.png)](https://www.youtube.com/watch?v=KXUTmM6y-LM "Click here to watch!")
+[![OpenAPI-to-GraphQL](../conveyor_belt.png)](https://www.youtube.com/watch?v=KXUTmM6y-LM "Click here to watch!")
 
 ## Do it yourself
 
 ### Make sure you have installed Node.js
 
-Before you install OASGraph, make sure to download and install Node.js (version 8.9.x or higher), a JavaScript runtime.
+Before you install OpenAPI-to-GraphQL, make sure to download and install Node.js (version 8.9.x or higher), a JavaScript runtime.
 
 To install Node.js, click [here](https://nodejs.org/en/download/).
 
-### Install OASGraph
+### Install OpenAPI-to-GraphQL
 
-OASGraph can be used either as a library, or via its Command Line Interface (CLI). To install the CLI tool, run the following command.
+OpenAPI-to-GraphQL can be used either as a library, or via its Command Line Interface (CLI). To install the CLI tool, run the following command.
 
 ```sh
-npm i -g oasgraph-cli
+npm i -g openapi-to-graphql-cli
 ```
 
 ### Save or locate the OAS
 
-OASGraph relies on the OpenAPI Specification (OAS) of an existing API to create a GraphQL interface around that API. OASGraph can also retrieve a web-hosted OAS.
+OpenAPI-to-GraphQL relies on the OpenAPI Specification (OAS) of an existing API to create a GraphQL interface around that API. OpenAPI-to-GraphQL can also retrieve a web-hosted OAS.
 
 If you are using LoopBack, you can simply copy the URL location of the web-hosted OAS, which should be located at http://127.0.0.1:3000/openapi.json after starting the API.
 
@@ -43,10 +43,10 @@ If you want to generate a GraphQL interface for another API, make sure that API
 
 ### Start GraphQL server
 
-Once OASGraph is installed and the OAS is obtained, you can create and start the GraphQL server. The created GraphQL server is then accessible by default at [http://127.0.0.1:3001/graphql](http://127.0.0.1:3001/graphql).
+Once OpenAPI-to-GraphQL is installed and the OAS is obtained, you can create and start the GraphQL server. The created GraphQL server is then accessible by default at [http://127.0.0.1:3001/graphql](http://127.0.0.1:3001/graphql).
 
 You can specify a local file containing the OAS specification or a remote url such as `http://127.0.0.1:3000/openapi.json`. 
 
 ```sh
-oasgraph <OAS JSON file path or remote url> 
+openapi-to-graphql <OAS JSON file path or remote url> 
 ```