Section 2.0: Best Practices

Public works and transportation Web sites pose unique challenges not found in a more “traditional” Web site. Most of the information that a city or county agency would present on a Web site has already been developed for an alternative form of publication. Public planning documents, highway system maps, meeting minutes, ordinances and other documents have already been delivered in one form or another, and a copy exists in some form of electronic media (on a hard disk, CD-ROM, etc.). An effective city or county Web site converts this information to a Web based format and uses the Internet to deliver it to a new audience. The most successful sites are the ones that are the most efficient at this process.

2.1 Web Sites and the Internet

The Internet is a global network of computers that share information and are connected together by common “languages” (called protocol). The World Wide Web is the part of this global network in which all of the documents that are accessible using sub-protocol called Hypertext Transfer Protocol or HTTP).

There is no need to understand all of the various workings of the Internet in order to publish a Web site, but the basics are important. In order for information to be published on the Internet, it must be able to be stored on a server and must be in a format that can be delivered by the requested protocol and correctly “decoded” or “interpreted” by the requesting client.[1]

World Wide Web files are stored on a computer referred to as a server. A server “listens” to all of the traffic on the World Wide Web and answers (serves) all requests that are directed (routed) to it. A computer designated as a server has a number of software packages installed that are designed to handle requests on different sub-protocols. One of those software packages is usually a Web server. This particular software package is designed to handle all incoming and outgoing data that uses the HTTP sub-protocol. There are often other types of server packages installed - for instance, e-mail servers and news group servers. Throughout this guidelines document, a “server” is defined as the computer that holds the software, and a “Web server” is the actual software package that makes a Web site possible. If the distinction is not important, the term “server” is simply used.

A Web browser makes requests to a Web server. This browser is software that resides on a user’s computer and is designed to use various Internet languages (specifically, the TCP/IP protocol) to talk to an Internet server. A browser is referred to as client software. In this document, the term “user” or “viewer” means the actual person requesting information from an Internet site. “Client” will never refer to a person; these terms will be used to refer to software installed on a user’s computer.

Client-server transactions are made through Uniform Resource Locators (URLs). A URL is often referred to as an “Internet Address”. The URL defines the language to use, the server being requested and the name of the file being requested from the server. The transfer of information from a server to a client is often referred to as a “download.” Transfers in the opposite direction, from a user’s computer to the server, are called “uploads.”

Bandwidth refers to the ability of the client-server connection to transfer information. Bandwidth describes how fast that connection is and how much information can be carried simultaneously. A good analogy is a pipe. The larger the pipe, the more water it can deliver. The higher the water pressure, the faster the water is delivered. A good high-bandwidth connection delivers information quickly and the speed of the transmission does not drop off as more users are added. High bandwidth is important if the server is expected to deliver large amounts of data without forcing users to wait too long for that information.

Most of the documents stored on a Web server are written in a special language called HyperText Markup Language (HTML). Existing data and graphic files are translated into HTML in order to provide common formatting instructions for the client software. These formatting instructions (markup) can include links (hyperlinks) to other documents on the same server or on other servers on the World Wide Web. Hyperlinks use URLs to identify these documents. It is important to understand what HTML is and is not. HTML is a language to format and deliver data, not a language to create data or graphics. (See Appendix A.1 - What is HTML? for a detailed discussion of HTML).

Project v. Enterprise

A Web site is a collection of documents, usually on one server, connected by a common theme. A Web site can be one page or hundreds of pages of information, text, graphics, etc. Because the term “Web site” can encompass such a wide range, more specific organizational terms, project and enterprise, are used in this document.

A project is a Web site published for a specific purpose, often part of a larger enterprise, but also likely to be able to stand-alone. This report will be published as project on the LRRB enterprise, one of many projects presented by that enterprise. The focus of a project site should be narrow and often has a specific lifespan.

An enterprise is a collection of information on a related topic. In contrast to a project Web site, an enterprise has a wider focus and often an open-ended lifespan. Enterprise sites are often comprised of a number of related project sites and are often published by large groups. The Local Road Research Board’s Web site is an example of an enterprise.

In this document, the terms project and enterprise indicate the scope of a Web site. The term Web site will refer to either or both, and will only be used when the scope of a Web site is irrelevant.

2.2 Typical Web Site Workflow

2.2.1 Design and Publish Cycle

There are four basic steps to publishing a Web site: creating, converting, editing and publishing. Each of these steps is described below:

Creating

