Lists Home |
Date Index |
- From: "Didier PH Martin" <firstname.lastname@example.org>
- To: <Marc.McDonald@Design-Intelligence.com>, <email@example.com>
- Date: Fri, 12 Mar 1999 23:37:35 -0500
It's quite true that you can have XML that does not require validation
and that this is commonly done. An exception is the defaulting of the
value of any attributes of elements in a DTD, which has been mentioned
in another reply.
You can construct a DOM without validation, but the next step ends up
being a procedural implementation of picking apart the DOM document
tree to construct whatever structure the application using DOM
requires to interpret the document.
I can parse:
<book title="tale of 2 cities">
without a DTD.
But if my application needs to get the information out of the DOM I
need to write code to:
Create a representation for Book consisting of a title and chapters
and get book from DOM
Create a representation for each Chapter and get Chapters from DOM
Create a representation for each paragraph in a chapter and get
paragraphs from DOM.
Part of this is what is expressed in the DTD. Wouldn't it be better if
a system were created that used the DTD on the receiving end to create
the application representation instead of serializing it back into
elements and constructing a new tree?
a) what do mean by " a representation" is it a rendition object?
Didier PH Martin
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)