Lists Home |
Date Index |
> Data binding tools use schemas for type information so you could say they
> use them for PSVI [in a way] but not validation. Many of the interop
> problems are of the form "my tool can bind to schemas with construct X
> while my business partner's can't". A real world example of this is trying
> to send nillable types back and forth between Java and .NET XML Web
> Service toolkits.
It is a funny question isn't it: can you have a PSVI when you have not
It's in the lax/strict ballpark I guess...you decide a priori that the
document is valid. Is that the distinguishing feature that needs to be
accommodated? No Schema Validation Infoset (NSVI)?