One of the key innovations introduced by web mashups into the integration landscape (basically focusing on data and application integration) is integration at the UI layer. Yet, despite several years of mashup research, no commonly agreed on component technology for UIs has emerged so far. We believe W3C’s widgets are a good starting point for componentizing UIs and a good candidate for reachin...

The W3C’s Geolocation API may rapidly standardize the transmission of location information on the Web, but, in dealing with such sensitive information, it also raises serious privacy concerns. We analyze the manner and extent to which the current W3C Geolocation API provides mechanisms to support privacy. We propose a privacy framework for the consideration of location information and use it to...

The current multi-stakeholder process to define the Do Not Track standard has considered inputs from many parties, including browser vendors, network advertisers, privacy researchers, and the government. However, we feel that average users, the millions of people who will be directly affected by a Do Not Track standard, have been underrepresented. These are the users whose information is collec...

What is the “high level view” of data on the Web that can be traced down within W3C’s rich roadmap of technologies? What the relationships between the “big needs” of data on the Web, and the forthcoming Web standards? A perspective is provided, in a nutshell.

z Text retrieval (e.g. PAT) identify documents in large document bases z Addressing documents (e.g. Xlink) have flexible link models z Document layout (e.g. XSL) transform documents for layout z Document transformation (e.g. tree regular grammars) transform documents from one DTD to the other z Databases (e.g. OQL) map documents into data structures to apply DB techniques z Knowledge bases (e.g...