Chapter 10
Home Study Guide 2007 News Articles Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13

 

Advanced Web Page Design

1. Isn't HTML enough? Why do I need interactive Web components? 
2. Is Java a true universal computer language? 
3. What's the difference between Java and JavaScript? 
4. Do I really need to know how to program scripts and applets? 
5. What kinds of applets and scripts should I add to my Web pages?

Overview

This chapter's discussion takes us into the world of scripting and applets. As the limitations of HTML were quickly recognized by those who wanted to add dynamic components to their Web sites, the skills of computer programmers were called upon. Stripped down versions of complex computer languages were offered as solutions. Common gateway interface (CGI) scripts written in languages such as Perl appeared on a number of Web sites, allowing such functions as sending email, submitting forms, querying databases, counting page visitors, etc. In 1996, early efforts with Java and JavaScript began to blossom into mini-industries centered around creating portable OS-independent Java applets and plug-and-play JavaScripts to handle a number of the chores previously assigned to CGI. Whether Java will become the computer language of networked computers is still in question. Is "Write Once, Run Anywhere" really possible? Non-programmers can now easily add active components to their Web sites, but knowledge of the syntax of these languages helps in being able to change parameters and troubleshoot problems. Given the plethora of applets now available, Web designers can modify existing multimedia applications or create new ones when needed using WYSIWYG software. Efforts to share applets abound. For example, in the educational field, projects such as Educom's IMS initiative create a way for educational applet designers to share their efforts with other faculty and speed the process of developing an Internet environment suitable for cooperative distance learning. 

1. Isn't HTML enough? Why do I need interactive Web components?

One of the most common misconceptions about Web design is that once you've learned HTML, you can create state-of-the-art Web pages. While a fundamental knowledge of HTML is essential (or how to use a WYSIWYG HTML editor), HTML itself was not created to build dynamic Web sites. HTML was designed to permit authors to mark up text to include word processing features (bold, italic, etc.) to overcome ASCII text limitations, add hypertext links to other documents or within documents, and to embed graphics or other multimedia components. As HTML has progressed, additional features have been added to the mark-up language, allowing more precise placement of tables, more use of colors and other design elements, etc., but the language itself does not allow true interactivity. The initial goal was simple: to create a proto-language for displaying documents that could be accessed on all computers (UNIX, IBM PC clones, Macs) by using one tool, a Web browser. If this sounds a bit like the promises now made by Java to offer a universal operating system that will run on any computer platform, it is. The holy grail of networked computing remains the creation and adoption of an open standard that will allow all computer users to interact via the Internet, just like anyone with a telephone can call and talk to any other telephone user anywhere in the world.

An first ongoing attempt to add greater flexibility to HTML was the use of plug-ins. With plug-ins software designers can create in formats not supported by HTML. However, the process requires downloading and installing potentially dozens of plug-ins, all of which are periodically upgraded. Finally, most of these are various graphics, animation, and sound formats, intended to add multimedia support but not true interactivity.

To allow interactivity on Web pages requires the use of programming code (scripts). The generic name adopted for these scripts was Common Gateway Interface (CGI)

The Common Gateway Interface (CGI) is a standard for interfacing external applications with information servers, such as HTTP or Web servers. A plain HTML document that the Web daemon retrieves is static, which means it exists in a constant state: a text file that doesn't change. A CGI program, on the other hand, is executed in real-time, so that it can output dynamic information.

CGI scripts must be written in any language the server understands, and allows the addition of such functions as sending email, submitting forms, querying databases, accepting credit card information, counting page visitors, etc. One of the most frequently used languages for CGI is Perl. Perl was originally written by Larrry Wall for the purpose of extracting data from text files, thus the name Practical Extraction and Report Language (i.e. Perl).  Perl is a cross between the programming  languages C and Basic; it uses some of both methods.  Actually, a CGI program can be written in any number of outher programming languages, including :

  • C/C++
  • Fortran
  • Perl
  • TCL
  • Any Unix shell
  • Visual Basic
  • AppleScript

However, CGI scripts allow a user to directly access a server, creating potential security issues.

Since a CGI program is executable, it is basically the equivalent of letting the world run a program on your system, which isn't the safest thing to do. Therefore, there are some security precautions that need to be implemented when it comes to using CGI programs. Probably the one that will affect the typical Web user the most is the fact that CGI programs need to reside in a special directory, so that the Web server knows to execute the program rather than just display it to the browser. This directory is usually under direct control of the webmaster, prohibiting the average user from creating CGI programs.

