> -----Original Message-----
> From: Glen Daniels [mailto:firstname.lastname@example.org]
> Sent: Tuesday, August 13, 2002 10:52 AM
> To: 'email@example.com'
> Subject: RE: Axis Chokes on Complex Types from MS Soap 3.0
> In other words, SOAP encoding in the case where "names are
> local to their containing types" trumps the schema, and
> requires unqualified elements. I've just fixed our
> BeanSerializer/BeanDeserializer code to account for this and
> am rerunning the tests to make sure all is well. I'm not
> precisely sure when names *wouldn't* be local to their
> containing types (I guess if they somehow were direct
> representations of another type/schema, but I don't think
> that's really doable in most programming languages), so
> perhaps a bit more research is warranted, but this seems like
> the way to go for now.
Hi Glen. I work for a company who has been researching Web Services for better than a year, mostly from a client perspective... and a fair amount of our activities in this area has been centered around potential partnerships with companies who provide data through Web Services. If you look at something like SAP, the trend we're seeing is that independent system integrators are developing web services that sit on top of SAP with each integrator defining his own schema. It's too early to tell which way the wind will blow, but I'm expecting to see a migration from independently managed schemas to schema repositories managed by the source... e.g., SAP. Also, MS's recent partnership with Price-Waterhouse to create an XBLR-based Web Service seems to be yet another push getting people to buy into XBRL.
These are just two example of where you'd potentially see non-local types. My personal opinion is that we'll see this kind of usage sooner than we think.