The Extensible Markup Language (XML) is an open, general-purpose specification for creating markup languages. Its primary purpose is to help information systems share structured data, particularly via the Internet, and it is used both to encode documents and to serialize data. It is used in a wide variety of technical communication document formats, including Microsoft Word, OpenOffice, XHTML, DITA, DocBook, and RSS, among others.
By taking advantage of open source products, and by stretching the definition of location, we were able to program xml and SVG tools to perform many of the functions of a standard geographic information system (GIS). Additionally, we were able to develop prototypes of document management, content management and knowledge visualization tools that are not easily available through standard GIS tools.
If you're a Java 2 Enterprise Edition (J2EE) developer, you'll want to preview the SQLXML technology, currently in development. Check out procedures to create an XML document, store an XML document in a relational database, retrieve an XML document from a database, and navigate an XML document with the SQLXML Java data type.
Topic Maps provide a very flexible and robust way to add arbitrary data to a relational databases at runtime. Moreover, Topic Maps come with a predefined exchange mechanism (the XML Topic Maps (XTM) interchange syntax) to allow data to be exported to XML.
XML is not just a pretty face, living in isolation from the rest of the computing world. XML is more than a rulebook for generating custom markup languages. It is part of a family of technologies, which, working together, make your XML-based documents very useful indeed.
In one of my past articles, A Pattern/Framework for Client/Server Programming in Java, I discussed a pattern for client/server development using java. That article does not answer exactly how the two parties, client and server, communicate with each other. We require an application-level protocol to do the talking between two entities. It sets up rules about how the two applications/entities communicate and understand each other over a network. If you happen to know the TCP/IP networking model or the OSI networking model, you will observe that network-based communication is implemented in layers, with the application layer at the top and the physical layer at the bottom. This article discusses issues you must face when implementing an application-level protocol and how XML proves to be an excellent choice to represent and implement the application-level protocol.
Today, we can find many applications to manage XML content that demonstrate the power and flexibility that can only be achieved through XML-native databases. Information intensive companies such as the airline and manufacturer described in this paper have achieved significant technical and business benefits from their use of XML standards and database technology over alternative approaches.
In this article, we look at the problem of Web publication, a process which concerns all enterprises having to send and receive information. What makes XML the technical solution to content syndication? How can the XML/XSL couple facilitate multi-channel publication? We will illustrate this last point using an example near and dear to our hearts, the publication of TrendMarkers e-newsletter.
In addition to the powerful features available now, the upcoming XSL-FO 1.1 will bring several new features. In the world of business-type documents, marketing material and forms, there is currently a need for end-of-page subtotals, multiple flows, easier page number citation, things that will be possible with XSL-FO 1.1. This presentation will cover the features of XSL-FO that are needed for this type of documents. Formatting objects and properties of both XSL-FO 1.0 as 1.1 will be covered, as well as how to combine these things to create a good-looking business-type document, because these types of documents need have the perfect layout.
This paper will explain how XSL-FO, XSLT, XForms and UBL can be used together (and how the implementation in Scriptura XBOS is done). Each technology contributes its own strengts to the total solution. XSL-FO for page oriented layout with a visual fidelity, XForms for advanced and flexible forms, and UBL to represent the business data. Together they allow to create UBL documents such as invoices in a very powerful and flexible way, all with open standards.
Introduces XM (XSLT Make), a simple and affordable Web publishing content-management solution that takes advantage of XML and XSLT. Code samples show the development of a wrapper for the XSLT to make it easy for a nonprogrammer to use. XM project code is available by link.
With XSLT support fast becoming a commonly available component in the browser, web developers can now leverage transformations to manipulate large amounts of data in the browser at speeds acceptable for more advanced user interfaces. Once Safari gets its act together, I see more and more UI-specific data processing being moved off of the server into the browser. This article outlines the process involved in transforming the del.icio.us user API XML document into an HTML fragment.
Macromedia Dreamweaver 8 supports two workflows when authoring with XML: client-side authoring with complete XSLT template pages and server-side with XSLT fragments. The client-side option is available from the Start page.
Introduces readers to Voice Extensible Markup Language (VXML), a markup language that allows vocal interaction between users and applications via a telephone-based communication system. The author also discusses World Wide Web Consortium specifications for VXML.
It may already be the de facto voice platform for the Internet, but this week the Voice XML 2.0 specification has moved closer to becoming an official World Wide Web Consortium (W3C) standard. The W3C, the body responsible for maintainin many of the core standards and protocols at the heart of the Internet, has publishe the new Voice XML 2.0 specification as a Proposed Recommendation
Gerald McCobb continues his introduction to the forthcoming W3C Multimodal Architecture with a survey of the many XML languages that you can use to author multimodal applications. He then shows how several specifications -- SCXML, XHTML, REX, and XML Events -- could work together in a complete multimodal application.
The internet did not replace television, which did not replace cinema, which did not replace books. E-books aren’t going to replace books either. E-books are books, merely with a different form. The electronic book is the latest example of how HTML continues to win out over competing, often nonstandardized, formats. E-books aren’t websites, but E-books are distributed electronically. Now the dominant E-book format is XHTML.
Business integration is at the heart of many of today's industry trends. As businesses consolidate infrastructure, and look at rolling out service-oriented architectures, they are finding they need to link previously isolated applications. It's not easy. You can't link applications without some form of middleware, an extra application layer that lets their various systems communicate. Whether you use web services, or a message-based solution, there's one key feature that's at the heart of modern integration technologies: XML.
DocBook is a set of tools for implementing XML (Extended Markup Language)-based structured documentation. It is developed back in 1991 and is widely used today by those technical writers who generate single-sourced documentation. It is especially well suited for software, hardware and networking documentation.
RSS, also known as rich site summary or real simply syndication, arrived on the scene a number of years ago, but was only recently embraced by webmasters as a means to effectively syndicate content. RSS Feeds provide webmasters and content providers an avenue to provide concise summaries to prospective readers. Thousands of commercial web sites and blogs now publish content summaries in an RSS feed. Each item in the feed typically contains a headline; article summary and link back to the online article.
Compares Gutenberg's invention of the movable type to the creation of XML. But where movable type changed the “economics of a mechanical process,” XML changed the “economics of content authoring, formatting, and customization.”