Are there interoperability concerns with certain xml schema (xsd) construct ?

[John Eapen <j1...@gmail.com>]

Hello -

Are there any do and don't with regards to interoperability when it comes to
using certain XML Schema definition constructs.
eg: Use of <xsd:attribute ../>  , or xsd:choice etc.

Apart from the usual "Element Vs Attribute", is there any reason why in web
services world, one does not see "xsd:attribute" being used much.

I did refer to WS-I Basic Profile 1.0, but did not find anything relevent to
the above.

Appreciate any help

Thanks
  John

Re: Are there interoperability concerns with certain xml schema (xsd) construct ?

[Anne Thomas Manes <at...@gmail.com>]

Attributes are generally okay.
Choice, list, union, abstract types, and substitution groups can cause
interoperability problems.

Anne

On Thu, May 1, 2008 at 3:47 PM, John Eapen <j1...@gmail.com> wrote:
>
> Hello -
>
> Are there any do and don't with regards to interoperability when it comes to
> using certain XML Schema definition constructs.
> eg: Use of <xsd:attribute ../>  , or xsd:choice etc.
>
> Apart from the usual "Element Vs Attribute", is there any reason why in web
> services world, one does not see "xsd:attribute" being used much.
>
> I did refer to WS-I Basic Profile 1.0, but did not find anything relevent to
> the above.
>
> Appreciate any help
>
> Thanks
>   John
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org