HTML documents form the basis of most Web sites, but rarely do information publishers compose documents for publication in HTML. Word processing applications, such as Microsoft Word or WordPerfect, are generally better suited for writing and composing text documents. While today’s “What-You-See-Is-What-You-Get” (WYSWYG) HTML editors have some built-in word processing features, it is generally more desirable to create word processing documents and convert them to HMTL, even if HTML is the primary format for publication.

Graphic elements are created with special software dedicated to creating or editing digital images.

Converting

Converting an existing document is the common method of generating an HTML file. Most modern word processing applications are capable of saving files in HTML format. Most image creating/editing programs are capable of creating images in one of the image formats - or can convert existing images - that can be used in a Web page (see Section 2.3.4 - Core Standards). Adobe’s Photoshop and Illustrator products, Macromedia’s Freehand and Fireworks, and Corel Draw are examples.

To speed the conversion process, it is standard practice to develop a Web page template or templates. A template is an HTML page with graphics, logos and other elements of a Web site that are consistent from page to page. Templates contain “placeholders” for elements that are unique to each individual page. Modern WYSIWYG editors can be employed to manage the templates, and make converting existing content to HTML and inserting into templates easier.

For detailed recommendations for converting documents, including a discussion of which document types convert easily and which pose additional challenges, see Appendix B - Data Conversion.

Editing

Once a text document has been converted to HTML, there are often still a number of details to add. Graphics must be linked to the layout and hyperlinks to other documents added. Long text files are often broken up into several smaller HTML documents that are hyperlinked together. Some of the graphic elements of a document that was designed for print must be changed to take advantage of a digital medium. Special software is often employed at this point, although no special tools are required. HTML is an ASCII text language, and any plain text editor (such as Notepad in Windows) can be used, however many sophisticated HTML editing packages exist.[2]

Publishing

When the HTML editing phase is complete, the documents must be published. Special software is used to transfer (upload) the files to the server. Any graphics included with the HTML layout need to be uploaded as well. Then the layout is tested to make sure all of the hyperlinks work correctly and that all of the linked graphics display properly.

2.2.2 Maintenance Cycle

A good Web site does not end with the Design and Publish cycle. Maintaining and updating a Web site can be a significant commitment as well, and it is crucial to a successful web site. Web sites should be evaluated at regular intervals and information should be kept as up-to-date as possible. Section 3.2.1 - Minimum Content has suggestions for an effective review/update schedule for different types of content.

2.3 Four Questions for Every Project

Properly planning a Web project or enterprise can make the difference between success and failure. There is some basic information that must be gathered at the beginning of the process. This section details that information in the form of four questions to be answered.

2.3.1 Who Hosts the Site and How is it Being Hosted?

This is an important technical question, but it goes far beyond logistics. There are several issues that need to be addressed, and in addition to “who,” “how” must also be answered.

Web site hosting can be complex, and there are a number of details that must be configured exactly right before a Web sight can be found on the Internet. First, the server must be connected to the Internet. This is the job of a third party, called an Internet Service Provider (ISP). There are many ISPs, each offering a different level of service. In many cases a local telephone or long distance provider is also an ISP. Other companies exist purely to provide Internet access. In some areas, a local cable television company can also provide access to the Internet.

After the server is connected to the Internet, a domain name (i.e., www.yahoo.com or www.lrrb.gen.mn.us) must be secured. There are several private companies, nationally and overseas, that can secure domain names. A domain name is associated with a particular server, but they can be easily transferred from one server to another. [3]

After the domain name is registered, there are numerous software and hardware adjustments required for the server before any Web site information can be loaded. Because of the number of details involved, it is often best to have the Web site hosted by a third party who specializes in Web site hosting. Often an ISP will also provide Web hosting services, and can roll all of the costs into one package, that include Internet access, domain registration and Web hosting. Since hosting a Web site requires tight integration among these components, having one company arrange all of the services is often very convenient and some vendors offer package discounts.

Unless a Web enterprise needs to provide a high level of interactivity, or has special needs that an ISP cannot meet, it is generally best to contract the Web hosting to a third party specialist.

Who Hosts the Site?

The Web design team for a project or an enterprise must understand who is hosting the site and how. Is the Web server on an internal computer, or is the site hosted remotely by a third party? What will the URL (the “address”) of the Web site be? If the Web site is hosted remotely, what type of access to the server is allowed? What are the procedures for accessing the server? Will the design team have direct access to the server, or will they hand off HTML files to a third party who will be responsible for transferring them to the server?

