New User!
XML for Data Architects
By: James BeanImprint: Morgan Kaufmann
Format: Adobe Encrypted (DRM)
Earn $0.50 - Write a Review »
"The book addresses a sorely missing set of considerations in the real world... This is a very timely book."
-Peter Herzum, author of Business Component Factory and CEO of Herzum Software
XML is a tremendous enabler for platform agnostic data and metadata exchanges. However, there are no clear processes and techniques specifically focused on the engineering of XML structures to support reuse and integration simplicity, which are of particular importance in the age of application integration and Web services. This book describes the challenges of using XML in a manner that promotes simplification of integration, and a high degree of schema reuse. It also describes the syntactical capabilities of XML and XML Schemas, and the similarities (and in some cases limitations) of XML DTDs. This book presents combinations of architectural and design approaches to using XML as well as numerous syntactical and working examples.
* Designed to be read three different ways: skim the margin notes for quick information, or use tables in the appendix to locate sections relevant the to a particular issue, or read cover-to-cover for the in-depth treatment.
* Contains numerous tables that describe datatypes supported by the most common DBMSs and map to XML Schema supported data types.
* Unique focus on the value added role and processes of the data architect as they apply to enterprise use of XML.
See more like this in our Computers eBooks section
Share your thoughts on the XML for Data Architects Computers eBook with others!
| Title of Computers eBook: XML for Data Architects | |
| Release Date: 06-19-2003 | |
| Publisher: Morgan Kaufmann |
This eBook download is available in the following formats:
| Parent title | XML for Data Architects |
|---|---|
| Encrypted (DRM) | Yes |
| SKU | 9780080521435 |
| File size | 15289 |
| Security | n/a |
| Printing | Not allowed |
| Copying | Not allowed |
| Read aloud | No Sys requirements Download reader |
| Devices | Samsung Tablet, Apple Ipad & Iphone, Barnes & Noble Nook, Kobo eReader, Aluratek Libre, Iliad, Nokia, Blackberry, Hanlin |
| Note | Excellent navigation features are available via Adobe such as bookmarks and a quick access table of contents. Text search is easily accessible. An Adobe DRM-protected file is different than a pdf file in that it uses Adobe DRM (Digital Rights Management) technology, which authors and publishers use to protect their content from illegal online distribution and to set certain privileges such as restrictions on copying and printing. |
XML for Data Architects
Chapter One
Motivation and Rationale for Using XML
Before embarking upon the journey to learn why eXtensible Markup Language (XML) is important or when it should be used in a technology application, you have to have some idea about how it came to be. XML has evolved to become a "conforming subset" of Standard Generalized Markup Language (SGML). SGML has been in use for a number of years to describe and constrain the content of primarily text-oriented documents and files. Common examples of text-oriented content are the pages of a book, letters, notes, brochures, and presentations. As would be expected, the contents of these documents are strings of characters and words that are generally assembled to present a context (most often as collections of phrases, sentences, paragraphs, sections, and chapters). With this type of loosely structured information, rarely is there a need to describe granular pieces of information such as individual words or even more specific characteristics such as data types. SGML applications of this type include the use of descriptive tags to delineate sections of contained text and to describe text and document characteristics. Although the value of SGML for describing document-oriented data is undisputed, its application to other business and technology paradigms such as global e-commerce and enterprise data exchanges presents a few problems. First, SGML is implemented by a complex syntax that for many can be difficult to learn and apply. Also, there is a obvious lack of support for strongly typed data (e.g., data architects will recognize "strongly typed data" as the "data types" of a data element, column, field,
...