An alternative to using CGI scripts seemed impossible in 1995. However, there were some thinking about whether it is was possible to download interactive programs or applets via the Internet that would then run interactively on the user's computer. Given that only those on networks did not have bandwidth problems, any solution of this type would have to be simple and not require long download times. Sun Microsystems stepped forward with a solution they named Java. At about the same time, Netscape was experimenting with adding support for a scripting language, JavaScript, that would operate inside its browsers without an additional request for data from the server. Microsoft had just discovered the Internet, but would soon offer yet another alternative called Active X (later DHTML). It is to discussion of these innovations and their strengths and weaknesses that we now turn.


How Far Can this Coffee Metaphor Go?

Additional Resources:

CGI - Common Gateway Interface (Yahoo)
http://www.yahoo.com/Computers_and_Internet/Internet/
World_Wide_Web/CGI___Common_Gateway_Interface/

Winfiles.com CGI Programming Tools
http://winfiles.cnet.com/apps/98/cgi.html

iHTML
http://www.ihtml.com/

Matt's Script Archive
http://www.worldwidemart.com/scripts/

Kristina's Scripts for Educators
http://www.linguistic-funland.com/scripts/

FreeCode - CGI Programming
http://www.freecode.com/cgiprog.html?au000en_andanavbar

The Perl Language Home Page
http://www.perl.com/perl/index.html

Developing Courses: Interactive Web Pages
http://www.fsu.edu/~crimdo/syllabus/203.html


2. Is Java a true universal computer language?

Before discussing the emergence of Java, a short aside on the history of computer operating languages is required. While C and C++ became dominant programming languages, software creators faced growing problems trying to design programs which would run on multiple platforms. By the late 1980s, the computer world was split into a number of camps. These included IBM clone PCs running DOS (later Windows), PCs build by Apple and Amiga running their own proprietary operating systems, workstations running various flavors of UNIX, and mainframes running a wide variety of operating systems but accessible to clients only by dummy terminals. In the 1990s, computer users would witness the emergence of a number of upgrades of Microsoft's GUI platform Windows, IBM's failed attempt to offer OS2 as an alternative to Windows, and continual upgrades of the Mac OS. While most of these platforms supported backwards compatibility, software developers struggled to keep up with all these changes.

The emergence of the Internet and HTML in the mid-1990s, offered the first real opportunity to reunite the computer world. However, HTML was never intended to be a software or development platform, only a document sharing mechanism. What Sun Microsystems envisioned when it created Java was a programming language that could be supported by a stripped down operating system capable of being run on any platform from inside a Web browser. Sun struck a deal with Netscape to include Java support in version 3.0 of its browser and worked on their own browser, Hot Java. Installation of either browser set up the environment to run Java applets on your computer. The basic Java operating system files reside on your computer; when you hit upon a page which contains a Java applet, the computer uses both the downloading files and the residing Java files to execute the program.

The major advantage in using Java to write programs is its support for object-oriented programming.

    Java is designed to be object oriented from the ground up. Object technology has finally found its way into the programming mainstream after a gestation period of thirty years. The needs of distributed, client-server based systems coincide with the encapsulated, message-passing paradigms of object-based software. To function within increasingly complex, network-based environments, programming systems must adopt object-oriented concepts. Java provides a clean and efficient object-based development environment.

Once an object has been designed it can be reused over and over again. This idea is now spelled out more fully in the use of JavaBeans to create complex reusable objects

The other stated advantages of Java are many:

  • Your programming language is object oriented, yet it's still dead simple.
  • Your development cycle is much faster because Java is interpreted. The compile-link-load-test-crash-debug cycle is obsolete--now you just compile and run.
  • Your applications are portable across multiple platforms. Write your applications once, and you never need to port them--they will run without modification on multiple operating systems and hardware architectures.
  • Your applications are robust because the Java run-time system manages memory for you.
  • Your interactive graphical applications have high performance because multiple concurrent threads of activity in your application are supported by the multithreading built into Java environment.
  • Your applications are adaptable to changing environments because you can dynamically download code modules from anywhere on the network.
  • Your end users can trust that your applications are secure, even though they're downloading code from all over the Internet; the Java run-time system has built-in protection against viruses and tampering.

