XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] XML data interchange format: Flatter is better


> Michael Kay wrote:
> 
>> And for my next exciting revelation, I will announce the discovery of third normal form.
> 
> Hello Michael, I assume you are saying this: 
> 
> 	Flat XML does not adhere to 3rd Normal Form 
> 	design and therefore is bad.
> 

No, that's not what I was saying at all. I shouldn't have been so flippant.

By flattening XML you are doing something close to putting the data in first normal form. So I was simply observing that you seemed to be following the path of enlightenment that would soon lead to third normal form (and probably beyond, e.g. to RDF triples).

In fact, normalization has a lot going for it if you want to present a graph of data to a community of users with differing requirements on what subsets of the data they are interested in, and of course it helps to avoid the redundancies that cause update anomalies. But as a data interchange format (the title of your message), no thanks. Messages are naturally hierarchic, it's the one place in data representation where hierarchies really work well, we've been using hierarchically-structured messages to communicate for centuries, and that's why XML and JSON work so well in this role. 

Michael Kay
Saxonica



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS