James Keogh (1) (1948–)

PDFKE | DOI: 10.1036/0072262109 | XML Demystified shows you how to define your own set of markup tags using XML and how to use electronic tools to make an XML document a working part of your business. By the end of this book, you’ll be able to make your classy markup tags that will leave even the sophisticated business manager in awe—and the IT department left scratching their heads, asking: How did he do that? |

Contents

Chapter 1: XML: An Inside Look
No doubt you heard a lot about XML since many in the business community see XML as a revolutionary way to store, retrieve, and exchange information within a firm and among business partners. The first chapter provides you with an overview of XML before learning the nuts and bolts of applying XML to solve a real business problem.

Chapter 2: Creating an XML Document
Now that you have an understanding of what XML is and how it works, it is time to learn how to apply your knowledge and design your own set of XML markup tags. Chapter 2 shows you step-by-step how to create a set of XML markup tags by finding natural relationships among pieces of information in your document.

Chapter 3: Document Type Definitions
Markup tags used in an XML document conforming to a standard set of markup tags that are adopted by a company or an industry. An XML standard is defined in a document type definition that specifies markup tags that can be used in the XML document and specifies the parent-child structure of those tags. Chapter 3 takes an in-depth look at how to develop your document-type definition.

Chapter 4: XML Schema
A parser is software used to extract data from an XML document. However, before doing so, the parser must learn about the XML tags used to describe data in the document by using an XML schema. In this chapter, you’ll learn how to create an XML schema for your XML document.

Chapter 5: XLink, XPath, XPointer Real-world XML documents can become complex and difficult to navigate, especially if the document references multiple external resources such as other documents and images. Professional XML developers use XML’s version of global position satellites to find elements within the XML document by using XLink, XPath, and XPointer. Sound confusing? Well, it won’t be by the time you finish this chapter.

Chapter 6: XSLT
A common problem facing anyone who works with data is that data is usually stored in different formats. For example, some systems store a date as 1/1/09 while others store it as 01 Jan 09. However, much of this problem can be resolved by using XML because data in an XML document can be easily converted into any format by using a stylesheet. A stylesheet is a road map that shows how to convert the XML document into another format. In this chapter, you’ll learn how to create a stylesheet and how to use an XSLT processor to transform an XML document into an entirely different format.

Chapter 7: XML Parsers and Transformations The powerhouse that makes an XML document come alive is the parser. A parser can transform a bunch of characters in an XML document into anything you can imagine. There are many parsers that you can choose from. This chapter provides you with insight into each standard, enabling you to make an intelligence choice when selecting a parser to transform your XML documents.

Chapter 8: Really Simple Syndication (RSS)
If you ever wished there was a way to distribute your web content to the millions of web sites on the Internet, then you’ll enjoy reading this chapter. RSS is an application of XML that is used to register your content with companies called aggregators. Aggregators are like a chain of supermarkets for web site content. In this chapter, you’ll how to create an RSS document that contains all the information an aggregator requires to offer your content to other web site operators.

Chapter 9: XQuery
Think of XQuery as your electronic assistant who knows where to find any information in an XML document as fast as your computer will allow. Your job is to use the proper expression to request the information. In this chapter, you’ll harness the power of XQuery by learning how to write expressions that enable you to tap into the vast treasure trove of information stored in an XML document.

Chapter 10: MSXML

MSXML is an application program interface (API) that enables you to unleash an XML document from within a program written with such programming languages as JavaScript, Visual Basic, and C++ by using Microsoft’s XML Core Services, simply referred to as MSXML. Any XML document can easily be integrated into your application by calling features of MSXML from within your program. You’ll learn about MSXML in this chapter and how to access an XML document using JavaScript. The same basic principle used for JavaScript can be applied to other programming languages. |

NO REFERENCE PAGE |

SA - https://www.librarything.com/work/13996188/book/254691083 | https://www.librarything.com/work/31877166/book/260244162 | https://www.librarything.com/work/31852297/book/259981696
RT - Interoperability
BT - Markup Language
NT - HTML
UF - XML is used to send requests and receive replies. It’s the best choice for exchanging data because it works with every operating system and programming language. XML is a markup language similar to HTML except that it enables you to create your own tag set.
SN - This is a textbook but with an informal tone. - it is not academic. (This entry does not reference a hierarchical list)… (mer)

A very disappointing book but for an even more disappointing reason - it had GREAT potential. I rate it so poorly because I have no choice. This guy obviously had NO EDITOR. There are so many inaccuracies in this book that it will make your head swim. All of the sample code is in VB.NET, except one example which is inexplicably in C# (with no notification of such). It seems that every 5 or so pages has a typo or a mistake in the code. It will say that the code does one thing but it doesn't. I mean, it's close but not quite correct. For example, one example is of how to do a basic loop. It says that the user enters the starting point and the loop is set to exit when the counter counts up from the user's starting point to the number 10. When the counter reaches 10, it will exit the loop and display the counter as a result. So what do you think it would display? 10 of course. He says, it will display the user's original entry PLUS 10. WRONG. Again, close, but WRONG.

I give the book 2* for one simple reason. It had GREAT potential. His writing style is perfect for a begining developer. The content is presented in a clear and logical flow to get you from "Hello World!" to binding controls with data from a database. It really is extremely well structured for that target reader. Unfortunately, the lack of proper editing makes it completely useless to the beginner because they would be confused the first time the code doesn't give the results that are expected.

How do I know all of this? How did I catch these errors? I'm an ASP classic developer who is no longer a full-time developer. I'm just now moving to get my arms around .NET. So 90% of what he was saying, I knew. I've even done a couple of sites in ASP.NET but I had to feel my way around in the dark as I built them. In short, the book was below my skill level due to my past experience. I read the book for two reasons: 1. to give myself a good foundation/"ground up" knowledge base upon which to build my future .NET experience and 2. because I'm looking for a beginner level book to get one of my IT staff up to speed as an entry-level ASP.NET developer. I'll still give him the book because as I read the text, I corrected every error I found. He'll be fine with it now.

Let's just say that there are way too many of my marks in that book - that are NOT marks in a good way (as in...I learned something, make a note!). Too bad this one was so shoddy that it likely won't get a second edition that's been cleaned up.… (mer)