[
Lists Home |
Date Index |
Thread Index
]
Hi All,
These questions maybe looking odd.... but just curious..
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
audience.
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 processing ?
3) Why is it that parsing an XML file leads to only a single XML Document?
There could be a message coming in, which might mean to represent multiple
payloads; i.e.lets say three XML Documents.... the xml processor could
interpret these, and after parsing the document, spit out three parsed XML
documents?
This information could be either inbuilt into the document, or the XML
Processor could be flagged on this information, and it should act
accordingly.
For e.g.
<Message>
<Header>
<QueueName> ....
<ProprietaryMessageID> ....
</Header>
<Payload>
<EmployeeInformation> ....
<BillInformation>....
</Payload>
<Footer>
<FromCustomer>......
.....
</Footer>
</Message>
After parsing this doc, the parser should generate three documents....., one
each for header, payload and footer.
_________________________________________________________________
News, views and gossip. Hot downloads ‘n previews.
http://www.msn.co.in/Cinema/ Get it all at MSN Cinema!
|
