I am in the process of refactoring the jboss_x_y.xsd for any EE6 related changes. I am trying to reduce any duplicacy between the ejb-jar xsd and the jboss xsd and instead follow a "extension" model to allow the jboss xsd schema to extend from ejb-jar schema. Although this sort of works, it still has some drawbacks. The other approach i see is to "redefine" some of the ejb-jar "types" to add jboss specific elements in those types. This however, makes it mandatory that both the ejb-jar xsd and jboss xsd have the same targetNameSpace. So effectively jboss xsd will have to have the "http://java.sun.com/xml/ns/javaee" namespace. Note that this does *not* mean that we have to host the xsd there, it's just a logical namespace. I'm curious whether there's any policy around:
1) Using the http://java.sun.com/xml/ns/javaee namespace as the targetNameSpace for application server vendor specific xsds
2) Redefining the types in the http://java.sun.com/xml/ns/javaee namespace.
Is this allowed (techincal/non-technical reasons)?
 An initial step towards https://jira.jboss.org/jira/browse/JBAS-7489
To me, it makes sense to keep the jboss namespace for the jboss-specific elements. This would help differentiate standard and propriatary configuration.