This document analyzes how design decisions of a specification's conformance model may affect its implementability and the interoperability of its implementations. To do so, it introduces the concept of variability - how much implementations conforming to a given specification may vary among themselves - and presents a set of well-known dimensions of variability. Its goal is to raise awareness of the potential cost that some benign-looking decisions may have on interoperability and to provide guidance on how to avoid these pitfalls by better understanding the mechanisms induced by variability.

The upcoming Firefox 3.0 release has built-in support for microformats in the form of an API that you can access from a Firefox extension. In this tip, you follow a simple example of how to use this API from within your extension code. You take a skeleton Hello World extension and give it the ability to store an hCard from any Web page and then use that stored hCard to populate a Web form.

The good folks over at the Gartner Group have revealed the top 10 technologies that they believe will change the world over the next four years:Multicore and hybrid processorsVirtualization and fabric computingSocial networks and social softwareCloud computing and cloud/Web platformsWeb mashupsUser InterfaceUbiquitous computingContextual computingAugmented realitySemantics

Members Approve Web Services for Remote Portlets (WSRP) 2.0 as OASIS Standard IBM, Sun Microsystems, Microsoft, Novell, Oracle, SAP, TIBCO, Vignette and Others Collaborate on Open Standard for Integrating Web Services into Portals

Boston, MA, USA; 30 May 2008 — OASIS, the international open standards consortium, today announced that its members have approved the Web Services for Remote Portlets (WSRP) version 2.0 as an OASIS Standard, a status that signifies the highest level of ratification. Developed through an open process by the OASIS WSRP Technical Committee, the new standard simplifies the effort required for aggregating applications, such as portals, to quickly integrate remote content and applications. "Vendors of aggregating applications no longer need to write special adapters to accommodate the variety of interfaces and protocols used by content providers," explained Rich Thompson of IBM, chair of the OASIS WSRP Technical Committee. "With WSRP, they can integrate remote content and applications with just a few mouse clicks and virtually no programming effort. WSRP version 2.0 adds those capabilities needed to fully integrate the remote components into the aggregated application."

Kabak Y., Dogac A. A Survey and Analysis of Electronic Business Document Standards Under revision.

The amount of work it takes to "offline enable" a Web application is roughly similar to the amount of work it takes to "online enable" a desktop application.

I suspect this is the bitter truth that answers the questions asked in articles like  The Frustratingly Unfulfilled Promise of Google Gears where the author laments the lack of proliferation of offline Web applications built on Google Gears. When it first shipped I was looking forward to a platform like Google Gears but after I thought about the problem for a while, I realized that such a platform would be just as useful for "online enabling" desktop applications as it would be for "offline enabling" Web applications. Additionally, I came to the conclusion that the former is a lot more enabling to users than the latter. This is when I started becoming interested in Live Mesh as a Platform, this is one area where I think Microsoft's hearts and minds are in the right place. I want to see more applications like Outlook + RPC over HTTP  not "offline enabled" versions of Outlook Web Access.

I don't think the Atom publishing protocol can be considered the universal protocol for talking to remote databases given that cloud storage vendors like Amazon and database vendors like Oracle don't support it yet. That said, this is definitely a positive trend. Back in the RSS vs. Atom days I used to get frustrated that people were spending so much time reinventing the wheel with an RSS clone when the real gaping hole in the infrastructure was a standard editing protocol. It took a little longer than I expected (Sam Ruby started talking about in 2003) but the effort has succeeded way beyond my wildest dreams. All I wanted was a standard editing protocol for blogs and content management systems and we've gotten so much more.

Microsoft is using AtomPub as the interface to a wide breadth of services and products as George Moore points out in his post A Unified Standards-Based Protocols and Tooling Platform for Storage from Microsoft 

