[ https://issues.jboss.org/browse/ELY-1098?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1098: ---------------------------------- bq. root element {{configuration}} is not included in elytron-1_0.xsd, it means that configuration with {{configuration}} are handled as invalid and configuration which has {{authentication-client}} as root element as valid The root element "configuration" should be without namespace, thus it does not belong in any one XSD. Relatedly, it may contain many nested elements, each with different namespaces, which allows all client configuration to exist in a single document (even future APIs which are not yet defined). We could have put "configuration" into its own namespace with an XSD containing a single root element whose type is "xs:any" but that would just mean that the user would have to put in a meaningless namespace onto that root element. We could still do that though as a possibility. I'd want to get a few diverse opinions on that first though, particularly from the support team. bq. XSD elytron-1_0.xsd includes some elements on the highest level of XSD, which for example means that configuration file which includes only element <set-user-name name="someUser"/> is valid according to XSD. There's nothing we can do about this. XML schema is very limited on structure. We certainly have *no* requirement that states that every XSD-valid document is a valid configuration, nor do we have a requirement that every valid configuration is XSD-valid; such a restriction would (in addition to breaking existing code) create unreasonable restrictions for us. It comes down to the determination that the XSD we ship is better than shipping no XSD at all. -- This message was sent by Atlassian JIRA (v7.2.3#72005)