Each blip
of a wavelet has a document
Contents contributed and discussions participated by Graham Perrin
6More
rich text "fields" - Google Wave API | Google Groups - 3 views
8More
Google Wave Data Model and Client-Server Protocol (Google Wave Federation Pr... - 1 views
1More
Google Wave Federation - 1 views
www.waveprotocol.org/...wave_federation_pub.pdf
2009 2009-08 2010 2010-06 2010-06-12 Google Wave document annotation Extensible Messaging and Presence Protocol
shared by Graham Perrin on 12 Jun 10
- No Cached
28More
Draft Protocol Spec (Google Wave Federation Protocol) - 1 views
www.waveprotocol.org/...draft-protocol-spec
2010 2010-06 2010-06-12 Google Wave document annotation Extensible Messaging and Presence Protocol
shared by Graham Perrin on 12 Jun 10
- Cached
- ...22 more annotations...
-
to represent text formatting, spelling suggestions and hyper-links
-
more efficient to have just one annotation map for each consecutive run of items with the same annotations
-
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
-
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;
7More
Acrobat 9 and Reader 9 | Acrobat.com - 18 views
8More
MALLET - 11 views
-
statistical natural language processing, document classification, clustering, topic modeling, information extraction, and other machine learning applications to text
- ...4 more annotations...
11More
Launch of co-ment® 2 services | Sopinspace | Public Debate and Co-operation o... - 5 views
- ...8 more annotations...
-
An efficient groupware workspace for text and user management Your own URL Advanced wiki-like editing and versioning SSL Securized communications
co-ment lite: collaborative text commenting and editing - sop - 4 views
7More
Computer scientists create a multilingual search engine - 14 views
OKFN annotator: shortlog - 4 views
12More
co-ment - web-based text annotation - 8 views
- ...6 more annotations...
-
upload any document (MSWord, RTF, OpenOffice Document)
-
It is only the new version (to be deployed in the coming weeks, most likely in January 2010) that markdown is the pivot format and you will be able to use the "latex to markdown" conversion of pandoc to upload texts. With the present version, the best solution is either: - Through OpenDocument and upload, which is a pain when you start from lyx, as lyx to OpenDocument does not work well. - By generating HTML from lyx, displaying it in a browser, creating a new text in co-ment (http://www.co-ment.net/text/add/) and cutting and pasting from the browser to the edition window in co-ment. This is ugly as a method but works well if you don't have images.
-
-
-
"The co-ment 1 services operated on the www.co-ment.net site are now being phased out" - http://www.sopinspace.com/blog/launch-co-mentr-2-services
26More
louisgray.com: Proposed Salmon Protocol Aims To Unify Conversations on the Web - 1 views
- ...21 more annotations...
-
conversations where they are comfortable
8More
Unifying the Conversations (Salmon Protocol) - 7 views
13More
DevHawk - The Last Mile of the Internet - 5 views
- ...9 more annotations...
-
Polling sucks. We think a decentralized pubsub layer is a fundamental, missing layer in the Internet architecture today
-
a fundamental design that looks like this: This picture leaves out multiple publishers and subscribers and the subscriber registration process, but you get the basic idea
-
fine for server subscribers (like, say Google Reader) but not for client subscribers (like, say TweetDeck).
-
the only way to enable client subscribers to play in this async messaging world is via some type of relay service
-
In this approach, the client subscriber makes an outbound connection to some type of relay infrastructure