Who hosts the site, and the type of access that the Web design team has to the server, will influence project planning. Access can determine how often the Web design team is able to update the site. Often, the level of access to the server will determine what kinds of “extras” or interactive enhancements to the Web pages the designers will be able to make.

How is the Site being Hosted?

Modern Web servers can be any one of a number of different “platforms”. Platform refers to the operating system of the host and the software that “runs” the Web server. Fifty percent of the Web servers on the Internet are some type of Unix operating system (Unix, HP-Unix, Linux, etc.). Other platforms used include: Windows NT, Windows 2000 and Macintosh. BE and AS400 platforms are rare. In addition to the operating system, numerous software packages enable a computer to be a Web server.

Although almost all of these packages conform to a minimum set of standards and protocols (see Section 2.3.4 - Core Standards), each implementation is unique, and each Web server package adds different capabilities in addition to that minimum set of standards. Each platform has advantages and disadvantages; however, a discussion of each is not within the scope of this document. The fact that differences exist and require special handling in the publishing phase is important to note.

When designing a Web site for a project or an enterprise, the platform of the server dictates the type of technology that can be used. With today’s emphasis on interactive Web experiences, knowing the server platform at the beginning of the project is essential to proper planning. Server platform also effects how the HTML files are transferred from the development environment to the server environment in the publishing phase (see Section 2.2 - Typical Web Site Work Flow).

At the project level, the Web server platform is often fixed and out of the control of the Web design team. A project Web site should flexible enough to take advantage of the server platform, but should not be limited by it. The server platform is an important point to consider when planning an enterprise site.

2.3.2 How Often Will the Site be Updated?

The strength of a Web site is the ability to publish and distribute information quickly, and to easily update that information. Typically, Web site information is distributed faster and is less expensive to produce than printed material.

The goals of a project or enterprise are used to plan an update schedule. Update schedules may be in conjunction with key milestones in a project, or may involve weekly project summaries or monthly newsletters. Part of that decision will also be influenced by external factors. Who hosts the site (see Section 2.3.1 - Who Hosts the Site) and the type of access to the server can influence the update schedule. A Web design team with direct access the Web server is better positioned to accomplish frequent updates. Projects or enterprises that do not have direct access to the server might be limited to monthly or quarterly updates.

The update schedule should be published. Posting a schedule will let viewers know when to return for updated material. Updated material should be highlighted so that viewers can quickly sift through information that they have already read. Keeping a site fresh is essential for attracting repeat visitors. If the update schedule cannot be met, serious consideration should be given to reducing the amount of information presented.

2.3.3 How Long is the Information Valid?

There is often a tendency to leave information on a Web site after it has served its purpose. A regular update schedule will reduce the amount of outdated material, but as a site or enterprise evolves, some of its content no longer has a use. Information should be dated whenever possible. It is not always possible (or practical) to remove out-of-date material, especially at the enterprise level, and dating the information will make it easier for the reader to determine which piece of information is essential.

Part of a regular update schedule could include a schedule for “archiving” information (see Section 2.3.2 - How Often Will the Site be Updated?). Information that has some value to the reader but is no longer current could be moved into a section of archived information. Archived information should be clearly labeled and dated, and ideally be presented in a section of the Web site separate from current information.

2.3.4 What is the Best Format for the Information?

A number of formats exist that enable information to be published on the World Wide Web. Text can be presented as a plain text file, HTML file or other proprietary formats like Microsoft Word, Rich Text Format (RTF), WordPerfect, etc. Graphics can be simple a Joint Photographic Group (JPEG) file or a Graphic Interchange Format (GIF) file, or can presented as Computer-Aided Design (CAD) drawings, a Tagged Image File Format (TIFF) file, a Window MetaFile (WMF) file, etc. Some of these formats need special Web browser add-ons (called plug-ins), and others are core standards that can be displayed by any browser.

The choice of formats is usually driven by the audience, the goals of the Web site, and the technical restraints of the Web server and server platform. Since the audience of a city/county highway Web enterprise or product is diverse, the goal, generally, is the broad distribution of information; most of the critical information should be presented in one of the standard formats described next.

Core Standards for Web Browsers

The World Wide Web Consortium (W3C) an international standards organization, has several core standards [4]. These are a “minimum” set of standards to which all Web browsers must adhere. If a Web site uses these standards, every Web browser will be able to display the information published. [5]

