On Thu, Jun 4, 2009 at 9:55 AM, Chris Delaney <[email protected]> wrote:
> As these are (mostly) recently released products, it is not clear to me that > the desired behavior is possible when only importing complex types (i.e. not > having the imported complex types declared as global elements). In fact, the > paragraph following the third example at: > http://www.w3.org/TR/xmlschema-0/#DefnDeclars > seems to imply exactly what we are finding. The second sentence reads, "In > general, the value of the ref attribute must reference a global element, i.e. > one that has been declared under schema rather than as part of a complex type > definition." It also goes on to state the limitation we originally tried to > avoid, that using ref= means the global elements may exist as the root > element within an instance document. > Chris, Perhaps we are supposed to use type= rather than ref= ? See the <import> examples in the link below. http://www.xfront.com/ZeroOneOrManyNamespaces.html heading: [1] Heterogeneous Namespace Design I think that's the same was what we're doing here. Starlet is giving me a nonsensical error against the instance XML for the hetergeneous case, maybe you can try that approach with a different validator. -- John. ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
