Skip to main content

Home/ Web2.0/ Contents contributed and discussions participated by Graham Perrin

Contents contributed and discussions participated by Graham Perrin

Graham Perrin

Annotation - 7 views

  • metadata that augments a range of text in a Document
    Note: annotation — — within the API.
    Whether 'annotation' in the Google Wave Protocol sense is comparable to annotation in the Diigo sense, I don't know
Graham Perrin

rich text "fields" - Google Wave API | Google Groups - 3 views

    Note: discussion of annotations.
    Whether 'annotation' in the Google Wave Protocol sense is comparable to annotation in the Diigo sense, I don't know
Graham Perrin

Google Wave Data Model and Client-Server Protocol ‎(Google Wave Federation Pr... - 1 views

  • Stand-off annotations are pointers into the XML document
  • Documents form a tree
  • independent of the XML document structure
  • ...5 more annotations...
  • represent the rich text messages in a wavelet (casually known as blips)
  • are typically invisible
  • data documents
  • text documents
  • for example, tags
Graham Perrin

Google Wave Federation - 1 views

    Jochen Bekmann, August 2009 - PDF
Graham Perrin

Draft Protocol Spec (Google Wave Federation Protocol) - 1 views

  • Draft
  • Google Wave Federation Protocol Over XMPP
  • Anthony Baxter, Jochen Bekmann, Daniel Berlin, Soren Lassen, Sam Thorogood
  • ...22 more annotations...
  • 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.
  • Each item has a key-value map of annotations.
  • Annotations are key-value pairs that span arbitrary ranges of the XML document
  • to represent text formatting, spelling suggestions and hyper-links
    • Graham Perrin
      … and annotations (page comments, highlights, stuck and floating notes) in the Diigo sense?
  • independent of the XML document structure
  • A document is a sequence of items
  • is composed of an XML document and a set 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;
    Note: this draft of the protocol/specification mentions annotation.
    Whether 'annotation' in the Google Wave Protocol sense is comparable to annotation in the Diigo sense, I don't know.
Graham Perrin

Acrobat 9 and Reader 9 | - 18 views

Graham Perrin

Marginalia - 18 views

Graham Perrin

MALLET - 11 views

  • MAchine Learning for LanguagE Toolkit
  • statistical natural language processing, document classification, clustering, topic modeling, information extraction, and other machine learning applications to text
  • ...4 more annotations...
  • sophisticated tools for document classification
  • tools for sequence tagging
  • open source
  • for analyzing large collections of unlabeled text. The MALLET topic modeling toolkit
Graham Perrin

Mindswap - 19 views

  • Mindswap
  • Maryland Information and Network Dynamics Lab Semantic Web Agents Project
  • The MINDSWAP Group
  • ...3 more annotations...
  • Semantic Web Research Group
  • working with Semantic Web technology
  • inside the MIND LAB at University of Maryland Institute for Advanced Computer Studies
Graham Perrin

Launch of co-ment® 2 services | Sopinspace | Public Debate and Co-operation o... - 5 views

  • Launch of co-ment(R) 2 services
  • co-ment 1 services operated on the site are now being phased out
  • co-ment 2 services
  • ...8 more annotations...
  • threaded discussions of comments
  • annotation
  • high-quality exports
  • imports from commonly used formats
  • structured text
  • large texts, massive commenting
  • English, Spanish, French, Brazilian Portugese, Bulgarian and Norwegian
  • An efficient groupware workspace for text and user management Your own URL Advanced wiki-like editing and versioning SSL Securized communications
Graham Perrin

co-ment | Text annotation and collaborative writing - 9 views

  • Text annotation and collaborative writing
  • co-ment
Graham Perrin

Computer scientists create a multilingual search engine - 14 views

  • Computer Scientists Create a Multilingual Search Engine
  • Mar. 18, 2010
  • query a contents repository written in Interlingua
  • ...3 more annotations...
  • questions formulated in any language
  • answer in the language in which the question was formulated
  • Interlingua is a language-independent contents representation
Graham Perrin

Gravity | About - 10 views

  • Gravity connects people
  • thousands of
  • user-created topic pages
Graham Perrin

co-ment - web-based text annotation - 8 views

  • co-ment : Web-based text annotation
  • write or upload your own texts, submit them for comments and process the comments
  • source code for the full functionality of the co-ment service is distributed as free software
  • ...6 more annotations...
  • upload any document (MSWord, RTF, OpenOffice Document)
    • Graham Perrin
      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 ( 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.
  • or write it directly with your browser
  • work privately on your text with a few chosen collaborators
  • or open the commenting process to the public
  • use comments to improve your document and create new versions of your text
  • export your text (and all comments) in any format (MS Word, OpenOffice Document, etc.)
    "The co-ment 1 services operated on the site are now being phased out" -
Graham Perrin

comt - 0 views

  • Free / open source software Web-based text annotation system
  • COMT is the core engine of co-ment
  • eading Web service for text annotation
  • ...8 more annotations...
  • install and run a text-annotation Web service
  • rights are defined
  • can be specialized for each text
  • AJAX Web interface for displaying annotated texts
  • and for interactive annotation, commenting and discussion
  • Django
  • PostgreSQL or MySQL
  • structured text markdown format
Graham Perrin Proposed Salmon Protocol Aims To Unify Conversations on the Web - 1 views

  • October 17, 2009
  • Proposed
  • Unify Conversations on the Web
  • ...21 more annotations...
  • conversations that occur on downstream aggregation sites
  • parallel discussions on the originating Web site
  • services, including JS-Kit's Echo and Disqus
  • pulling external discussions to the source
  • Salmon Protocol
  • unify the conversations
  • upstream and downstream
  • in all places
  • An Initial Presentation
  • send the new comments to the site which is lacking the full conversation
  • multiple downstream destinations
  • leverages the newest iteration of webfinger
  • fractured conversations
  • conversations where they are comfortable
    • Graham Perrin
      I'm most comfortable in Diigo.
  • could cause confusion
  • implied (all data is public)
  • a test playground for the Salmon Protocol
  • turn this brand-new protocol into a new standard
  • a serious challenge to services like JS-Kit Echo and Disqus
  • including threaded replies
  • the long debate over unified conversations could soon be over
Graham Perrin

Unifying the Conversations (Salmon Protocol) - 7 views

  • Salmon Protocol
  • Unifying the Conversations
  • protocol for comments and annotations to swim upstream to original update sources
  • ...4 more annotations...
  • commentary in a virtuous cycle
  • user centric
  • demo running at the Salmon Playground
  • presentation: Salmon Real Time Commenting FlowSalmon Real Time Commenting Flow
Graham Perrin

DevHawk - The Last Mile of the Internet - 5 views

  • August 27, 2009
  • The Last Mile of the Internet
  • NAT/Firewall issue makes any async messaging based approach useless for clients
  • ...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
  • technically feasible
  • Yes, having to relay messages sucks. But the question is
  • which sucks worse: polling or relaying?
  • Harry Pierson
1 - 20 of 157 Next › Last »
Showing 20 items per page