The standard for text is Hypertext Markup Language (HTML) - or the newer standard, XHTML. (See Appendix A.1 - What is HTML?). This simple programming language is used to add formatting and display information to plain text. As described by W3C standards, HTML adds very little interactivity, but it forms the base of most of the information displayed on the World Wide Web today.

GIF, PNG, JPEG are the W3C core standards for images. GIF and PNG have limited ability to add simple frame-by-frame animation to the image. Each of these formats is designed to compress images as much as possible (sometimes by sacrificing image quality) in order to make them easier to send from the server to the Web browser. These core standards are detailed in Appendix A.2 Image File Formats.

Cascading Style Sheets (CSS) are a W3C recommendation for specifying text and other layout parameters within an HTML document. A style sheet can give instructions to a Web browser and describe how every paragraph should be formatted, how every header should be styled, etc. Used correctly, they provide consistency and structure to a document (see 3.1.3 - Site Readability: Font Consistency).

CSS are similar to the style sheets employed in desktop publishing and word processing applications. Some word processing applications can translate a style sheet into a CSS formatted style sheet and embed them in the translated HTML document. HTML documents can also link to an external style sheet to provide consistent layout specifications to a series of documents. Of all of the core standards discussed here, CSS is the least consistent across all browser platforms but, if used correctly, it can speed up the process of converting documents from other electronic formats to HTML.

Web sites that use only the core standards are guaranteed to be displayed by the greatest majority of Web browsers without the use of extra software on the server or client. However, often the core standards become out-dated, or don’t cover certain applications, formats or techniques.

Other Formats

Outside of the W3C’s core standards, a number of vendor-specific technologies can be used to publish information on the Internet. The number of technologies makes discussing each greater than the scope of this document; however, there are some that are common enough that these can be discussed alongside the core standards. Adobe’s Portable Document Format (PDF) and Macromedia’s Flash format are common standards. All of the formats that fall outside of the core standards have advantages and can improve the viewer’s experience. Each also has a disadvantage, such as larger file sizes that take longer to download, special viewing software that needs to be installed by the user (see Browser Plug-in) or extra resources on the server. These and other disadvantages will need to be carefully considered before any format outside of the core is contemplated.

2.4 Converting Existing Projects to the Web

As was previously mentioned (see Section 2.2.1 - Design and Publish Cycle), HTML is not normally a language used to create documents. Most Web content is converted from a previous format, a technique often referred to as “repurposing”. The following section will provide some recommendations for converting existing documents to be published on the World Wide Web. This is not a detailed discussion (see Appendix B - Data Conversion), but a rather general set of recommendations.

2.4.1 Converting Word Processing Files to HTML

Most text documents are created with word processing software. Microsoft Word, WordPerfect and other dedicated word processing packages have made efforts to integrate HTML conversion into the workflow. Most of these applications can save documents in HTML format.

Since there is no standard computer screen size or resolution, modern Web browser software allows the users to set preferences for text display, text size and, to some extent, colors. Much of the time, Web designers will devote many hours in the editing phase of the process to try to achieve a similar layout from word processing to HTML. In some cases, it is not possible (or even practical) to attempt to duplicate the layout of document from a word processing application to the HTML publication.

2.4.2 Desktop Publishing Formats

Popular desktop publishing programs such as QuarkXPress, Adobe PageMaker or Microsoft Publisher perform functions similar to HTML. These applications take text and images from other applications, add formatting and layout instructions and “publish” the information. While many of these programs have made strides to convert their layouts to HTML, the process is more difficult. The more complex the layout task, the harder it is to translate into effective HTML which requires more editing to achieve similar results.

If possible, text should be created in word processing applications and all final edits should be done before the documents are published with HTML or a desktop publishing application. This will ensure that the content of both the HTML and printed publication is the same. Often, converting a document after it has been desktop published is more work and results in a less desirable final product.

2.4.3 Using PDF files

If keeping the layout, font size and other graphic design elements of a printed publication is essential, Adobe PDF can be used. PDF files are created with special software, but can be viewed on any operating system, in most browsers, with the use of a special plug-in, distributed free from Adobe® [6] (see Browser Plug-in).

PDF files have some advantages. In general, with the right software, creating PDF files is as easy as printing them, so the conversion cycle is short, and there is generally a shorter editing cycle. A PDF file contains all of the document’s original formatting instructions, including all of the font information, copies of the graphics, etc. PDF files can be hyperlinked from a normal HTML file, and they can contain hyperlinks to other HTML files or to other PDF files.

