Hvordan ser frem-  tiden ud for det andet internet!
Man er ved at have fundet en løsning på antallet af internetadresser, fordi der udvides med nye domænenavne som .nation; .tele; .ditten og datten.

W3 org
Ministeriet for Videnskab, teknologi og udvikling

Sample XML document This is the sample XML document that we will use for this exercise: FileCab This chapter describes the commands that manage the FileCabinet application. Note that the first element, , surrounds the entire document. Therefore, it is the document element of this document instance. It is also the child of a root node that is defined to always be the top node of any parsed XML document. Concept: Source document viewed as a tree This is how the source XML document may be represented after it has been parsed, as the first stage in XSL processing. For another way of viewing the parsed source tree for this document, see the definition for walking a tree

The Voice XML document shown in Listing 1 has one form that prompts the user to choose a beverage from three developer favorites. The prompt can be presented through a prerecorded audio file or it can be generated via text-to-speech. Voice XML does not specify audio file formats. The element points to a grammar file in which the possible answers are defined. In this case, the grammar uses the Java Speech Grammar Format (JSGF). A conforming Voice XML grammar will specify a set of utterances that a user may speak to perform an action or supply information. It will then provide a corresponding string value (in the case of a field grammar) or set of attribute-value pairs (in the case of a form grammar) to describe the information or action. The application will repeat the prompt until the user responds. Input can come from speech recognition, touch-tone characters, or recordings. Production Voice XML applications will take advantage of exception handling and default behaviors to be more user friendly in these cases. For example, a link element could be used to jump to a live operator whenever the user resorts to saying "help" or "operator." If the user chooses one of the three recognized answers, the field exits and the flow of the document lead to the block element where the form input is submitted to an Active Server Page called “orderbeverage.asp.” Because the Voice XML gateway (called the interpreter context) is directing content requests to a plain old Web server, a Voice XML document can request static content or dynamic content via Active Server Pages, Java Server Pages, CGI scripts, or any other server-side application service. More sophisticated Voice XML applications are created using elements and client-side scripting. Subdialogs are subroutines that allow the reuse of common chunks of Voice XML code, such as those that prompt for passwords and credit card information. Subdialogs use ECMAScript-style objects to return results. (ECMAScript is the standardized version of JavaScript.) Motorola and IBM are taking active roles in building Voice XML tools for developers. IBM alphaWorks has a Voice XML SDK (see Resources) that includes a beta version voice browser, the ViaVoice runtime engines for speech recognition, text-to-speech and other services, and good documentation and samples. IBM’s Voice XML SDK requires the IBM Java Runtime Environment Version 1.2.2. Motorola’s Mobile Application Development Kit is an integrated development and simulation tool. The Mobile ADK supports both WML and Voice XML application development. I encourage you to check out Voice XML. It’s wise to know all of your options for distributing content to all of your users -- the Web is not just visual anymore. Jeff Jurvis is a principal consultant in the n-tier and information appliances practices of Rainier Technology, Inc., a software and infrastructure solutions provider in Minneapolis, MN. You can contact him at jeff.jurvis@rainier.com.

Kontakt mig, hvis I har vigtige nyheder.
Email: ValdemarThomsen@yahoo.com
By mail: Valdemar Thomsen, Livjægergade 26,4th DK-2100 København Ø.
Telefon nr.+45 35425367/35269498
Se min anden Website i angelfire.

Et sikkert internet - hvordan det?
Herunder vil der være en liste over de seneste nyeder som vedrører et sikkert internet. mere herom i December måned.

Future XML use! Voice-activated Web access A new flavor of XML redefines mobile communication Jeff Jurvis Principal consultant, Rainier Technology, Inc. September 2000 Contents: Voice XML Say what? Resources About the author There’s more than one way to connect to the Internet on a mobile phone. WAP and WML are among the more common technologies used in North America. Now a new XML schema is providing another way for users to link up to the Web over their mobile phones. People are talking about extending the Web to mobile phones, and most of the talk is about transplanting something like the traditional Web browser into the phone’s smaller footprint. The Wireless Application Protocol (WAP) (see Resources) and its Wireless Markup Language (WML) are -- along with WML’s antecedent: Handheld Device Markup Language (HDML) -- the most common technologies used to extend the Web to mobile phones in North America. WAP is nearly ubiquitous in Europe, and iMode (with Compact HTML) is huge in Japan. Each approach delivers text and limited graphics to a small phone display. But we tend to overlook another channel for providing Web content over the phone: the phone’s microphone and speaker. Voice XML Voice XML is a new XML schema intended to standardize the delivery of audio dialogs for voice access and interactive voice response linked to Web-based content and applications. IBM, Motorola, Lucent, and AT&T founded the Voice XML Forum (see Resources) in early 1999 to leverage existing speech technologies to make the Internet accessible by voice and phone. Not only do speech technologies open the Web to those unable to use visual browsers due to circumstance or physical limitations, they also make Web access more convenient for all users. New speech technologies can create dialog-driven applications such as speech recognition, speech synthesis, and recording and playback of digitized speech on PCs and servers for distribution to client devices. Voice XML provides a technology-neutral language that can be used to deliver speech applications. These applications separate the front-end presentation layer in Voice XML from the back-end services that handle speech and the mechanics of processing. For example, a well-designed Web site could easily support a voice-driven browser (such as one you might use on a mobile phone) in the same way the site would support another browser (such as a WAP browser or an HTML browser). When the initial request comes in from the browser, the server sniffs the browser type. If the browser is identified as a voice browser, the server will return the appropriate Voice XML pages. Say what? Knowing the basics of XML isn’t the only hurdle to understanding Voice XML. Its speech-oriented vocabulary and nonstandard architecture are unlike other XML schemas that hold close to the syntax and flow of HTML (such as the WML). A Voice XML document implements dialogs that connect in a finite state machine. The user enters into a conversation with the application at the first node of the finite state machine. Each node is a dialog that determines -- via voice or touch-tone interaction with the user -- which dialog to transition to next. The application exits implicitly when a dialog does not specify a successor, or explicitly when an invoked element causes an exit. Specifically, the primary top-level elements that make up a Voice XML document are the dialog elements form and menu. Forms present information and gather input. Menus offer choices of what to do next. Other top-level elements are used to define things like meta tags, variables, and scripts. Forms are at the heart of Voice XML, where conversations mainly take place. Inside forms are field and control items. Field items collect input and control items prompt the user and perform computations. Listing 1: A Voice XML document Would you like Dr Pepper, Mountain Dew, or Jolt? <;/form>