>Its human readable and it goes through firewalls. ADO.NET will use XML as the storage mechanism for its tables so there will be no performance penalty to serialize the table into XML and send it through the wire. It works much better in a disconnected, distributed world.

This I understand, and agree with.

>Think of Web Services. A Web service needs to provide information that will go through corporate firewalls or else no corporate users could consume Microsoft's new Hailstorm services. It will work on any consumer device too. Mobile phone, PDA, etc.

Yes, I did notice it was particularly aimed at Web Services. I am not involved with Web Services, but writing corporate client management systems which will have no place on the Web - Ever! Unless the government forces us to.

Did you finding switching from RDBMS's to XML a bit tricky/fiddly?

The other thing is, is it possible to relate one XML schema to another, like a relationship ?

Thanks
Kev

>
>-Dave
>
>
>
>>Hi
>>
>>I've just been to an XML seminar and myself and various other developers came away thinking :
>>
>>"What a load of work/learning etc., and for what?"
>>
>>Can anyone please enlighten me as to why I would use XML, what's wrong with ASP's connecting to the Datasource, I must be missing something. I can understand it's a common data structure and doesn't require any specialist product to run.
>>
>>But do the Pro's really way out the Con's?
>>
>>Thanks
>>Kev