The format has some disadvantages, however. For example, the average size of a PDF file is much larger than a HTML file. PDF files also require special software to view and print the documents. While the software is free, not every user will want to take the time to visit Adobe’s Web site to download and install the free software. In addition, any time there is software to install; there is a risk that the user will not install it correctly. Regardless, the format is well supported, and the savings in editing and converting documents make it an attractive method for Web publishing.

2.4.4 Including Maps

Maps are often the most effective method for communicating transportation information. They are also one of the most difficult formats to convert and publish on a Web site. Maps tend to need fine detail and line work, which is often rendered illegible by the compression techniques used in the graphic file formats for Web publishing (see Appendix A.2 - Image File Formats).

A mapping tutorial for the Internet is beyond the scope of this document. However, some general tips are included.

Maps should be “simplified” for inclusion on a Web site. For instance, any unnecessary layers should be removed from a CAD file before converting it to a Web file. Background fills should be eliminated, if possible. There should be a good contrast in color and line weights, and the contrast should be exaggerated, if possible. The text should be at least 10 point at the final size of the map for publishing.

Often, it is best to display a map in a window by itself, free from other text and normal site navigation. If necessary, text links back to the originating page can be included. Users have different sized computer monitors and display images at different screen resolutions. To fit the majority of screens without forcing users to scroll the window, a map should be no more than 760 pixels wide and 420 pixels high.

Several file formats, outside of the core standards for graphics (GIF, JPEG, PNG) discussed earlier, can be used effectively. PDF files are often an excellent compromise between file size and readability, and, with the right software, are generally easy to produce. Several Geographic Information Systems (GIS) software packages will export maps in PDF format without the software from Adobe.

A variety of other types of software is also available to publish CAD and GIS files on the Internet, and there are several special browser plug-ins available to read CAD and GIS formats without converting them. If possible, whenever a file format that requires browser plug-ins is used, an alternative version of the map should also be made available in one of the core standards for graphics. Even if the quality of the alternative is poor, it is often better than nothing.

A Web site might have two distinct types of viewers: the general public consumer, and a consumer from another agency, the media or contractor. The second type of consumer is more likely to need a map with greater detail, and is therefore more likely to invest the time to download and install a plug-in to view a converted CAD or GIS file. CAD, PDF and GIS formats are not very compact. They will take more storage space on a Web site and use up more bandwidth to transfer the files.

2.5 Planning Web Publishing

The size of the Web doubles every eight months, and there are over 28 million Internet addresses registered [7]. Increasingly, agencies are taking advantage of the Internet as an inexpensive distribution channel. Documents are now being created in two versions: a hard copy, and a version for electronic publishing. This can translate to twice the amount of work, unless careful planning and thought go into every project or enterprise.

As the Web grows, groups are seeking to add a new Web presence or to enhance an existing Web presence. Without careful planning, these Web projects can quickly become difficult to manage and fall short of their goals.

2.5.1 Plan for a Web Project

The first step is usually to decide if a Web project is the right choice. Using the Web has several big advantages and some definite drawbacks.

The World Wide Web is an inexpensive distribution medium. The duplication costs of documents are obviously not a factor. There are cost savings in staff time to prepare the materials, and there are obvious savings in shipping, storing and recycling. Unlike printed material, Web documents can be changed, edited or updated without incurring additional cost.

The World Wide Web can increase the reach of information. Publishing on the Web instantly reaches a global audience. Properly indexed and cataloged Web documents are available to search engines on the entire Internet.

The Web can reduce the cost of marketing and advertising, or extend the reach of current marketing and advertising efforts.

The obvious drawback of the Web is the accessibility. Users must have a computer and an Internet connection to view the documents on the Web. Because of this serious limitation, the Web has not yet threatened to replace printed materials.

If a Web publishing project is the goal, the four basic questions identified above should be answered as early in the project as possible. The answers to those questions will help shape the work plan for a project or enterprise.

2.5.2 Set Goals for the Web Project

A Web project can have different goals than a print project. For instance, a Web project can be initiated to support a printed project or to announce the completion of a large project. Enterprises can support an agency, increase customer service and reduce the burden on staff. Web sites can also be a low-cost advertising medium, and increase the reach and availability of services.

Attainable goals for each Web project or enterprise are crucial. These goals will likely evolve and change as each goal is met. Success should be measured periodically (see Section 4.0 - Measuring Success) and the goals adjusted accordingly.

