Evolution in Data Integration From EII to Big Data
Approaches to integrating data are changing with emergence of cloud computing.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Michael Stal on Jul 02, 2011
In an article for HowStuffWorks Jonathan Strickland addresses his perspective on Web 3.0. He believes in Web 3.0 as a disruptive new technology. Other experts have different opinions what the Web 3.0 is or what it should be. Some think, it might only comprise an evolutionary step, leveraging semantic metainformation. So is it coming and what exactly is the Web 3.0?
Since the increasing penetration of applications like Facebook, Twitter, Flickr as well as new user-based media like blogs or podcasts, the so-called Web 2.0 has become state of the art. However, Web 2.0 is rapidly reaching its limitations in terms of user experience and personalized content. Web 3.0 presumably will be the next step of the Internet evolution. There is a lot of discussion whether Web 3.0 will be just an realization of Tim Berners-Lee’s idea of a Semantic Web. Although most experts have different anticipations regarding the new Web, at least most of them seem to agree on the traits of Web 3.0:
For example, Knowledge@Wharton reports from a panel with Travis Katz, Mitch Kapor, Shannon Berning, and Bryan Sabrian. The panelists agreed that there were too much information in the Web today so that ways are required for filtering out the relevant information. These filtering and search mechanisms, however, need to take the personal profile of the user into account. In addition, the Web could turn into a People Web where the information will more emphasize people and their interactions instead on focusing on the system or infrastructure. ´
In his blog posting called Say Hello to Web 3.0 the author Waqas E. considers seven technologies to be particularly essential for the new incarnation of the Web. The author is not a professional engineer, but reveals some expectations from the user's perspective:
For architects and developers, such a Web 3.0 would definitely have a lot of consequences with respect to application development, if they need to leverage all the aforementioned technologies. Probably, mash-ups and APIs will gain importance.
Although some of the experts statements are very concrete, we should not forget that it is very difficult to anticipate the future. Technologies and concepts in the Web tend to be fast moving targets.The Semantic Web is not developed as experts thought a few years ago. Opinions on the concrete shape and function still vary a lot as described in Wikipedia.
For interested readers, there is an interesting video that reveals some aspects of Web 3.0. So, what do you think, should be part of an upcoming Web 3.0?
I proposed my own vision on the future development of Web in:
on-meaning.blogspot.com/2011/06/great-blunders-...
Briefly said, we should have semantic ecosystem, which will change not only Web itself, but also the way we interact with computers. What Semantic Web lacks is human-friendliness, simple and affordable approach to integrate semantics. And this proposal tries to fill this gap.
Approaches to integrating data are changing with emergence of cloud computing.
Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.
Dave Farley and Martin Thompson discuss solutions for doing low-latency high throughput transactions based on the Disruptor concurrency pattern.
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project.
Dale Schumacher presents several patterns of actor interaction that can be used in collaborative programs written in any language.
Rúnar Bjarnason discusses Scalaz, a Scala library of pure data structures, type classes, highly generalized functions, and concurrency abstractions to perform functional programming in Scala.
One of the main challenges when designing software architecture is considering quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes.
Michael Feathers analyzes real code bases concluding that code is not nearly as beautiful as designers aspire to, discussing the everyday decisions that alter the code bit by bit.
1 comment
Watch Thread Reply