Today we're introducing Google Fusion Tables on Labs, an experimental system for data management in the cloud. It draws on the expertise of folks within Google Research who have been studying collaboration, data integration, and user requirements from a variety of domains. Fusion Tables is not a traditional database system focusing on complicated SQL queries and transaction processing. Instead, the focus is on fusing data management and collaboration: merging multiple data sources, discussion of the data, querying, visualization, and Web publishing. We plan to iteratively add new features to the systems as we get feedback from users.
Michael, It's interesting that I had already Diigo bookmarked Google Fusion Labs on 26th August. This illustrates something I was observing with Steve the other day; that social bookmarking seems to be 'one-way'. In other words we all stuff things into Diigo, but why? Other than transitory email alerts to new bookmarks, I have no feel for emerging themes, or common bookmarks via Diigo. This is something the Knowledge Hub will no doubt surface in activity streams and emerging themes (I hope!)
This is the developer area of the Legislation API. It's not just for developers though! Anybody interested in getting their hands on legislation or linking to it will find useful information. The Legislation API Developer Zone gives complete documentation for all of the available functionality. You can follow development of this project on Twitter using #opsidev and on the PerSpectIves, the OPSI blog.
Since the announcement that we will discontinue development of Google Wave as a standalone product, many people have asked us about the future of the open source code and Wave federation protocol. After spending some time on figuring out our next steps, we'd like to share the plan for our contributions over the coming months.
We will expand upon the 200K lines of code we've already open sourced (detailed at waveprotocol.org) to flesh out the existing example Wave server and web client into a more complete application or "Wave in a Box."
Open and linked data in action. Nottingham Insight, previously known as NOMAD+, is a shared evidence base that provides access to data, information and intelligence about Nottingham and the surrounding area. This partnership system aims to improve decision-making, support partnership working and better prepare us for the future.
Unvarnished is an online resource for building, managing, and researching professional reputation, using community-contributed, professional reviews...not sure if this is the type of thing we're looking for but could be useful when considering achievements and systems cred stuff?
Integration of remote content and application logic into an End-User presentation has been a task requiring significant custom programming effort. Typically, vendors of aggregating applications, such as a portal, write special adapters for applications and content providers to accommodate the variety of different interfaces and protocols those providers use. The goal of this specification is to enable an application designer or administrator to pick from a rich choice of compliant remote content and application providers, and integrate them with just a few mouse clicks and no programming effort. This revision of the specification adds Consumer managed coordination, additional lifecycle management and a set of related aggregation enhancements.
URIBurner takes an existing Web-accessible resource (webpage, media) and generates an RDF graph of its metadata using existing well-known ontologies as well as site-specific knowledge. URIBurner then re-presents this data as either a new HTML webpage, or directly as RDF in a variety of serializations (RDF/XML, text/n3, turtle, JSON).
A simple but powerful service that delivers RDF-based structured descriptions of Web addressable resources (documents or real world objects) in a variety of formats through Generic HTTP URIs.
The underlying technology is Virtuoso's Sponger, which takes an existing Web-accessible resource (webpage, media) and generates an RDF graph of its metadata using existing well-known ontologies as well as site-specific knowledge. URIBurner then re-presents this data as either a new HTML webpage, or directly as RDF in a variety of serializations (RDF/XML, text/n3, turtle, JSON).