And by the way, this problem is seeming awfully familiar now. ISTR issues with some XML editors dealing with extending existing schemas. The import stuff was just too hard for them.
It was for that reason, at least in part, that I suggest instead of attempting to use the extension mechanisms that are defined by W3C XML Schema, that vendors should create "strongly typed" schemata to go along with their own product releases. In such a scheme, you would provide an alternative to the core LLRP XSD in which you replace the extension point where "anything goes" with an explicit list of allowed parameter types. This would more closely model the reality of the situation since a given reader will only support certain extensions. I continue to believe that is the best course of action. An XSLT could be created to do that. Heck, the bug to do that work is probably still assigned to me ;-) -- 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
