IT Computer Training Articles Tutorials - Submit Your Article - Articles Submission Directory. - Articles - XML

Class-Relational Approach to Tabular and XML Data Representation

no@spam.com (Sergey Savushkin) — Thu, 10 Jan 2008 03:23:08 PKT

This article is directed to all who are interested in XML databases and their possibilities to represent tabular data in XML view. Author, based on the long experience in development of database system (Sav Zigzag ORDBMS), suggests new ideas considering tables and XML as forms for presentation of one common data model. Ideas enable to convert tables set in the XML without using of mapping schema. XPath language may be applied to express the navigation through the correspondent tabular data.

Use XML Standard Entity References

no@spam.com (Jhon Mark) — Wed, 13 Jun 2007 00:00:00 PKT

No reasonably sized keyboard could possibly include all the characters in Unicode. U.S. keyboards are especially weak when it comes to typing in foreign languages with unusual accents and non-Latin scripts. XML allows you to use either character references or entity references to address this problem. In general, named entity references like Ě should be preferred to character references like ě because they're easier on the human beings who have to read the source code.

Stay with XML 1.0

no@spam.com (Jhon Mark) — Wed, 13 Jun 2007 00:00:00 PKT

Everything you need to know about XML 1.1 can be summed up in two rules.

Don't use it.
(For experts only) If you speak Mongolian, Yi, Cambodian, Amharic, Dhivehi, Burmese, or a very few other languages and you want to write your markup (not your text but your markup) in these languages, you can set the version attribute of the XML declaration to 1.1. Otherwise, refer to rule 1.

XML Mark Up with ASCII if Possible

no@spam.com (Mike Tayler) — Mon, 04 Jun 2007 00:00:00 PKT

Despite the rapid growth of Unicode in the last few years, the sad fact is that many text editors and other tools are still tied to platform- and nationality-dependent character sets such as Windows-1252, MacRoman, and SJIS. The only characters all these sets have in common are the 128 ASCII letters, digits, punctuation marks, and control characters. These characters are the only ones that can be reliably displayed and edited across the wide range of computers and software in use today. Thus, if it's not too big a problem, try to limit your markup to the ASCII character set. If you're writing in English, this is normally not a problem.

Include an XML Declaration

no@spam.com (Mike Tayler) — Mon, 04 Jun 2007 00:00:00 PKT

Although XML declarations are optional, every XML document should have one. An XML declaration helps both human users and automated software identify the document as XML. It identifies the version of XML in use, specifies the character encoding, and can even help optimize the parsing. Most importantly, it's a crucial clue that what you're reading is in fact an XML document in environments where file type information is unavailable or unreliable.

Most Frequently Confused XML Terms

no@spam.com (Mike Tayler) — Sun, 03 Jun 2007 00:00:00 PKT

This is neither an introductory book nor an XML tutorial. I assume that you're familiar with the basic structure of an XML document as elements that contain text, that you know how to ask a parser to read an XML document in your language of choice, that you can attach a stylesheet to a document as necessary, and so forth.

XML for Beginner

no@spam.com (Richard Richi) — Mon, 26 Mar 2007 00:00:00 PKT

Welcome to the wonderful world of Extensible Markup Language (XML). This short article is an effort to explain what XML is, what are it's benefits, and briefly describe some of standards evolving around it.