Critics emerged rapidly. According to Jesse Berst, there are a number of myths about Java.

    Behind all this good news is an ugly fact the Java promoters don't want you to know. Many of Java's key promises are myths. Here are the five fables that could lead you astray.

    1. Write once, run everywhere. Java's key promise. Fact: It's not true today and it may never happen. Applets that run fine on Windows 95 may not run at all on the Mac (or vice versa). And may run so slowly on 16-bit Windows, they become unusable. I'm still hoping we'll end up with Java virtual machines that are consistent across platforms, but right now we're still just wandering around.
    2. Businesses will rewrite their applications in Java. Of course not. Fact: We still have production applications running today in Fortran and Cobol. People hate to throw stuff away. And why should they?
    3. People will do everything new in Java. Every language has its strengths. Fact: Java will never be optimized for everything. Visual Basic, C++ and other languages will continue to thrive.
    4. Java is secure. Java is more secure than Microsoft's ActiveX. It is also more restrictive. Using the standard Java "sandbox," you can't cache downloaded Java applets on your local machine, forcing you to download the same Java applets over and over again. Fact: As Java is modified to allow local caching, local storage, and local printing, it will become less secure.
    5. Java is an open standard. Yes, Sun Microsystems has turned Java over to a standards body. But on a glacially slow timetable and in a manner that keeps all the control with Sun. Fact: Java is less open than Microsoft's ActiveX.

There is much confusion about Java. CNET's 20 questions piece is very useful in attempting to clarify things. For Web designers who want to use Java to add interactive elements important questions include "What is an applet?" and "How Can I Make an Applet?"

To date Java has not had the major breakthrough it needs. Corel aborted its attempt to create a suite of Word Perfect software tools in Java. IBM and Lotus released eSuite, with the hope it would find a market in the emerging world of NCs. Software to create Web sites entirely in Java such as Net-It-Now are appearing. 

Additional Resources:

20 questions about Java
http://www.cnet.com/Content/Features/Techno/Java20/index.html?ibd

The Java Tutorial
http://www.javasoft.com:80/nav/read/Tutorial/index.html

Top Five Java Myths
http://www5.zdnet.com/anchordesk/story/story_799.html

Java: Information Sources
http://www.december.com/works/java/info.html

Java Programming Tools
http://winfiles.cnet.com/apps/98/java.html

TechTools: Java
http://www.webtools.com/toolbox/java

JavaBeans
http://java.sun.com/beans/

A Web developer's guide to JavaBeans
http://www.netscapeworld.com/netscapeworld/
nw-07-1997/nw-07-bytecode.html

Webmasters / Java User
http://www.zdnet.com/products/javauser.html

Net-It Software
http://www.net-it.com/


 

3. What's the difference between Java and JavaScript?

A number of misunderstandings have emerged over whether Java and JavaScript are the same thing. They are not:

Java, developed under the Sun Microsystems brand, is a full-fledged object-oriented programming language. It can be used to create standalone applications and a special type of mini application, called an applet. Applets are downloaded as separate files to your browser alongside an HTML document, and provide an infinite variety of added functionality to the Web site you are visiting. The displayed results of applets can appear to be embedded in an HTML page (e.g., the scrolling banner message that is so common on Java-enhanced sites), but the Java code arrives as a separate file.

JavaScript

It is important to understand that a Java-enabled browser is not automatically a JavaScript-enabled browser: the two technologies require entirely separate interpreters (licensed from separate companies) to handle the languages. It is unlikely, however, that future browsers will incorporate one but not the other. 

JavaScript

  1. JavaScript
  2. Status Bar Messages
  3. Retrieving user information
  4. Prompting For Information
  5. Opening New Windows
  6. Telling Time
  7. Changing Background Colors
  8. The Famous script for changing your web page depending on the time of day

Microsoft did not support JavaScript as quickly as Netscape. Microsoft, which had somehow missed the importance of the Net--perhaps because of its dominance in operating system software--moved first to develop a better browser, add interactivity to it, and finally to integrate their application software and operating system with the Web. Given that there were a large number of program designers already using Microsoft's flagship design product, Visual Basic, Microsoft would attempt to create a Web version of it and rename it Active X. Using Active X controls, programmers could create dynamic Web pages (but only viewable in Microsoft's Explorer browser). In 1998, Microsoft stopped calling their scripting language Active X and switched to DHTML. Rather than support open standards, Microsoft continued to create proprietary software. Such was also the case with Microsoft's use of Java, which it attempted to encase inside proprietary Microsoft code, ultimately resulting in a lawsuit with Sun Microsystems and a countersuit by Microsoft. Microsoft's attempt to integrate its Web browser with the Windows 95 desktop resulted in a US Justice Department probe of monopoly practices and a quick response from Microsoft. A two-year Justice Department civil trial resulted.

