Click on image to enlarge.
|
Code Notes for XML/XSLT [Secure eReader (recommended)/Mobipocket/Microsoft Reader/Adobe]
eBook by Gregory Brill
| |
Regular |
|
 |
|
Club |
| You Pay: |
$19.95 |
|
|
|
$16.96 |
| Micropay Rebate: |
10% |
|
|
|
10% |
| Cost After Rebate: |
$17.95 |
|
|
|
$15.26 |
| You Save: |
10.03% |
|
|
|
23.51% |
eBook Category: Technology/Science/General Nonfiction
eBook Description:  CodeNotes provides the most succinct, accurate, and speedy way for a developer to ramp up on a new technology or language. Unlike other programming books, CodeNotes drills down to the core aspects of a technology, focusing on the key elements needed in order to understand it quickly and implement it immediately. It is a unique resource for developers, filling the gap between comprehensive manuals and pocket references. CodeNotes for XML is a practical handbook for Java and Visual Basic developers interested in working with XML. You will learn how to leverage both CSS and XSLT to produce rich, compelling output, as well as manipulate XML using the DOM and SAX APIs. The new XML Schema specification is also covered in-depth. CodeNotes for XML is your guide to these powerful technologies, presented within the context of the distributed application, database, or web-based world you already know. This edition of CodeNotes includes: A global overview of a technology and explanation of what problems it can be used to solve; Real-world examples; "How and Why" and "Bugs and Caveats" sections that provide hints, tricks, workarounds, and tips on what should be taken advantage of or avoided; Instructions and classroom-style tutorials throughout from expert trainers and software developers. Every CodeNotes title is written and reviewed by a team of commercial software developers and technology experts. See "About the Authors" for more information.
eBook Publisher: Random House, Inc., Published: 2002
Fictionwise Release Date: June 2002
Available eBook Formats [Secure eReader (recommended)/Mobipocket/Microsoft Reader/Adobe - What's this?]: SECURE MOBIPOCKET FORMAT [791 KB], SECURE MICROSOFT READER FORMAT [544 KB] - Requires Microsoft Reader 2.1.1 for PCs, or Microsoft Reader 2.2.2 on Pocket PC 2002 handheld devices. Some older Pocket PCs can be upgraded. Learn More., SECURE EREADER (RECOMMENDED) FORMAT [464 KB], SECURE ADOBE READER 7 FORMAT [1.2 MB]
Words: 125000
Reading time: 357-500 min.
Secure Adobe: Printing enabled, Read-aloud DISABLED
Other formats: Printing DISABLED, Read-aloud DISABLED
Microsoft Reader ISBN, Adobe Acrobat Reader ISBN, MobiPocket Reader ISBN, eReader (recommended) ISBN: 9780679647287
 
Chapter 1
INTRODUCTION
ORIENTATION
What Is XML?
Extensible Markup Language (XML) is a globally accepted,
vendor-independent standard for representing structured, text-based
data. An XML document is a perfect medium in which to encapsulate any
kind of information that can be arranged or structured in some way. For
example, an XML document can contain a list of personal or business
contacts, books in a library's card catalogue, or products in a
warehouse.
If we looked at any one of these examples--say, the library card
catalogue--in the more traditional "table-oriented." view with which
most developers would be familiar, we would see something like the
following:
Table 1.1 A card catalog in a flat table format
An XML document, on the other hand, would present this information
hierarchically, where the column names would become tags or possibly
"attributes." For example:
0812589041
science fiction
Orson
Scott
Card
Enders Game
1985
0883853280
biography
William
Dunham
Euler The Master of Us All
1999
Listing 1.1 The card catalog as XML
Listing 1.1 is included to give you a first look at XML, which can be
overwhelming compared to a familiar table structure. However, as you
become more familiar with XML, you will see that this structure has many
important advantages over a traditional table.
XML and HTML
It can help to think of XML at its most basic level as being very
similar to a HyperText Markup Language (HTML) web page. However, the
tags in an XML document do not have a fixed meaning the way they do in
HTML (e.g., , , etc.) When a developer writes an XML
document, he or she decides on the names of the elements (e.g., book,
title, year, and author) and the data the elements will contain (e.g.,
the tags contain the year the book was published). The developer
chooses his elements with the expectation that some client application
exists that will read the XML file and be written to process those
particular elements in some way. Referring back to Listing 1.
|
)
