@ondewo/csi-client-angular 2.3.1

package/ondewo-csi-api/ondewo-nlu-api/googleapis/google/pubsub/v1beta2/README.md

@@ -0,0 +1,136 @@
+## Overview
+This file describes an API for a Pub/Sub (Publish/Subscribe) system. This system
+provides a reliable many-to-many communication mechanism between independently
+written publishers and subscribers where the publisher publishes messages to
+*topics* and each subscriber creates a *subscription* and consumes *messages*
+from it.
+
+1.  The Pub/Sub system maintains bindings between topics and subscriptions.
+2.  A publisher publishes messages into a topic.
+3.  The Pub/Sub system delivers messages from topics into attached
+    subscriptions.
+4.  A subscriber receives pending messages from its subscription and
+    acknowledges each one to the Pub/Sub system.
+5.  The Pub/Sub system removes acknowledged messages from that subscription.
+
+## Data Model
+The data model consists of the following:
+
+*   **Topic**: A topic is a resource to which messages are published by
+    publishers. Topics are named, and the name of the topic is unique within the
+    Pub/Sub system.
+
+*   **Subscription**: A subscription records the subscriber's interest in a
+    topic. The Pub/Sub system maintains those messages which still need
+    to be delivered and acknowledged so that they can retried as needed.
+    The set of messages that have not been acknowledged is called the
+    subscription backlog.
+
+*   **Message**: A message is a unit of data that flows in the system. It
+    contains opaque data from the publisher along with its *attributes*.
+
+*   **Message Attributes** (optional): A set of opaque key-value pairs assigned
+    by the publisher to a message. Attributes are delivered unmodified to
+    subscribers together with the message data, if there's any.
+
+## Publisher Flow
+A publisher publishes messages to the topic using the `Publish` call:
+
+```data
+PubsubMessage message;
+message.set_data("....");
+message.attributes.put("key1", "value1");
+PublishRequest request;
+request.set_topic("topicName");
+request.add_message(message);
+Publisher.Publish(request);
+```
+
+## Subscriber Flow
+The subscriber part of the API is richer than the publisher part and has a
+number of concepts for subscription creation and use:
+
+1.  A subscriber (user or process) creates a subscription using the
+    `CreateSubscription` call.
+
+2.  A subscriber receives messages in one of two ways: via pull or push.
+
+  *   To receive messages via pull, a subscriber calls the `Pull` method on the
+      `Subscriber` to get messages from the subscription. For each individual
+      message, the subscriber may use the `ack_id` received in the
+      `PullResponse` to `Acknowledge` the message, or modify the *ack deadline*
+      with `ModifyAckDeadline`. See the `Subscription.ack_deadline_seconds`
+      field documentation for details on the ack deadline behavior. Messages
+      must be acknowledged or they will be redelivered in a future `Pull` call.
+
+      **Note:** Messages may be consumed in parallel by multiple processes
+      making `Pull` calls to the same subscription; this will result in the set
+      of messages from the subscription being split among the processes, each
+      process receiving a subset of the messages.
+
+  *   To receive messages via push, the `PushConfig` field must be specified in
+      the `Subscription` parameter when creating a subscription, or set with
+      `ModifyPushConfig`. The PushConfig specifies an endpoint at which the
+      subscriber exposes the `PushEndpointService` or some other handler,
+      depending on the endpoint. Messages are received via the
+      `ProcessPushMessage` method. The push subscriber responds to the method
+      with a result code that indicates one of three things: `Acknowledge` (the
+      message has been successfully processed and the Pub/Sub system may delete
+      it), `Nack` (the message has been rejected and the Pub/Sub system should
+      resend it at a later time).
+
+      **Note:** The endpoint may be a load balancer for better scalability, so
+      that multiple processes may handle the message processing load.
+
+Subscription creation:
+
+```data
+Subscription subscription;
+subscription.set_topic("topicName");
+subscription.set_name("subscriptionName");
+subscription.push_config().set_push_endpoint("machinename:8888");
+Subscriber.CreateSubscription(subscription);
+```
+
+Consuming messages via pull:
+
+```data
+// The subscription must be created without setting the push_config field.
+
+PullRequest pull_request;
+pull_request.set_subscription("subscriptionName");
+pull_request.set_return_immediately(false);
+pull_request.set_max_messages(10);
+while (true) {
+  PullResponse pull_response;
+  AcknowledgeRequest ack_request;
+  ackRequest.set_subscription("subscriptionName");
+  if (Subscriber.Pull(pull_request, pull_response) == OK) {
+    for (ReceivedMessage received in pull_response.received_messages()) {
+      Process(received.message().data());
+      ackRequest.add_ack_id(received.ack_id());
+    }
+  }
+  if (ackRequest.ack_ids().size() > 0) {
+    Subscriber.Acknowledge(ack_request);
+  }
+}
+```
+
+## Reliability Semantics
+When a subscriber successfully creates a subscription using
+`Subscriber.CreateSubscription`, it establishes a "subscription point" for
+that subscription, no later than the time that `Subscriber.CreateSubscription`
+returns. The subscriber is guaranteed to receive any message published after
+this subscription point. Note that messages published before the subscription
+point may or may not be delivered.
+
+Messages are not delivered in any particular order by the Pub/Sub system.
+Furthermore, the system guarantees *at-least-once* delivery of each message
+until acknowledged.
+
+## Deletion
+Both topics and subscriptions may be deleted.
+
+When a subscription is deleted, all messages are immediately dropped. If it
+is a pull subscriber, future pull requests will return NOT_FOUND.

