Lists Home |
Date Index |
Following up on Ram's questions, if one was to cherry-pick, what kinds of
situations would benefit from:
1. A document that is not written in a tagged tree structure?
2. A less verbose (streamlined) way to structure content, which (a) is
easily read by humans and (b) comes in a single version that is optimized
for rapid processing/rendering?
3. The ability to parse into multiple documents?
From: Elliotte Rusty Harold [mailto:email@example.com]
Sent: Friday, April 09, 2004 8:43 AM
To: Ram Menon
Subject: Re: [xml-dev] Some Questions on XML and XML Processing
At 3:06 PM +0530 4/9/04, Ram Menon wrote:
1) Is the way XML is written[strctured, tree fashion] just because of the
structured nature of the data it represents? Why was this mode of
representing a document chosen in first place?
>2) XML is so verbose that it cannot be easily interpreted by a human
>Why is it that there aren't two versions of an XML document - a
>"direct" human readable representation of the XML content [ other
>than using XSLT and making it readable], and another representation
>for processing it, which is compact and available for fast
3) Why is it that parsing an XML file leads to only a single XML Document?
Because two forms is substantially more complex than one. Plus, it's
not at all proven that another, non-human readable form would be any
faster than the current form. In fact, there's substantial evidence
to suggest the opposite. Of course, by suitable cherry picking of
test cases, you can prove the proposition either way. But in the real
world, XML processing seems to be quite fast enough. That is it is
rarely the bottleneck in a system.
Elliotte Rusty Harold
Effective XML (Addison-Wesley, 2003)
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription