WEB 2.0

The term "Web 2.0" is commonly associated with web applications that facilitate interactive information sharing, interoperability, user-centered design,[1] and collaboration on the World Wide Web. A Web 2.0 site allows its users to interact with each other as contributors to the website's content, in contrast to websites where users are limited to the passive viewing of information that is provided to them. Examples of Web 2.0 include web-based communities, hosted services, web applications, social-networking sites, video-sharing sites, wikis, blogs, mashups, and folksonomies.

HISTORY

The term "Web 2.0" was coined in 1999 by Darcy DiNucci .The Web we know now, which loads into a browser window in essentially static screenfulls, is only an embryo of the Web to come. The first glimmerings of Web 2.0 are beginning to appear, and we are just starting to see how that embryo might develop. The Web will be understood not as screenfulls of text and graphics but as a transport mechanism, the ether through which interactivity happens. It will [...] appear on your computer screen, [...] on your TV set [...] your car dashboard [...] your cell phone [...] hand-held game machines [...] maybe even your microwave oven.

Her use of the term deals mainly with Web design and aesthetics; she argues that the Web is "fragmenting" due to the widespread use of portable Web-ready devices. Her article is aimed at designers, reminding them to code for an ever-increasing variety of hardware. As such, her use of the term hints at – but does not directly relate to – the current uses of the term.The term did not resurface until 2003.[6][7][8] These authors focus on the concepts currently associated with the term where, as Scott Dietzen puts it, "the Web becomes a universal, standards-based integration platform".[9]

CHARACTERISTICS

Web 2.0 websites allow users to do more than just retrieve information. They can build on the interactive facilities of "Web 1.0" to provide "Network as platform" computing, allowing users to run software-applications entirely through a browser.[3] Users can own the data on a Web 2.0 site and exercise control over that data.[3][14] These sites may have an "Architecture of participation" that encourages users to add value to the application as they use it.[2][3]

The concept of Web-as-participation-platform captures many of these characteristics. Bart Decrem, a founder and former CEO of Flock, calls Web 2.0 the "participatory Web"[15] and regards the Web-as-information-source as Web 1.0.

PRINCIPLES

The overall goal of Web 2.0 is to provide an online experience that is much richer than the experience we currently have with Web 1.0. The principles behind this new system are quite different than the Internet that existed a decade ago. One of the most important principles behind Web 2.0 is the fact that web based services are now available that can pull information from a number of different sources to serve them to the user. With this new system, data will be freed and exposed to everyone that wants to view it. In addition to this, the data can be altered in a number of different ways.

The ways in which data can be altered may be different from the original application. However, a number of experts have pointed out that there is no need for new technology to be made available for the release of data that was previously stored. Another powerful principle of Web 2.0 is the permission it gives for the construction of applications that are virtual. When this virtual application is constructed, data and functions can be pulled from a variety of different sources. In most cases, these applications will be small, and they can be deployed quickly within a short period of time. Currently, this function is only made available to a select few corporations.

TAXONOMY

Information taxonomy is a Web developer's best friend because it can help reach those two most elusive goals of effective Web design: user satisfaction and return on investment. Conversely, even the most efficient search engine cannot completely overcome problems caused by poorly conceived or completely absent information taxonomy.

Although search engines have become much more sophisticated in recent years, finding information on the Internet is still often a hit or miss proposition. You may get zero hits or you may get millions of hits. The second scenario is often like trying to find a needle in a haystack, or perhaps like trying to find the right needle in a haystack filled with a million other needles. The volume of unstructured Web content keeps on growing, which further worsens the problem. Even on an intranet Web site, where the content scope is much smaller, frustration will ensue if the site is not well organized or structured.

BENEFITS OF TAXONOMY IN WEB DEVELOPMENT

The life sciences use taxonomy to hierarchically organize all life forms. The library and information sciences specialize in methodologies and techniques of information search and retrieval. By borrowing these methodologies and techniques, we can develop a Web taxonomy framework that unlocks the secret to structured Web content and therefore enables easy and accurate information access.

Taxonomy intersects with many other areas of Web development, including Web site design, content management, and Web search processes. Let's take a look at the benefits of taxonomy in the context of these areas.

RSS

RSS (most commonly expanded as Really Simple Syndication) is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format. An RSS document (which is called a "feed", "web feed",[3] or "channel") includes full or summarized text, plus metadata such as publishing dates and authorship. Web feeds benefit publishers by letting them syndicate content automatically. They benefit readers who want to subscribe to timely updates from favored websites or to aggregate feeds from many sites into one place. RSS feeds can be read using software called an "RSS reader", "feed reader", or "aggregator", which can be web-based, desktop-based, or mobile-device-based. A standardized XML file format allows the information to be published once and viewed by many different programs. The user subscribes to a feed by entering into the reader the feed's URI or by clicking an RSS icon in a web browser that initiates the subscription process. The RSS reader checks the user's subscribed feeds regularly for new work, downloads any updates that it finds, and provides a user interface to monitor and read the feeds.

VERSIONS OF RSS RSS 0.90 was the original Netscape RSS version. This RSS was called RDF Site Summary, but was

based on an early working draft of the RDF standard, and was not compatible with the final RDF Recommendation.