Yet another scripting alternative is Lingo script. However, Lingo script works only within Macromedia Director. To date Director has been one of the major multimedia creation formats, capable of running over the Web by using the Shockwave plug-in. While I would not have thought Shockwave had a long-term future on the Net a few months ago, the recent release of Macromedia's Flash (vector graphics format) and its incorporation into the latest version of Real Player have now positioned it strongly. 

Additional Resources:

Java vs. JavaScript
http://www.dannyg.com/javascript/javavsjavascript.html

Webmasters / JavaScript User
http://www.zdnet.com/products/javascriptuser.html

Scripting Tools
http://winfiles.cnet.com/apps/98/scripting.html

Danny Goodman's JavaScript Pages
http://www.dannyg.com/javascript/

JavaScript World
http://www.jsworld.com/

Netscape's JavaScript Authoring Guide
http://developer.netscape.com/docs/manuals/javascript.html

Thau's JavaScript Tutorial
http://www.hotwired.com/webmonkey/
98/03/index0a.html?collection=javascript

Microsoft Internet Developer
http://www.microsoft.com/mind/

Visual Basic
http://msdn.microsoft.com/vbasic/

Microsoft Visual InterDev
http://msdn.microsoft.com/vinterdev/

Dynamic HTML
http://www.hotwired.com/webmonkey/geektalk/97/39/index3a.html

ZD Net: Dynamic HTML
http://www.zdnet.com/devhead/filters/0,9429,2133215,00.html

Macromedia - Flash
http://www.macromedia.com/software/flash/

Macromedia - Authorware
http://www.macromedia.com/software/authorware/

 


 

4. Do I really need to know how to program scripts and applets?

Early HTML writers struggled to learn the required tags and add them to text documents by hand. The next generation used WYSIWYG design tools that kept code hidden from Web designers. However, knowing HTML allows the designer to more easily troubleshoot problems when the WYSIWYG tool fails (as Netscape Composer and FrontPage will).

The same pattern holds true for both Java and JavaScript. Early Java applet designers took the time to learn the language; many were programmers. JavaScript is much more basic than Java and can be learned by those with little programming background. In 1996, WYSIWYG Java tools such as Visual J++, Symantec Visual Café for Windows 95/NT, Bongo, and Jamba emerged. In 1997, Netscape released Visual JavaScript.

Repositories of existing Java applets and JavaScript archives now are commonplace. Some are freeware, other marketed as shareware. Non-programmers can now easily add active components to their Web sites, but knowledge of the syntax of these languages helps in being able to change parameters and troubleshoot problems. For example, once I downloaded the slideshow applet, I still had to figure out how to import my own graphics, set the transition effects, etc (see source code example below). As with all computer programming projects, try to find the most experienced person you can to assist you.

Sample Applet Code for Slideshow Applet

<applet align=center code="transit.class" width=368 height=246>
<param name=img value="images">
<param name=nimgs value="10">
<param name=transitionArray value="blind moveright pattern iris spiral blind moveright pattern iris spiral">
</applet>

Within this applet I can change the display box size, numbers of images to be displayed, and the pattern of transition effects. I can not alter other features of this applet as they are part of the compiled code and not available to me.

The segmentation of HTML writers from CGI script writers continued until around 1996, when script repositories started to appear. If you wanted to run a program on a certain UNIX server and you could find a script for it you did not need a programmer. In 1997, programs such as Microsoft's Frontpage 98, integrated Web design with server scripting for those running Windows NT Server and Internet Information Server. Without writing any scripts I created an on-line survey which dumped the results of a submittal to four places simultaneously: email message sent, update a Web page, new entry in Access database, and comma-delimited text file suitable for later database use.  

I Guess There Are More Coffee Names Left! 


Below are a number of Web sites offering scripts. These can be very useful if you need specialized features for your site.

Additional Resources:

