Group items tagged

microdata
stuff under discussion for HTML 5

represent the rich text messages in a wavelet (casually known as blips)

are typically invisible

data documents

text documents

for example, tags

omits details that we are unable to capture at this point

Each document has an id

Each wavelet is a container for any number of documents.

is composed of an XML document and a set of annotations.

Annotations are key-value pairs that span arbitrary ranges of the XML document

to represent text formatting, spelling suggestions and hyper-links

independent of the XML document structure

A document is a sequence of items

Each item has a key-value map of annotations.

Annotation keys and values are strings

each item conceptually has its own annotation map

more efficient to have just one annotation map for each consecutive run of items with the same annotations

serialization of the document without annotations into a string is not formally an XML document

current annotations update, which is a map of annotation keys to pairs (old-value, new-value), where old-value and new-value are either null or an annotation value

After the final component, the annotations update must be empty

Document operation components can be divided into four classes

do not directly affect the document or the cursor

annotation boundaries (annotationBoundary) change the current annotations update

interaction with annotations

Appendix A.  Protocol Schema

message AnnotationBoundary { // This field is set to true if and only if both ends and changes are // empty. It is needed to ensure that the optional annotationBoundary // component field is not dropped during serialization. optional bool empty = 1; // MUST NOT have the same string twice. repeated string end = 2; // MUST NOT have two updates with the same key. MUST NOT // contain any of the strings listed in the 'end' field. repeated KeyValueUpdate change = 3; }

optional AnnotationBoundary annotationBoundary = 1; optional string characters = 2; optional ElementStart elementStart = 3; optional bool elementEnd = 4; optional int32 retainItemCount = 5; optional string deleteCharacters = 6; optional ElementStart deleteElementStart = 7; optional bool deleteElementEnd = 8; optional ReplaceAttributes replaceAttributes = 9; optional UpdateAttributes updateAttributes = 10;

Chapter 3 Manage Your Wave Contacts Find and add people and groups to collaborate with in Wave.

Chapter 4 Find and Organize Waves Tag, file, search, and filter waves.

Chapter 5 Dive Deeper into Wave Add rich content to your waves like maps and photo slide shows.

Chapter 6 Master Wave's Interface Navigate Wave from the keyboard and customize your Wave interface.

Chapter 7 Wave Gadgets Add interactive content to your waves with gadgets.

Chapter 8 Wave Bots Automatically update the contents of your waves with bots.

Chapter 9     Life with Wave Integrate Wave into your daily workflow.

Chapter 10 Wave in Action See real-world case studies of regular people using Wave to get things done.

Appendix A Frequently Asked Questions Common questions and quick answers about Google Wave.

Appendix B What Wave Can't Do It's not just you. See what's NOT working in the current version of Wave, and what features the Wave team has promised are coming.

Appendix C Contribute to The Complete Guide to Google Wave In the spirit of Google Wave, this guide is a collaborative effort. We need you (yes, you) to help revise and expand this guide as Wave evolves.

our growing compilation of Wave-related links and video clips from across the web.

get someone up-to-speed within minutes, rather than hours

developers can build their own version of Google Wave

Google Wave can be hosted on your own server

the most important aspect of Google Wave. Open-source code fosters innovation

quick adoption

write documents collaboratively

plan events

discuss

create a wave and add people

formatted text, photos, gadgets, and even feeds from other sources on the web

reply

or edit the wave

concurrent rich-text editing

"playback" to rewind the wave to see how it evolved

API that could be used to extend the service

Wave protocol that allows anyone to run a "wave" server

available later this year

the first round clearly goes to Wave

collaborative technology that blurs the lines between email, wiki, SMS and Twitter

Wave integrates many of the features of disparate systems in common use

application programming interfaces would make it easier for third-parties to customise web applications

Microsoft's Bing, launched under the NineMSN banner in Australia

Go offline and the wave data stayed with you

ultimately it would mean a user could save all their work in the browser and dump it on the intertubes when they go back online

waves worked best on standards-compliant, Webkit browsers

emails (which could be translated between languages in real time) to a wave user

wave that was turned back into an e-mail

The same held true for instant messages and tweets

getting people to change their rusted-on habits

a shift from discrete applications to just one to handle all communications

Safari

Mozilla

Chrome

HTML 5 standard

demonstration of what is possible in the browser

email with IM and document-sharing

threaded conversations between multiple users

threads - or "waves," as Google insists on calling them

APIs for adding "waves" to other web services

Wave protocol for communication

open-source "the lion's share" of Wave's code

open protocol