• From: "Don Park" <donpark@q...>
• To: <xml-dev@i...>
• Date: Tue, 3 Aug 1999 11:34:40 -0700

Rick,

XML Schema information can be sent in fragments on as-needed basis and, on
the receiving end, cached and accumulated to avoid the problems you are
talking about.  The schema cache can then be used to drive a validation FSM.
Further traffic reduction can be achieved by marking XML fragments with
'validated' hints via custom HTTP header info or embedded tag.

I really do not see a significant enough problem with verbosity that would
negate the benefits offered by the XML schema.  Yeah, the software ends up
more complicated but that is what we get paid for.

Best,

Don Park
Docuverse


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • RE: XML trade off 1 - DTD vs XML Schema
    • From: JR Gardner <jgardner@b...>

• References:
  • Re: XML trade off 1 - DTD vs XML Schema
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: RE: XML trade off 1 - DTD vs XML Schema
• Next by Date: No Subject
• Previous by thread: Re: XML trade off 1 - DTD vs XML Schema
• Next by thread: RE: XML trade off 1 - DTD vs XML Schema
• Index(es):
  • Date
  • Thread