Java Goodies JavaScript Repository
http://www.htmlgoodies.com/javagoodies/

JavaScript Archives
http://www.jsworld.com/scripts/

Cut-N-Paste JavaScript
http://www.infohiway.com/javascript/indexf.htm

JavaScript
http://tanega.com/java/java.html

JavaScripts.com
http://www.javascripts.com/

Nic's JavaScript Page
http://www.geocities.com/~jsmaster/


5. What kinds of applets and scripts should I add to my Web pages?

Obviously, such choices are up to the Web site designer and should be based upon identified needs to go beyond simple HTML pages. One way to approach this would be to use an organization or section as a focus group to help determine which materials need to be developed in an interactive format. For example, if a self-administered and automatically graded quiz would assist users in better identifying what information they're looking for, scripts can be written or borrowed to install it. Will a graphic, animation, or slideshow with audio be the best way to demonstrate an important aspect? If the latter, which of the many slideshow applets available is best suited for the information? 

Web sites can be set up using cookies that remember visitors, know what pages they have seen before, and suggest new areas to visit. Cookies, combined with Web server statistics tools, can collect all types of information about how folks are using your Web site. Using this information, Web sites can be redesigned so users easily locate the materials they want and they see the pages you want them to see. Visitors should be told the site uses cookies, in case they want to decline to participate.

Unfortunately, the original intent of the cookie has been subverted by some unscrupulous entities who have found a way to use this process to actually track your movements across the Web. They do this by surreptitiously planting their cookies and then retrieving them in such a way that allows them to build detailed profiles of your interests, spending habits, and lifestyle. On the surface, this practice may seem harmless and hardly worth fretting over since the worst thing most imagine is that corporate concerns will use this information to devise annoying, yet relatively innocuous advertising campaigns, targeted towards specific groups or individuals. However, it is rather scary to contemplate how such an intimate knowledge of our personal preferences and private activities might eventually be used to brand each of us as members of a particular group. But remember a site only knows what information you have entered. Not all cookies are bad, they can also provide useful functions on the web.

You can comparison shop for all types of Java applets at Sun's Gamelan site and other on-line Java repositories. As of 11/99, Gamelan contained over 1400 educational applets, nearly 1900 games, over 900 multimedia applications, plus thousands of others. 

Since there are distance learning and training efforts going on worldwide, there are bound to be a number of similar applets and modules being developed. But, how do you find them? The Educom IMS Project is intended to help faculty and teachers locate existing educational applets anywhere on the Internet using metadata tags. In fact, it may soon be possible to construct an entire course by picking from a number of educational learning modules. Similar to paying by the number of plates piled up on the table at the end of a Chinese dim sum meal, students would pay a technology or site license fee based on the total number of modules adopted within the course. Each module would have a small cost and materials authors would receive modest royalties if there materials were adopted by others. Publishers, software companies, and on-line information providers will also have on-line resources available for adoption. These may include access to databases, on-line educational simulations, testing environments, etc. Having just returned from an academic conference in which I was approached by a number of faculty who have been asked to get their courses onto the Web while offered minimal support, a shared environment for cooperative distance learning and training is a much needed aid. 

Additional Resources:

Cookie Central
http://www.cookiecentral.com/

Using Cookies to Analyze User Activity and Create Custom Pages
http://www.netscapeworld.com/
nw-02-1997/nw-02-cookiehowto.ibd.html

Government Speaks out on Cookies
http://www.cookiecentral.com/creport.htm

Web Server Statistics Tools
http://winfiles.cnet.com/apps/98/servers-webstat.html

Gamelan
http://www.gamelan.com/

JARS.COM
http://www.jars.com/

STATLETS - Java Applets for Statistical Analysis and Graphics
http://www.statlets.com/

BotSpot
http://botspot.com/


The example below demonstrates what can be done using advanced Web design techniques. Pennsylvania used XML to create a way for users to access a number criminal justice agency databases simultaneously from the same Web browser window. The system, known as JNET, allows authorized users to access law enforcement, court, and correctional agency databases to track individual offenders; and has sealed a number of cracks that offenders used to slip through.

What is JNET?

The goal of the Pennsylvania Justice Network (JNET) is to enhance public safety by providing a common on-line environment whereby authorized state, county, and local officials can access offender records and other criminal justice information from participating agencies. The JNET System is also expected to promote cost-effectiveness and reduce redundancy and errors by making it possible, where appropriate, to enter new offender information only once as subjects proceed through the criminal justice process.