RSS 1.0 is an open format by the RSS-DEV Working Group, again standing for RDF Site Summary. RSS 1.0 is an RDF format like RSS 0.90, but not fully compatible with it, since 1.0 is based on the final RDF 1.0 Recommendation.

RSS 1.1 is also an open format and is intended to update and replace RSS 1.0. The specification is an independent draft not supported or endorsed in any way by the RSS-Dev Working Group or any other organization.

The RSS 2.* branch (initially UserLand, now Harvard) includes the following versions:

RSS 0.91 is the simplified RSS version released by Netscape, and also the version number of the simplified version originally championed by Dave Winer from Userland Software. The Netscape version was now called Rich Site Summary; this was no longer an RDF format, but was relatively easy to use.

RSS 0.92 through 0.94 are expansions of the RSS 0.91 format, which are mostly compatible with each other and with Winer's version of RSS 0.91, but are not compatible with RSS 0.90.

RSS 2.0.1 has the internal version number 2.0. RSS 2.0.1 was proclaimed to be "frozen", but still updated shortly after release without changing the version number. RSS now stood for Really Simple Syndication. The major change in this version is an explicit extension mechanism using XML namespaces.[21]

MODULES OF RSS

The primary objective of all RSS modules is to extend the basic XML schema established for more robust syndication of content. This inherently allows for more diverse, yet standardized, transactions without modifying the core RSS specification.

To accomplish this extension, a tightly controlled vocabulary (in the RSS world, "module"; in the XML world, "schema") is declared through an XML namespace to give names to concepts and relationships between those concepts.

Some RSS 2.0 modules with established namespaces are:

* Ecommerce RSS 2.0 Module

* Media RSS 2.0 Module

* OpenSearch RSS 2.0 Module

PUTTING RSS FEEDS INTO WEB PAGESPutting RSS Feeds into WebCT and Web Pages

Using the Parser on DSU Server

This parser works well with RSS feeds provided as regular XML files. It may not work

well with RSS feeds that are not pure XML files.

Add an RSS Feed in WebCT

1. Copy the RSS feed URL you want to put in WebCT. You can test whether

the URL is valid by entering the URL into the Address box of Internet

Explorer. An XML page should display if it’s a good RSS feed.

2. Go to http://support.dsu.edu/rss/parser/ and enter the feed URL.

3. Copy the new URL returned.

4. Open your WebCT course.

5. Select “Add Page or Tool” > “URL”

6. Paste the copied feed URL into the Address box

7. Enter a title and select an organizer page to hold the new item.

8. Click Add and then select “View” to test it out.

ATOM

The name Atom applies to a pair of related standards. The Atom Syndication Format is an XML language used for web feeds, while the Atom Publishing Protocol (AtomPub or APP) is a simple HTTP-based protocol for creating and updating web resources.

Web feeds allow software programs to check for updates published on a website. To provide a web feed, a site owner may use specialized software (such as a content management system) that publishes a list (or "feed") of recent articles or content in a standardized, machine-readable format. The feed can then be downloaded by websites that syndicate content from the feed, or by feed reader programs that allow Internet users to subscribe to feeds and view their content.

ATOM'S USAGE

Web feeds are used by the blogging community to share recent entries' headlines, full text, and even attached multimedia files.[2] These providers allow other websites to incorporate the blog's "syndicated" headline or headline-and-short-summary feeds under various usage agreements. Atom and other web syndication formats are now used for many purposes, including journalism, marketing, bug-reports, or any other activity involving periodic updates or publications. Atom also provides a standard way to export an entire blog, or parts of it, for backup or for importing into other blogging systems.

It is common to find web feeds on major Web sites, as well as many smaller ones. Some websites let people choose between RSS or Atom formatted web feeds; others offer only RSS or only Atom. In particular, many blog and wiki sites offer their web feeds in the Atom format.

Add an RSS Feed to a Web Page

1. Copy the RSS feed URL.

2. Go to http://support.dsu.edu/rss/parser/ and

enter the feed URL.

3. Copy the new URL returned.

4. Open your website. Open an existing page or

create a new page.

5. Add the feed URL as a link, just like a regular

hyperlink.

WYSIWYG

It is an acronym for What You See Is What You Get. The term is used in computing to describe a system in which content displayed during editing appears very similar to the final output,which might be a printed document, web page, slide presentation or even the lighting for a theatrical event.

BENEFITS

* Easy Usage

eWebEditor can be operated easily. It only needs one line of code to finish the call of eWebEditor, and it only takes less than 5 minutes to complete the integration process with your current content management system.

* Visualized Customization

eWebEditor's user can customize the number of buttons on toolbar, displaying the status bar or not, the size of upload files, the path of upload files, effect of interface etc.

* Code Criterion

As a software product, eWebEditor always emphasize the importance of code criterion in program coding. We believe what we need is not only a software application, but a code criterion. So in the process of consummating the product, we keep on perfecting our code criterion such as making suitable notation and setting up sound organization structure. These criterions not only can be the study reference for programmers, but also can help the product further development.

* Whole Document

eWebEditor offers a detailed and vivid instruction documents, which include End-user Manual, Development Manual, FAQ and some examples. With these documents, you can understand function of every item and apply it in your own system. If these instruction documents cannot solve your problem, you can contact us for technical support at any time.