package/ondewo-csi-api/ondewo-nlu-api/googleapis/google/rpc/README.md

@@ -0,0 +1,5 @@
+# Google RPC
+
+This package contains type definitions for general RPC systems. While
+[gRPC](https://github.com/grpc) is using these defintions, they
+are not designed specifically to support gRPC.

package/ondewo-csi-api/ondewo-nlu-api/googleapis/google/streetview/publish/README.md

@@ -0,0 +1 @@
+An API to contribute 360 photos to Google Street View. The API also allows the users to connect photos, update metadata of the photos, generate photo collections, and delete photos.

package/ondewo-csi-api/ondewo-nlu-api/googleapis/google/type/README.md

@@ -0,0 +1,16 @@
+# Google Common Types
+
+This package contains definitions of common types for Google APIs.
+All types defined in this package are suitable for different APIs to
+exchange data, and will never break binary compatibility. They should
+have design quality comparable to major programming languages like
+Java and C#.
+
+NOTE: Some common types are defined in the package `google.protobuf`
+as they are directly supported by Protocol Buffers compiler and
+runtime. Those types are called Well-Known Types.
+
+## Java Utilities
+
+A set of Java utilities for the Common Types are provided in the
+`//java/com/google/type/util/` package.

package/ondewo-csi-api/ondewo-s2t-api/README.md

@@ -0,0 +1,89 @@
+![Logo](https://raw.githubusercontent.com/ondewo/ondewo-logos/master/github/ondewo_logo_github_2.png)
+
+# ONDEWO S2T APIs
+
+This repository contains the original interface definitions of public ONDEWO APIs that support gRPC protocols. Reading the original interface definitions can provide a better understanding of ONDEWO APIs and help you to utilize them more efficiently. You can also use these definitions with open source tools to generate client libraries, documentation, and other artifacts.
+
+The core componenets of all the client libraries are built directly from files in this repo using [the proto compiler.](https://github.com/ondewo/ondewo-proto-compiler)
+
+For an end-user, the APIS in this repo function mostly as documentation for the endpoints. For specific implementations, look in the following repos for working implementations:
+* [Python](https://github.com/ondewo/ondewo-s2t-client-python)
+* [Angular](https://github.com/ondewo/ondewo-survey-client-angular)
+* [JavaScript](https://github.com/ondewo/ondewo-survey-client-javascript)
+* [TypeScript](https://github.com/ondewo/ondewo-survey-client-typescript)
+
+Please note that some of these implementations are works-in-progress. The repo will make clear the status of the implementation.
+
+## Overview
+
+ONDEWO APIs use [Protocol Buffers](https://github.com/google/protobuf) version 3 (proto3) as their Interface Definition Language (IDL) to define the API interface and the structure of the payload messages. The same interface definition is used for gRPC versions of the API in all languages.
+
+There are several ways of accessing APIs:
+
+1.  Protocol Buffers over gRPC: You can access APIs published in this repository through [GRPC](https://github.com/grpc), which is a high-performance binary RPC protocol over HTTP/2. It offers many useful features, including request/response multiplex and full-duplex streaming.
+
+2.  ONDEWO Client Libraries:
+You can use these libraries to access ONDEWO Cloud APIs. They are based on gRPC for better performance and provide idiomatic client surface for better developer experience.
+
+## Discussions
+
+Please use the issue tracker in this repo for discussions about this API, or the issue tracker in the relevant client if it is language-specific.
+
+## Repository Structure
+
+```
+.
+├── CONTRIBUTING.md
+├── LICENSE
+├── ondewo
+│   └── s2t
+│       └── speech-to-text.proto
+├── README.md
+└── RELEASE.md
+```
+
+## Generate gRPC Source Code
+
+API client libraries can be built directly from files in this repo using [the proto compiler.](https://github.com/ondewo/ondewo-proto-compiler)
+
+Automatic Release Process
+------------------
+The entire process is automated to make development easier. The actual steps are simple:
+
+TODOs in Pull Request before the release:
+
+ - Update the Version number inside the Makefile
+
+ - Check if RELEASE.md is up-to-date
+
+TODOs after Pull Request was merged in:
+
+ - Checkout master:
+    ```bash
+    git checkout master
+    ```
+ - Pull the new stuff:
+    ```bash
+    git pull
+    ```
+ - Release:
+    ```bash
+    make ondewo_release
+    ```
+
+The   ``` make ondewo_release``` command can be divided into 5 steps:
+
+- cloning the devops-accounts repository and extracting the credentials
+- creating and pushing the release branch
+- creating and pushing the release tag
+- creating the GitHub release
+
+The variable for the GitHub Access Token is inside the Makefile,
+but the value is overwritten during ``` make ondewo_release```, because
+it is passed from the devops-accounts repo as an argument to the actual ```release``` command.
+
+Proto Documentation
+-------------------
+
+Documentation for the .proto files is generated automatically when there is a pullrequest or push
+to master. It is located in the branch [gh-pages]("https://github.com/ondewo/ondewo-s2t-api/tree/gh-pages").

package/ondewo-csi-api/ondewo-t2s-api/README.md

@@ -0,0 +1,89 @@
+![Logo](https://raw.githubusercontent.com/ondewo/ondewo-logos/master/github/ondewo_logo_github_2.png)
+
+# ONDEWO T2S APIs
+
+This repository contains the original interface definitions of public ONDEWO APIs that support gRPC protocols. Reading the original interface definitions can provide a better understanding of ONDEWO APIs and help you to utilize them more efficiently. You can also use these definitions with open source tools to generate client libraries, documentation, and other artifacts.
+
+The core componenets of all the client libraries are built directly from files in this repo using [the proto compiler.](https://github.com/ondewo/ondewo-proto-compiler)
+
+For an end-user, the APIS in this repo function mostly as documentation for the endpoints. For specific implementations, look in the following repos for working implementations:
+* [Python](https://github.com/ondewo/ondewo-t2s-client-python)
+* [Angular](https://github.com/ondewo/ondewo-survey-client-angular)
+* [JavaScript](https://github.com/ondewo/ondewo-survey-client-javascript)
+* [TypeScript](https://github.com/ondewo/ondewo-survey-client-typescript)
+
+Please note that some of these implementations are works-in-progress. The repo will make clear the status of the implementation.
+
+## Overview
+
+ONDEWO APIs use [Protocol Buffers](https://github.com/google/protobuf) version 3 (proto3) as their Interface Definition Language (IDL) to define the API interface and the structure of the payload messages. The same interface definition is used for gRPC versions of the API in all languages.
+
+There are several ways of accessing APIs:
+
+1.  Protocol Buffers over gRPC: You can access APIs published in this repository through [GRPC](https://github.com/grpc), which is a high-performance binary RPC protocol over HTTP/2. It offers many useful features, including request/response multiplex and full-duplex streaming.
+
+2.  ONDEWO Client Libraries:
+You can use these libraries to access ONDEWO Cloud APIs. They are based on gRPC for better performance and provide idiomatic client surface for better developer experience.
+
+## Discussions
+
+Please use the issue tracker in this repo for discussions about this API, or the issue tracker in the relevant client if it is language-specific.
+
+## Repository Structure
+
+```
+.
+├── CONTRIBUTING.md
+├── LICENSE
+├── ondewo
+│   └── t2s
+│       └── text-to-speech.proto
+├── README.md
+└── RELEASE.md
+```
+
+## Generate gRPC Source Code
+
+API client libraries can be built directly from files in this repo using [the proto compiler.](https://github.com/ondewo/ondewo-proto-compiler)
+
+Automatic Release Process
+------------------
+The entire process is automated to make development easier. The actual steps are simple:
+
+TODOs in Pull Request before the release:
+
+ - Update the Version number inside the Makefile
+
+ - Check if RELEASE.md is up-to-date
+
+TODOs after Pull Request was merged in:
+
+ - Checkout master:
+    ```bash
+    git checkout master
+    ```
+ - Pull the new stuff:
+    ```bash
+    git pull
+    ```
+ - Release:
+    ```bash
+    make ondewo_release
+    ```
+
+The   ``` make ondewo_release``` command can be divided into 5 steps:
+
+- cloning the devops-accounts repository and extracting the credentials
+- creating and pushing the release branch
+- creating and pushing the release tag
+- creating the GitHub release
+
+The variable for the GitHub Access Token is inside the Makefile,
+but the value is overwritten during ``` make ondewo_release```, because
+it is passed from the devops-accounts repo as an argument to the actual ```release``` command.
+
+Proto Documentation
+-------------------
+
+Documentation for the .proto files is generated automatically when there is a pullrequest or push
+to master. It is located in the branch [gh-pages](https://github.com/ondewo/ondewo-t2s-api/tree/gh-pages).

package/package.json

@@ -0,0 +1,49 @@
+{
+  "name": "@ondewo/csi-client-angular",
+  "version": "2.3.1",
+  "description": "ONDEWO Natural Language Understanding (CSI) Platfrom client library for Angular",
+  "author": "ONDEWO GmbH <office@ondewo.com>",
+  "homepage": "https://ondewo.com/",
+  "license": "Apache-2.0",
+  "keywords": [
+    "ondewo",
+    "csi",
+    "api",
+    "client",
+    "ngx-grpc",
+    "grpc"
+  ],
+  "peerDependencies": {
+    "@angular/common": ">=14.1.3",
+    "@angular/core": ">=14.1.3",
+    "@ngx-grpc/common": ">=3.0.2",
+    "@ngx-grpc/core": ">=3.0.2"
+  },
+  "repository": {
+    "type": "git",
+    "directory": "https://github.com/ondewo/ondewo-csi-client-angular"
+  },
+  "module": "fesm2015/ondewo-csi-client-angular.mjs",
+  "es2020": "fesm2020/ondewo-csi-client-angular.mjs",
+  "esm2020": "esm2020/ondewo-csi-client-angular.mjs",
+  "fesm2020": "fesm2020/ondewo-csi-client-angular.mjs",
+  "fesm2015": "fesm2015/ondewo-csi-client-angular.mjs",
+  "typings": "index.d.ts",
+  "exports": {
+    "./package.json": {
+      "default": "./package.json"
+    },
+    ".": {
+      "types": "./index.d.ts",
+      "esm2020": "./esm2020/ondewo-csi-client-angular.mjs",
+      "es2020": "./fesm2020/ondewo-csi-client-angular.mjs",
+      "es2015": "./fesm2015/ondewo-csi-client-angular.mjs",
+      "node": "./fesm2015/ondewo-csi-client-angular.mjs",
+      "default": "./fesm2020/ondewo-csi-client-angular.mjs"
+    }
+  },
+  "sideEffects": false,
+  "dependencies": {
+    "tslib": "^2.3.0"
+  }
+}

package/public-api.d.ts

@@ -0,0 +1,54 @@
+export * from './api/google/rpc/status.pb';
+export * from './api/google/api/annotations.pb';
+export * from './api/google/api/http.pb';
+export * from './api/google/type/latlng.pb';
+export * from './api/ondewo/s2t/speech-to-text.pb';
+export * from './api/ondewo/s2t/speech-to-text.pbconf';
+export * from './api/ondewo/s2t/speech-to-text.pbsc';
+export * from './api/ondewo/t2s/text-to-speech.pbconf';
+export * from './api/ondewo/t2s/text-to-speech.pbsc';
+export * from './api/ondewo/t2s/text-to-speech.pb';
+export * from './api/ondewo/csi/conversation.pbsc';
+export * from './api/ondewo/csi/conversation.pb';
+export * from './api/ondewo/csi/conversation.pbconf';
+export * from './api/ondewo/nlu/intent.pb';
+export * from './api/ondewo/nlu/session.pbconf';
+export * from './api/ondewo/nlu/webhook.pbconf';
+export * from './api/ondewo/nlu/utility.pbsc';
+export * from './api/ondewo/nlu/project-role.pb';
+export * from './api/ondewo/nlu/session.pb';
+export * from './api/ondewo/nlu/common.pb';
+export * from './api/ondewo/nlu/user.pb';
+export * from './api/ondewo/nlu/operations.pb';
+export * from './api/ondewo/nlu/server-statistics.pb';
+export * from './api/ondewo/nlu/session.pbsc';
+export * from './api/ondewo/nlu/user.pbconf';
+export * from './api/ondewo/nlu/aiservices.pbconf';
+export * from './api/ondewo/nlu/aiservices.pbsc';
+export * from './api/ondewo/nlu/user.pbsc';
+export * from './api/ondewo/nlu/entity-type.pbconf';
+export * from './api/ondewo/nlu/project-role.pbsc';
+export * from './api/ondewo/nlu/project-statistics.pbsc';
+export * from './api/ondewo/nlu/agent.pbconf';
+export * from './api/ondewo/nlu/project-role.pbconf';
+export * from './api/ondewo/nlu/agent.pbsc';
+export * from './api/ondewo/nlu/operations.pbconf';
+export * from './api/ondewo/nlu/intent.pbsc';
+export * from './api/ondewo/nlu/webhook.pbsc';
+export * from './api/ondewo/nlu/server-statistics.pbconf';
+export * from './api/ondewo/nlu/agent.pb';
+export * from './api/ondewo/nlu/intent.pbconf';
+export * from './api/ondewo/nlu/operation-metadata.pb';
+export * from './api/ondewo/nlu/utility.pb';
+export * from './api/ondewo/nlu/operations.pbsc';
+export * from './api/ondewo/nlu/context.pbsc';
+export * from './api/ondewo/nlu/utility.pbconf';
+export * from './api/ondewo/nlu/project-statistics.pb';
+export * from './api/ondewo/nlu/server-statistics.pbsc';
+export * from './api/ondewo/nlu/webhook.pb';
+export * from './api/ondewo/nlu/project-statistics.pbconf';
+export * from './api/ondewo/nlu/entity-type.pb';
+export * from './api/ondewo/nlu/context.pb';
+export * from './api/ondewo/nlu/entity-type.pbsc';
+export * from './api/ondewo/nlu/context.pbconf';
+export * from './api/ondewo/nlu/aiservices.pb';