Using open Internet/World Wide Web technologies and standards, the JNET System links information from diverse hardware/software platforms under a common, web-browser interface. Each participating agency controls what information it shares and who is authorized to see it. Network firewalls, secure communication protocols, data encryption, and authentication based on digital signatures and certificates protect information on the JNET System from unauthorized access.

 

Pennsylvania Justice Network Infrastructure

 

In addition, the JNET System serves as a platform for broad-based knowledge-sharing among Justice Network users. Encrypted, authenticated electronic mail provides a secure channel for inter-agency messaging. JNET servers support searchable on-line reference libraries and threaded discussion groups, as well as non-public web sites specifically for criminal justice business.

Who is participating?

Overall policy and strategic vision for the JNET Project is established by the JNET Executive Council, which comprises chief executives from the 15 JNET Governing Agencies

JNET Governing Agencies
-  Administrative Office of Pennsylvania Courts (AOPC)
-

Board of Pardons (BOP)

-

Department of Corrections (DOC)

-

Department of Public Welfare (DPW)

-

Juvenile Court Judges' Commission (JCJC)

-

Office of Attorney General (OAG)

-

Pennsylvania Board of Probation and Parole (PBPP)

-

Pennsylvania Commission on Crime and Delinquency (PCCD)

-

Pennsylvania Department of Transportation (PennDOT)

-

Pennsylvania State Police (PSP)

The JNET Steering Committee, also made up of representatives from the 15 Governing Agencies, is responsible for tactical planning for the deployment of JNET Project functionality and associated information-sharing requirements (JNET Governance Structure Details).

Ten of the governing agencies—AOPC, BOP, DOC, DPW, JCJC, OAG, PBPP, PCCD, PennDOT, and PSP—are the initial providers and users of content for the JNET System. Other state, county, and local organizations are being encouraged to join as the capacity of the JNET System grows. Because the criminal justice process begins and ends in our communities, county and local authorities ultimately must become the foundation, as well as beneficiaries, of the Pennsylvania Justice Network.

JNET offers an array of connectivity and information-sharing options for easy entry at various levels of participation:

  • The JNET System supports network connections via the Commonwealth Metropolitan Area Network (MAN), county and municipal networks, and telecommunication lines.
  • Agencies that wish to contribute information to the JNET System are able to selectively "publish" data by exporting it to a standardized repository on a JNET Agency Server. This option has no impact on existing legacy systems.
  • Some agencies do not require an intermediate JNET data repository. Depending on the configuration of its legacy systems, an agency may be able to share information through a JNET query gateway.
  • Agencies re-engineering their information systems, or building new ones, may choose to develop a solution around JNET architectural specifications. This approach will yield an agency system that is capable of full integration with JNET, but remains completely under the agency's control.
  • For information that is extremely sensitive or rarely needed by other organizations, an agency can share that data electronically using encrypted, authenticated e-mail over JNET.

How is the system being implemented?

The JNET project is currently in the Phase II of a multi-phase development plan that spans several years:

JNET Lab

The JNET Laboratory, located at Pennsylvania State Police Department Headquarters in Harrisburg, prototyped initial JNET content and applications in preparation for Phase I, and now serves as a center for on-going development.

Phase I

The first phase of the JNET project focused on the infrastructure and application framework needed to interconnect the ten Commonwealth agencies that supplied the initial JNET information content. In this phase, more than 100 trial users were given access to proof-of-concept data-sharing applications, HTML (“web”) sites, and inter-agency communications.

 

JNET Phase 1 Data Sharing

 

Phase II

The second phase is extending JNET to provide more information and new functionality, including case-file transfer, digital mug shots, PennDOT photo images and driver license information, live posting of court dispositions to the PSP Criminal History Repository, and enhancements to existing Phase I applications. More organizations and users are being connected as directed by the JNET Steering Committee.

Phase III and beyond

Subsequent to Phase II, continuing development will explore adding new capabilities and connecting additional users from qualified state, county, and local organizations.

Additional Resources:

McDonough, Brian. 1999. Sealing the Cracks. Government Technology. December, pp. 122-123.

Caterinicchia, Dan. 2000. Maryland Cuts Red Tape from Justice Spending. Civic.com. January. pp. 16-18.

 

01/29/2007 01:37:47 PM