On Wed, Jun 3, 2009 at 11:22 AM, Paul Dietrich <[email protected]> wrote: > Thanks John, > > I understand the side effects, but thought that the behavior you describe > below is desirable rather than detrimental. For example, there are cases > where a user would want to import a single LLRP parameter from LTK-XML into > internal objects (e.g. .NET). It would not be possible to validate this > parameter against the schema unless the parameters appear as root of the > schema. >
Typically, XML documents are validatable but fragments are not, since fragments are not XML AFAIK. > I'm OK with deferring this decision until a later time, but I'm curious what > alternatives you were thinking about to address the issue of LLRP parameters > within custom messages. > I don't use XML Schema every day, so my first thought was for me to re-read the XML Schema specification and try to find a good answer :-) It looks like the link Christian just provided may be helpful in that regard. -- 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
