Labs/Site 2.0/Existing site replacement/Site content/Ubiquity: Difference between revisions

Jump to navigation Jump to search

Labs/Site 2.0/Existing site replacement/Site content/Ubiquity (view source)

Revision as of 03:26, 4 July 2009

4 bytes removed ,  4 July 2009
→‎Re-Introducing Ubiquity
Line 29: Line 29:
=== Re-Introducing Ubiquity ===
=== Re-Introducing Ubiquity ===


  As a Labs project, Ubiquity is an investigation into two areas.  The first is '''linguistic interfaces''' -- interfaces where you type what you want to do.  Can such an interface be made practical as a part of everyday internet use?  Can it be made close enough to natural language that people can discover how to use it without special training?  Does it have significant speed advantages over a mouse-based interface?  Can it be made good enough at understanding the user's intentions that it is just as usable as a point-and-click interface?  Can it do all this for more languages than just English?
As a Labs project, Ubiquity is an investigation into two areas.  The first is '''linguistic interfaces''' -- interfaces where you type what you want to do.  Can such an interface be made practical as a part of everyday internet use?  Can it be made close enough to natural language that people can discover how to use it without special training?  Does it have significant speed advantages over a mouse-based interface?  Can it be made good enough at understanding the user's intentions that it is just as usable as a point-and-click interface?  Can it do all this for more languages than just English?


  The second area of investigation is what we call "'verbifying the Web'''.  More and more websites are ''things that you do'' rather than ''places that you go to''.  We Digg things, Tweet things, Google for things, blog things, map things, and so on.  But in most cases, using one of these services requires copying some text, going to the appropriate website, and pasting it into a form.  How about if the interface to the Web treated these services as tools that you can pick up and take with you, to use anywhere, instead of treating them as destinations?
The second area of investigation is what we call "'verbifying the Web'''.  More and more websites are ''things that you do'' rather than ''places that you go to''.  We Digg things, Tweet things, Google for things, blog things, map things, and so on.  But in most cases, using one of these services requires copying some text, going to the appropriate website, and pasting it into a form.  How about if the interface to the Web treated these services as tools that you can pick up and take with you, to use anywhere, instead of treating them as destinations?


Ubiquity commands are small chunks of javascript which can interface with web services.  Any website can offer Ubiquity commands; any Ubiquity user who visits the site can see the commands and choose whether to subscribe to them.  Once subscribed to, those commands can be used anywhere.
Ubiquity commands are small chunks of javascript which can interface with web services.  Any website can offer Ubiquity commands; any Ubiquity user who visits the site can see the commands and choose whether to subscribe to them.  Once subscribed to, those commands can be used anywhere.
Jdicarlo
1,007

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/153441"

Navigation menu