The XML namespace is `http://cm.symfony.com/schema/dic/bundle_name` With `bundle_name` being the di alias of the bundle [1]

 [1]: second paragraph in http://symfony.com/doc/current/cookbook/bundles/extension.html#creating-an-extension-class (we should create a reference there to be able to link to it)

---

I agree with the link for the configuration class support.


With XML schema, I meaned the xsi or XML validation. This is not documented in our docs, because it's not that related to Symfony. It's a file living in the path which is returned by `Configuration::getXsdValidationBasePath` and following the conventions it's `Resources/config/schema/bundle_name-1.0.xsd` (with `bundle_name` being the same as for thhttp://www.w3.org/TR/xmlschema-guide2versioning/e namespace).

For information about that file, I've learned it from http://www.w3.org/TR/xmlschema-guide2versioning/

---

Some others things to bring up, now we are talking about XML schema's:

- to make the best use of them, these should be placed online available for everyone.
- these should be updated every time the configuration class is updated. If that file is out of sync, the configuration won't work anymore. The config component (actually the dependency injection component) first validates the xml using XML schema's and if that fails, it never start parsing.

   As requested by david some weeks ago, I've searched if we can find a way to test the xsd file being up to date and I think I found something. I'll try to submit that before I'm going on holiday (which is monday).