Re: [xml-dev] reasons why an XML instance must be validated with a XML s

["Mukul Gandhi" <gandhi.mukul@gmail.com>]

When XML data is shared (transmitted) between two parties (a sender
and a receiver), the parties usually agree on the Schema of the XML
data. I guess, you know what a Schema is (which Philippe also wrote)..

So if the sender is sending XML data to receiver, then by validating
XML data before sending gives confidence to the sender that it is
sending the correct (i.e., valid data, conforming to the Schema) data.

While the receiver validates data before consuming (or realizing
business benefit out of it) is because, then the receiver has
confidence that it is consuming the correct (valid) data.

On Tue, Sep 9, 2008 at 8:35 PM, ilango <ilangocal@yahoo.com> wrote:
> I just started working on a project that uses JMS/WebSphere MQ with non-J2EE
> systems to build an enterprise system. We would be using XML for all the
> request/response message flows that take place between two system (for
> example, a JMS Listener and one or more than one queues.
>
> I was posed with the following scenario: Our Listener Module submits
> document requests in XML formatted data into an input message queue
> monitored by a document generaton engine.
> The need for validating the XML naturally arises.  Should the XML be
> validated against an XML schema.
> The question they raised was:
> If so, why should we use XML schema to validate XML?
>
> So this is the question I am trying to answer for myself and for my team
> here.
>
> Any suggestions, ideas are gratefully accepted.
>
> thanks
> ilango


-- 
Regards,
Mukul Gandhi