• To: "Hess Yvan" <yvan.hess@i...>
• Subject: Re: Problem designing complexType accepting a specified element and a llowing any others.
• From: "Jeff Greif" <jgreif@a...>
• Date: Thu, 11 Mar 2004 15:10:35 -0800
• Cc: <xml-dev@l...>
• References: <DF7EC83D7AFBD411965B0008C7596EC5E0D49F@i...>

Perhaps in your app the xs:any element can be restricted by
namespace="##other", removing the indeterminacy.
Jeff
----- Original Message ----- 
From: "Hess Yvan" <yvan.hess@i...>
To: <jcowan@r...>
Cc: <xml-dev@l...>
Sent: Thursday, March 11, 2004 1:42 PM
Subject: RE:  Problem designing complexType accepting a specified
element and a llowing any others.


> John,
>
> Thanks for your answer. Do you mean that there is NO solution to solve my
> problem using XML schema ? Are you sure about that because it will have a
> big impact on the project I am working on...
>
> Yvan

• References:
  • RE: Problem designing complexType accepting a specified element and a llowing any others.
    • From: Hess Yvan <yvan.hess@i...>

• Prev by Date: what is an XML Object Broker?
• Next by Date: RE: GenX and attribute QNames
• Previous by thread: RE: Problem designing complexType accepting a specified element and a llowing any others.
• Next by thread: RE: Problem designing complexType accepting a specified element and a llowing any others.
• Index(es):
  • Date
  • Thread