And a few weeks after George's post even more was revealed in posts such as this one about  FeedSync and Live Mesh where we find out Congratulations to the Live Mesh team, who announced their Live Mesh Technology Preview release earlier this evening! Amit Mital gives a detailed overview in this post on http://dev.live.com. You can read all about it in the usual places...so why do I mention it here? FeedSync is one of the core parts of the Live Mesh platform. One of the key values of Live Mesh is that your data flows to all of your devices. And rather than being hidden away in a single service, any properly authenticated user has full bidirectional sync capability. As I discussed in the Introduction to FeedSync, this really makes "your stuff yours". Okay, FeedSync isn't really AtomPub but it does use the Atom syndication format so I count that as a win for Atom+APP as well. As time goes on, I hope we'll see even more products and services that support Atom and AtomPub from Microsoft. Standardization at the protocol layer means we can move innovation up the stack.

As innovation in the consumer space spills over into the enterprise, IBM believes its social software suite that includes blogs and social networks for business will give users the collaboration features they want while giving IT the ability to hook it into existing systems.

Lotus Connections represents IBM's response to a Web 2.0 world.

While analysts say the social software in SharePoint lacks the functionality and usability of competitor products, its tight integration with existing Microsoft systems such as Exchange and Office makes it an attractive buy for IT departments looking to capitalize on the Web 2.0 movement while still utilizing the technology tools they already have inside their companies.

For its part, Microsoft boasts a staggering rate of adoption for SharePoint. According to Rob Curry, director of SharePoint, Microsoft has sold around 100 million licenses of the product

Draft Recommendation — 29 May 2008

Abstract This specification evolves HTML and its related APIs to ease the authoring of Web-based applications. Additions include the context menus, a direct-mode graphics canvas, inline popup windows, and server-sent events. Heavy emphasis is placed on keeping the language backwards compatible with existing legacy user agents and on keeping user agents backwards compatible with existing legacy documents.

Some things are clearer with hindsight of several years. It is necessary to evolve HTML incrementally. The attempt to get the world to switch to XML, including quotes around attribute values and slashes in empty tags and namespaces all at once didn't work. The large HTML-generating public did not move, largely because the browsers didn't complain. Some large communities did shift and are enjoying the fruits of well-formed systems, but not all. It is important to maintain HTML incrementally, as well as continuing a transition to well-formed world, and developing more power in that world.

The plan is, informed by Webforms, to extend HTML forms. At the same time, there is a work item to look at how HTML forms (existing and extended) can be thought of as XForm equivalents, to allow an easy escalation path. A goal would be to have an HTML forms language which is a superset of the existing HTML language, and a subset of a XForms language wit added HTML compatibility.

EPUB Support from list of Publishers An Open Letter from AAP to IDPF

What is EPUB, .epub, OPS/OCF & OEB? ".epub" is the file extension of an XML format for reflowable digital books and publications. ".epub" is composed of three open standards, the Open Publication Structure (OPS), Open Packaging Format (OPF) and Open Container Format (OCF), produced by the IDPF. "EPUB" allows publishers to produce and send a single digital publication file through distribution and offers consumers interoperability between software/hardware for unencrypted reflowable digital books and other publications. The Open eBook Publication Structure or "OEB", originally produced in 1999, is the precursor to OPS. For the latest on IDPF standards, sample files and companies who have implemented our specifications, please visit our public forums.  Getting started? Visit our FAQ's.

TimesMachine is a collection of full-page image scans of the newspaper from 1851–1922 (i.e., the public domain archives). Organized chronologically and navigated by a simple calendar interface, TimesMachine provides a unique way to traverse the historical archives of The New York Times.

Using Amazon Web Services, Hadoop and our own code, we ingested 405,000 very large TIFF images, 3.3 million articles in SGML and 405,000 xml files mapping articles to rectangular regions in the TIFF’s. This data was converted to a more web-friendly 810,000 PNG images (thumbnails and full images) and 405,000 JavaScript files — all of it ready to be assembled into a TimesMachine. By leveraging the power of AWS and Hadoop, we were able to utilize hundreds of machines concurrently and process all the data in less than 36 hours.