This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
Update vocabulary.md #293
Open
jcstine
wants to merge
1
commit into
main
Choose a base branch
from
jcstine-patch-31
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+16
−14
Open
Update vocabulary.md #293
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,19 +9,21 @@ | |
- **Combo-Component** - a component that performs the functions normally associated with two or more components. An example could be a component with functions of both automatic speech recognition and natural language processing that accepts audio input and produces a semantic structure as an output. | ||
- **Component Interoperability** - the ability, within a voice assistant, to replace one component with another from a different vendor. For the purposes of the Open Voice Network, interoperable components may be recognized within the voice industry as open or proprietary as long as interoperability capabilities are met. | ||
- **Context** - see "Conversational Context," below. Information extracted from _n_ prior utterances of the current conversation. This could include some or all of the following: information that has been input, output, or inferred in Conversational Processors, and the information state of the Dialog Manager. | ||
- **Conversation** - a joint activity in which two or more agents (human or automated) use linguistic forms and non-verbal signals (i.e., gestures) to communicate to achieve an outcome that meets a shared goal. | ||
- **Conversation Event** - A conversation event signals changes in the conversational that may be acted upon. Such an event may be at the beginning or ending of a Conversational Session, completion of a Conversation Processor, decoding of Conversation Information, changes to the state of a Conversation Endpoint, or changes to the status of a Conversation Stream. Any component with access to the system is allowed to generate a Conversation Event. | ||
- **Conversation Facilitator** - coordinates communication between two or more Dialogue Systems and/or Processors during the course of one or more Sessions. This allows dialogue Systems and associated Processors to collaborate regardless of technology being used. Examples of Conversation Information include semantic, lexical, syntactic, and prosodic features. | ||
- **Conversation Information Layer** - represents an abstraction of a type of information in a Dialog System. A layer may be a specific type of acoustic, linguistic, non-linguistic, or paralinguistic features. Examples of layers would be Cepstral features, Phonemes, Intonation Boundaries, Words, Phrases, Turn Boundaries, Syllabic Stress, Discourse Move Tiype, and specific Semantic representation schemes. | ||
- **Conversation Processors** - Conversation information is encoded and/or decoded by one or more Conversational Processors, also known as a Component. Conversational Processors may also take as input the output from another Conversation Processor. A Conversation Processor may generate Conversation Events and Conversation Streams. | ||
- **Conversation Session** - A particular conversation that consists of two or more Conversation Streams (see below) generated by two or more agents through one or more Conversational Endpoints. Sessions may be persistent, but they will often have a start-point and an end-point in time determined by one of the Agents or some other external event. | ||
- **Conversation Stream** - Each Conversational Endpoint generates one or more Conversation Streams based upon the capabilities of the Endpoint and the preferences of the Agent. A Conversation Stream is associated with a particular Agent and may include any media type including text, audio, video, and application UI events. | ||
- **Conversational Agent** - A digital participant in a conversation. This may be an application with a consistent persona, such as Amazon Alexa, Google Assistant, the Target Google Assistant Action, a Facebook Messenger chatbot, or an IVR system at a bank. Conversational agent is a common term utilized in the area of Dialogue System research and university level instruction; the term often is used to describe a human participant in a conversation. For clarity of reference, however, the OVN will use the term "user" to identify a human participant. (See "user" below.) | ||
- **Conversation** - a collaborative linguistic act between two or more conversational agents to achieve a user goal. | ||
- **Conversational Access Point** - the means of carrying a signal to a conversational platform. Users initiate and conduct conversationds through _access points_. An access point can be physical or virtual. Current examples of conversational access points iclude smartphones, smart speakers, personal compiuters, wearables, or microphone-enabled smart home hubs. Access points may be referred to elsewhere as a "device" or a "channel." _In the interoperable world, conversational access points will enable connection to any conversational platform and agent_. | ||
- **Conversational Agent** - A digital participant in a conversation. Conversational agent is a common term utilized in the area of Dialogue System research and university level instruction; the term also used to describe a human participant in a conversation. For clarity of reference, however, the Open Voice Network will use the term "user" to identify a human participant. (See "user" below.) Within the OVON Interoperability Initiative, a _conversational agent_ is perceived by users to be a single conversational actor, and with the ability to not only provide requested information, but _operate on behalf of the user_. It uses the infrastructure of a conversational platform, and uses one or more conversational capabilities to hold conversations with the user, with continuity of knowledge and persona, and a name by which it can be addressed. Enterprise conversational agents reach outside the corporate firewall to fulfill user intents. _In the interoperable world, there will be both general-purpose and specific-purpose conversational agents. Dialogs, data, context, and controls will be passed between agents according to standardized protocols. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would like to see a reference to this research/instruction to shore up our vocabulary. |
||
- **Conversational AI** - is the set of technologies to enable automated communication between computers and humans. This communication can be speech and text. Conversational AI recognizes speech and text, understands intent, decipher various languages, and responds where it mimics human conversation. In some cases, it is also known as Natural Language Processing. | ||
- **Conversational Context** - more research is required and underway; however, as of 2020.12.15, the Open Voice Network will use this definition: information extracted from N prior utterances of the current conversation. This could include some or all of the following: information that has been input, output, or inferred in Conversational Processors, and the information state of the Dialog Manager. | ||
- **Conversational Endpoint** - agents conduct conversations using conversational endpoints; these may be a phone, mobile device, voice speaker, personal computer, kiosk, or any other device that enables an agent to participate in a conversation. Endpoints may be referred to elsewhere as a "device" or a "channel." | ||
- **Conversational Information Packets** - information that relates to a specific period of time. Packets form the input and output of Conversation. | ||
- **Conversational Platform** - A group of technologies that are used as a base for one or more conversational agents; also (see "Platform" below) a business model that harnesses and creates a large, scalable network of users and resources that can be accessed on demand. | ||
- **Conversational Assistant** - is perceived by users to be a single conversation actor, and with the ability to provide requested information. It uses the infrastructure of a conversational platform, and uses one or more conversational capabilities to hold conversationns with the user, with continuity of knowledge and persona and a name by which it can be addressed. Enterprise conversational assistants can reach outside the corporate firewall to fulfill user intents. _In the interoperable world, there will be specific-purpose conversational assistants. | ||
- **Conversational Capability** - provides specific dialog functions that inform an agent. Capabilities do not have a defined name or voice, nor the continuity of discourse context. A capability may be as limited as a response from an IOT sensor ot an information fragment that supports an agent dialog; it may be as expansive as a partial or full dialog on behalf of an agent. _In the interoperable world, conversational capabilities will exist independently from conversational agents and conversational assistants. | ||
- **Conversational Context** - more research is required and underway; however, as of 2020.12.15, the Open Voice Network chose this definition: _information extracted from N prior utterances of the current conversation_. This could include some or all of the following: information that has been input, output, or inferred in Conversational Processors, and the information state of the Dialog Manager. | ||
- **Conversational Event** - A conversation event signals changes in the conversational that may be acted upon. Such an event may be at the beginning or ending of a Conversational Session, completion of a Conversation Processor, decoding of Conversation Information, changes to the state of a Conversation Endpoint, or changes to the status of a Conversation Stream. Any component with access to the system is allowed to generate a Conversation Event. | ||
- **Conversational Facilitator** - coordinates communication between two or more Dialogue Systems and/or Processors during the course of one or more Sessions. This allows dialogue Systems and associated Processors to collaborate regardless of technology being used. Examples of Conversation Information include semantic, lexical, syntactic, and prosodic features. | ||
- **Conversational Information Layer** - represents an abstraction of a type of information in a Dialog System. A layer may be a specific type of acoustic, linguistic, non-linguistic, or paralinguistic features. Examples of layers would be Cepstral features, Phonemes, Intonation Boundaries, Words, Phrases, Turn Boundaries, Syllabic Stress, Discourse Move Tiype, and specific Semantic representation schemes. | ||
- **Conversational Packet** - an input to or an output from a conversational processor. Packets that have start and end times in sequence are a _conversational stream_. | ||
- **Conversational Platform** - the combination of components that enables the operation and management of one or more conversational agents. These components may include natural lanaguage understanding, natural language generation, and dialog management. _In the interoperable world, creators of conversational agents will be able to choose from multiple conversational platform providers_. | ||
- **Conversational Processors** - Conversation information is encoded and/or decoded by one or more Conversational Processors, also known as a Component. Conversational Processors may also take as input the output from another Conversation Processor. A Conversation Processor may generate Conversation Events and Conversation Streams. | ||
- **Conversational Session** - A particular conversation that consists of two or more Conversation Streams (see below) generated by two or more agents through one or more Conversational Endpoints. Sessions may be persistent, but they will often have a start-point and an end-point in time determined by one of the Agents or some other external event. | ||
- **Conversational Stream** - Each Conversational Endpoint generates one or more Conversation Streams based upon the capabilities of the Endpoint and the preferences of the Agent. A Conversation Stream is associated with a particular Agent and may include any media type including text, audio, video, and application UI events. | ||
|
||
|
||
## D | ||
|
@@ -53,7 +55,7 @@ | |
## O | ||
- **Organization** - a group of individuals brought together for a specific purpose, including the creation, transaction, and delivery of products or services. Examples would include a for-profit business, a not-for-profit group, or government agency. | ||
## P | ||
- **Platform** - The collection of components (the environment) needed to execute a voice application. Examples of platforms include the Amazon and Google platforms that execute voice applications. | ||
- **Platform** - The collection of components (the infrastructure) needed to execute a voice application. Examples of platforms include the Amazon and Google platforms that execute voice applications. | ||
|
||
## Q | ||
- **Query** - user’s word requesting for specific function and expecting a particular response. | ||
|
@@ -68,7 +70,7 @@ | |
|
||
## U | ||
- **Utterance** - spoken or typed phrases. | ||
- **User** - a person who interacts with channels. | ||
- **User** - a person who interacts with access points, and through access points, conversational assistants and agents. | ||
|
||
## V | ||
- **Voice Application** - also known as skill, action, capsule or domain. This is the specific executable component that has association to multiple things such as invocation, collection of related intents and entities up to the configuration to your dialog manager. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conversational Agent is defined below as a "digital participant". Is the intent to restrict /conversation/ to digital agents as well? (I would find this confusing.)