[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Some Questions on XML and XML Processing

• To: 'Ram Menon' <menon_dev@h...>, xml-dev@l...
• Subject: RE: Some Questions on XML and XML Processing
• From: "Hoebeke, Bram" <Bram.Hoebeke@n...>
• Date: Fri, 9 Apr 2004 15:35:35 +0200

Ram,

1)because a Markup Language is used to identify structures in a document
2)because neither semantics nor tag-set are specified
In HTML, the semantics & tag-set are fixed >> the presentation is always
simular..
3)because parsing = analysing & passing, after that you can display the xml,
enrich it, split it up, aso..

regards,

Bram


-----Original Message-----
From: Ram Menon [mailto:menon_dev@h...]
Sent: April 09, 2004 11:36
To: xml-dev@l...
Subject:  Some Questions on XML and XML Processing


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!


-----------------------------------------------------------------
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
manager: <http://www.oasis-open.org/mlmanage/index.php>

• Prev by Date: Re: XML Binary Characterization WG public list availabl e
• Next by Date: RE: Some Questions on XML and XML Processing
• Previous by thread: RE: XML Binary Characterization WG public list availabl e
• Next by thread: RE: Some Questions on XML and XML Processing
• Index(es):
  • Date
  • Thread