We could also build on any of these (using arquillian.org as an example) to make a dedicated schema URL:
- http://arquillian.org/xml/ns/arquillian (consistent with Java EE schemas)
- http://arquillian.org/xsd/arquillian (consistent with Maven)
I'm partial to #2 in the second list for these two reasons:
It removes the association from jboss.org, which fits best when arquillian is used in a product (no need to change jboss.org to jboss.com, for example).
It opens the door for different root XML elements (perhaps we decide to split them out in the future or we need another configuration format. We aren't in the way then).
The result would be:
<?xml version="1.0" encoding="UTF-8"?> <arquillian xmlns="http://arquillian.org/xsd/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://arquillian.org/xsd/arquillian http://arquillian.org/xsd/arquillian-1.0.xsd"> </arquillian>
Other namespaces will come in next v. As we split up impl-base in multiple modules, core, container, container test, test, config etc, each module will have it's own XSD + impl XSDs.
+ Container (container.xsd)
+ Property (jbossasremote.xsd)
+ Property (servlet-3.0.xsd)