2.5.3 Decide on the Final Format for Products at the Onset

Many projects begin with a printed product as the final target outcome. Web products that are an afterthought or a secondary goal can lead to extra work in the conversion and editing phases of a Web project. Projects that are defined as Web projects from the onset can be approached in a manner that will avoid extra editing and conversion, and will result in a better end product.

2.5.4 Test Formats Early in the Design Cycle to Make Sure they will Work

Some types of documents, such as CAD drawings, complex graphics, etc., are difficult to convey over the Internet effectively. Trying a sample document conversion early in the project is recommended to avoid surprises in the final publishing phases, both for print and for Web publishing. Experimenting with alternatives to the printed format can help designers discover what the best digital version will be.

2.5.5 Devote Adequate Resources to the Update Cycle

Many Web enterprises fail to anticipate the staff resources necessary to maintain an existing Web site. Keeping the Web site up-to-date is critical to the success of the project or enterprise.

2.6 Future Trends in Web Publishing

XHTML

By far the most talked-about trend in electronic publishing is XML and the move away from HTML toward eXtensible HyperText Markup Language (XHTML). In fact, the W3C has announced that the current recommendation for HTML 4.01 will be the last HTML recommendation. It has submitted recommendations for XHTML 1.0.

XHTML is a more strict application of the Markup Language, based on XML (eXtensible Markup Language). The goal of XML is to present a way to store documents in a structure so that display information is kept separate from data. The advantage of storing data this way is that can be moved from application to application, from platform to platform with little or no effort.

In a standard HTML document (see Appendix A.1 - What is HTML?), the tags that markup the data often describe the method for displaying it. A paragraph of text also contains formatting instructions, making it difficult to separate layout tags from data. Therefore, it is difficult to convert the document to any other format besides HTML.

Redefining HTML as an XML subset will make the data easier to separate from the layout instructions. The goal is to store one document that can be displayed in a Web browser, a word processing application, a handheld computer, etc., without having to re-edit the document for each application.

E-Commerce

While not exactly a “future” trend, e-commerce is steadily gaining acceptance. Many city and county public works Web sites surveyed for this report already employed online payment transactions for functions like permits, property taxes, traffic fines, parking registrations, vehicle license renewals, and park and recreation user fees.

E-commerce is specialized enough that a third party specializing in the field should be consulted before any online payment systems are contemplated. At some point, most city and county Web sites will probably want to provide online transactions. If they are not a part of the Web site plan now, they should be considered in the near future.

SVG

Scalable Vector Graphics (SVG) Format is a draft recommendation of the W3C - meaning they are proposing to adopt it. It is a subset of XML developed to describe vector-based graphics on the World Wide Web. A variety of vector graphics formats are currently available. Examples include Adobe Illustrator, AutoCAD, MicroStation, various GIS implementations and a host of other drawing packages. Currently, vector-based graphics must be translated into a raster image format (such as GIF or JPEG) to be displayed in a web browser. SVG seeks to change that.

"… to produce a specification for an SVG format, written as a modular XML tagset and usable as an XML namespace, which can be widely implemented in browsers and authoring tools and which is suitable … as a replacement for many current uses of raster graphics."

"This will mean that the graphics in Web documents will be smaller, faster, more interactive, and be displayable on a wider range of device resolutions from small mobile devices through office computer monitors to high resolution printers." [8]

If the draft recommendation gains widespread acceptance, publishing maps, and other schematic drawings will become easier, and the end products will be better.

[1]Technically, Web pages are “parsed” by the client.

[2] American Standard Code for Information Interchange (ASCII) is a set of letters, characters, spaces, numbers and punctuation that is used in almost every present-day computer. More precisely, the HTML file formatted is an extension to the ASCII format called ISO-Latin1, or a newer international standard called Unicode.

[3] http://www.verisign.com, http://www.dotstar.com and http://domain.com are some examples.

[4] The World Wide Web Consortium is an international organization comprised of representatives from industry, research and educational institutions. The W3C has no international authority to enforce the standards they publish. Compliance is voluntary.

[5] Unfortunately, none of the browsers on the market today implement the W3C’s core standards completely. The standards are published internationally as recommendations. Each company that makes Web browser software chooses which of the recommendations their product will implement, and how. Some browser manufacturers implement standards of their own, which can later become W3C recommendations.

[6] See Adobe’s Web site (http://www.adobe.com) for more information.

[7] Measured by the number of documents published on the Web.

2.0 Standards and Best Practices