Intent
This document defines terms used across all the standards in this site which describe the Wave environment.
Dependancies
Format
The gust of this standard is in the terms section in this overview. However, additional terms to help end users understand the system are defined seperately.
Terms
If this is unclear, the Federation Format document may help.
- Wave
- An internet service based on the concept of hosted conversations, described by the standards on this site.
- wave
- The root, searchable, entities in Wave. It's content is stored in a wavelet. (Always use lower case to avoid confusion with the service itself)
- wavelet
- A sequence of blips which limited wave accounts can edit.
- blip
- A rich text message which can contain gadgets, attachments, and/or inputs.
- gadget
- A collaborative tool which is embedded, and stores data in, the wave.
- attachment
- A file downloaded from Wave.
- input
- A "widget", a information gathering tool provided by the operating system. There are several types of inputs.
- annotation
- A key to value pair spanning a length of text.
- Wave adress
- A string representing an end user (or script) of Wave. In the format of username@domain where username is specified by the user and domain is the DNS domain of the Wave Provider.
- May also be in the format alias/user where the alias is a traditional account which the address behaves like and user is another traditional account which the address identifies as.
- tag
- A string or key to value pair which serves to ease searching for specific waves.
- inbox
- A hierarchy of search strings.
- link
- A section of text displayed differently which when "clicked" downloads and displays a new document.
- Wave Provider
- A corperation which replies to the protocols which make up Wave.
Authors/Reviewers
These terms are not used in these documents, but are merely suggestions on terms to use to describe Wave to users.